Mayank JainEngineering Manager
Bengaluru, India  ·  9+ years  ·  India & North America

I take the systems everyone is afraid to touch and make them boring to deploy.

Eight years scaling the device-lifecycle platform behind Apple, Samsung, HP and AT&T — then two products for safari operators, built end to end, alone. I lead teams of up to ten and still review the diff.

The Platform V2 rebuild Open the console
platform_v2 — aftershipped
production incidents−70%
throughput+50%
release velocity2×
time-to-interactive−40%

Monolith → independently deployable Node.js services, migrated one capability at a time with the old path live.

01AboutBengaluru, India

Same product, progressively larger blast radius.

Ten years, three cities, one consistent bet: the interesting problems live where software meets the people who have to keep it running.

I started in 2016 on live video — detecting ad breaks in IP streams and swapping in personalised spots. Then eight years on one platform as it grew from a consumer app for device repair into infrastructure that Apple, Samsung, HP and AT&T route real warranty and claims volume through. Mumbai, then Toronto, then Bengaluru.

Managing never took me out of the code. I have never been able to set architectural direction I wasn't willing to read line by line — and the months I spent building Halisi alone, every layer from multi-tenant isolation to 2am production support, were partly to check that the instinct was still real. It was.

Education
BCA, Computer Science — Jain University, 2016
Based
Bengaluru — previously Toronto and Mumbai
Open to
Engineering Manager · Senior / Staff Engineer — remote, hybrid or relocation
How I work
01
Contracts before codeAgreeing on the interface is far cheaper than agreeing about it afterwards, across four squads.
02
A boring deploy is a featureObservability, logging and pipelines go in before the migration, not after the first incident.
03
I still read the diffDirection I'm not willing to review line by line isn't direction — it's an opinion.
Core skills

Frontend

TypeScriptJavaScript (ES6+)ReactNext.jsReduxHTML5CSS3Micro frontendsDesign systemsComponent librariesServer-side renderingResponsive designAccessibility (WCAG)Performance optimisation

Backend & platform

Node.jsMicroservicesREST API designSystem designMonolith decompositionMulti-tenant architectureMulti-region deploymentsScalability & reliability

Testing & delivery

React Testing LibraryPlaywrightCypressUnit / integration / E2EJenkinsCI/CD pipeline designDockerRelease managementObservabilityDistributed logging

Cloud

AWSGCPAutoscalingManaged databasesMonitoringMulti-environment rollouts

AI & GenAI

LLM feature integrationRAGPrompt engineeringAI-assisted developmentClaudeCursorGitHub Copilot

Leadership

People managementHiringPerformance reviewsMentoring & coachingAgile / ScrumTechnical roadmappingCross-functional managementStakeholder management
02ImpactServify · 2018–2026

The numbers I'd want you to ask about.

Every figure came out of one rebuild, or the delivery discipline built around it. Ask me what broke on the way — that part is more interesting.

−70%Production incidentsMonolith decomposed into independently deployable Node.js services.
+50%ThroughputStandardised API contracts across warranty, claims and buyback.
2×Release velocityFour squads shipping on their own cadence instead of one train.
−40%Time-to-interactiveLazy loading, code splitting and CDN asset delivery on the React frontend.
−30%JS bundle sizeTree shaking plus one shared component library instead of five forks.
−60%Deployment timeJenkins pipelines that made a production deploy a non-event.
10 engineers led4 squads4 regions — India, MEA, EU, US8 years at Servify2 products shipped solo
03Experience2016 → 2026

Ten years, one direction.

Video player → consumer app → enterprise platform → my own products. Each step a larger blast radius than the last.

Feb — Aug 2026Bengaluru

Co-Founder & Engineering Lead

Halisi Safari Solutions

Two products for safari operators, designed and shipped end to end as sole engineer — a headless itinerary CMS and a multi-tenant booking and operations platform. Both live, with paying operators running daily business on them.

  • Owned the whole stack in production: multi-tenant isolation, role-based access across operators, camps and agents, releases, monitoring and support.
  • Integrated LLM-backed itinerary drafting and guest replies into the operator workflow, cutting the manual effort of answering enquiries.
Next.js 15TypeScriptNode.jsMongoDBMulti-tenantRAG / LLM

Both products in detail  ↓ section 04

Sep 2018 — Jan 2026Mumbai · Toronto · Bengaluru

Servify

8 years · 3 cities · 3 roles

The device-lifecycle platform behind Apple, Samsung, HP and AT&T — protection plans, claims, repair, exchange and buyback, running across four regions.

Engineering ManagerJun 2024 — Jan 2026 · Bengaluru
  • Led 10 engineers across 4 squads — hiring, performance and career development — while staying in code and design review.
  • Led Platform V2: monolith decomposed into independently deployable Node.js microservices with standardised API contracts.
  • Built an SSR and brand-theming framework for full partner whitelabelling from one shared component library.
  • Designed the Jenkins CI/CD pipelines across services and React apps — deployment time down ~60%.
Software Engineering ManagerJun 2021 — May 2024 · Toronto
  • Led a cross-functional frontend and backend team from technical design through QA, rollout and post-launch stabilisation.
  • Shipped the product surfaces for ML-backed capabilities — fraud detection, GSM warranty validation, automated device diagnostics.
  • Ran services on AWS and GCP under multi-region traffic — India, MEA, EU, US.
Lead Product EngineerSep 2018 — Jun 2021 · Mumbai
  • Built the React-Redux consumer app for device after-sales, deployed for Apple, OnePlus, Nokia, Motorola and Samsung.
  • Delivered internationalisation including Chinese and Arabic with full RTL support.
  • Integrated payments across Razorpay, Stripe, PayPal and Telr.
2016 — 2018Bengaluru
Software Engineer iService

Booking product, e-commerce site and internal CRM for doorstep device repair.

Frontend Developer Vidgyor

Auto-detection of TV ad breaks on live IP streams, swapping broadcast ads for personalised video.

04Case studyServify · 2024–2026

Strangling a monolith in production

Four enterprise partners, four regions, zero acceptable downtime, and a roadmap nobody would let us pause.

01 — The situation

One codebase served Apple, Samsung, HP and AT&T across India, MEA, EU and the US. Every release was a coordinated event, and a bug in one partner's warranty flow could take down another partner's claims flow. The incident rate reflected exactly that.

02 — The real risk

Not the architecture — the team. Ten engineers across four squads, each with their own partner commitments, could just as easily have built four inconsistent services and landed on a distributed monolith. That is worse than what we started with.

03 — What I did

Refused the big-bang rewrite. Drew service boundaries around business capability, standardised API contracts before anyone wrote a service, then strangled the monolith one capability at a time — old path live until the new one proved itself. Observability, distributed logging and Jenkins pipelines went in ahead of the migration, so a deploy became boring rather than an event.

Four squads came out of it shipping to one standard rather than four. That outcome matters more to me than the incident graph.

MONOLITH warranty claims buyback repair payments diagnostics ONE RELEASE TRAIN · SHARED BLAST RADIUS 4 partners · 4 regions LEGACY shrinking STRANGLER API CONTRACTS warranty-servicenode.js · own deploy claims-servicenode.js · own deploy buyback-servicenode.js · own deploy payments & the restmigrated behind the same contract OBSERVABILITY + CI/CD WENT IN FIRST
−70%Incidents
+50%Throughput
2×Release velocity
−60%Deploy time
05ProductsHalisi · 2026 · sole engineer

Two products, one engineer,
live in production.

Halisi Safari Solutions is safari-operations infrastructure. I designed, built, shipped and support both products — architecture, data model, frontend, auth, billing logic, deploys and the 2am incidents.

marvelsofafrica.com / itineraries
Itinerary CMS frontend Payload CMS admin
Product 01 — headless CMS

Itinerary CMS

A self-hosted headless CMS and marketing frontend for safari itineraries. Editors stack blocks into pages and multi-day trips, and the same content renders as a web page or a print-ready PDF.

  • Block-based page builder. Every section is a Payload block wired to the frontend through one render map — new layouts without a deploy.
  • Itinerary engine. Day-by-day timeline, camps and lodges, expected sightings, inclusions, gallery, reviews and FAQ.
  • Luxury PDF export. A PDF-only render mode with its own cover and page-break rules — one content source, two very different outputs.
  • Attributed enquiries. A shared form context records which page and which block opened every lead.
Stack
Next.js 15 App Router · TypeScript · Payload 3 · MongoDB · Tailwind + shadcn/ui
Content
Lexical rich text · nested docs · SEO, search and redirect plugins · S3 media · live preview
Testing
Vitest + Testing Library
halisisafarisolutions.com / platform
Halisi platform console Operator CRM analytics
Product 02 — multi-tenant SaaS

Safari Booking Management

The operations platform underneath. Each operator signs in on their own subdomain with their own branding, users and roles; the Halisi console runs on the apex domain and onboards new tenants.

  • Tenant isolation by subdomain. Middleware resolves host to tenant; every query, role and asset is scoped to it — one deployment serving the console and every operator.
  • Money, carefully. Bookings into verification, supplier ledger, credit notes and multi-currency instalments — cash-based P&L bucketed by payment date, not sold price.
  • Operations views. Cashflow heatmap of inflow against unpaid supplier balance, a bookings calendar, and analytics that merge multi-country trips into one destination line.
  • Auth for shared laptops. Session JWT plus a device cookie, email OTP on every new device, invite and set-password flows, per-tenant role validation.
Stack
Next.js 15 · React 19 · TypeScript · MongoDB / Mongoose · Zod
Platform
Multi-tenant subdomains on one Vercel project · Vercel Blob · Brevo transactional mail · jsPDF documents
Scope
Tenants, roles, bookings, quotes, rate book, group departures, guides, agents, supplier credit notes

Both repositories are private under the Halisi-safari-solutions organisation — happy to walk through the code in an interview.

06Consoletype help

Or just ask the shell.

Everything on this page, queryable. A few commands aren't on the list.

mayank@portfolio — zsh
❯
07Contactavailable immediately

Let's talk about
the hard part.

If you're rebuilding something in flight, standing up a platform team, or you need someone who will lead it and still write code — I'd like to hear about it.

available immediately
mayank007.j@gmail.com +91 99724 14529 in/mayank-jain-5a2b65125
Bengaluru, India
Résumé — PDF

Open to Engineering Manager and Senior / Staff Engineer roles. Remote, hybrid or relocation.