KM.
Lead Backend / PlatformFormer CTO
Remote available

Think like a founder.Build like an engineer.Care like a customer.

I build distributed systems with end-to-end ownership—from architecture and delivery to production recovery and customer impact.

Kapil Mehta

Lead · Staff · Principal
Udaipur, India

Let’s talk
10+ years in engineering
40M+events / dayChargebee · 60+ modules · 10+ teams
30×faster webhooksChargebee · ~6s → 200ms
40×faster deploymentsChargebee · ~2h → 3 min
200K+registered usersGohiggs · founder-led scale

01 · Selected engineering work

Complex systems. Clear ownership. Measurable outcomes.

A selection of platform, recovery, and product systems I’ve owned from architecture through production.

01 / Chargebee

A shared queue platform for teams and languages

Context. Teams needed a consistent way to work across SQS, SNS, and Kafka without coupling product modules to provider-specific details.

Ownership. Owned the architecture and evolution of a language-agnostic gRPC abstraction, including its adoption across the organization.

Design. Established a shared boundary over messaging infrastructure and automated queue provisioning through Terraform-based CI/CD.

Outcome

40M+ events per day across 60+ modules, 10+ teams, and 20+ engineers.

Conceptual architectureNot an exact internal design
Product modules60+ producers & consumers
Queue frameworkLanguage-agnostic gRPC boundary
SQS
SNS
Kafka
Terraform CI/CD · automated provisioning and plan generation

02 / Chargebee

Recovery engineered around customer impact

Context. As the Platform team’s primary contact for major incidents, reliability decisions had direct consequences for customer workloads.

Ownership. Led incident recovery, identified Lambda concurrency constraints, and drove the resulting ECS redesign.

Design. Architected a cross-shard, cross-region Job Recovery Platform to strengthen recovery across distributed workloads.

Outcome

Restored queue, job, and webhook workloads within approximately 3 hours during a major AWS disruption.

03 / Gohiggs

Founder-level ownership, engineer-level depth

Context. Building a real-time social platform required product judgment, technical delivery, and operational ownership to move together.

Ownership. As CTO & Co-Founder, owned AWS architecture and core backend systems end to end.

Design. Built self-managed live-streaming infrastructure supporting approximately 500 concurrent viewers.

Outcome

Scaled to 200K+ registered users, helped secure ₹10 million in funding, and led a 10-engineer team.

04 / Kadel Labs

OkayGo’s backend foundation

Context. The workforce platform needed a cohesive technical foundation spanning matching, APIs, and deployment.

Ownership. Architected the end-to-end backend and established engineering standards.

Design. Defined APIs, domain boundaries, workforce matching, and deployment architecture.

Outcome

The OkayGo platform was later acquired by BetterPlace.

02 · How I work

Engineering judgment grounded in what happens next.

01

Customer impact

Own the incident, restore the workload, then redesign the constraint that caused it.

02

Systems thinking

Set durable abstraction boundaries across messaging, asynchronous workflows, and recovery architecture.

03

Engineering leadership

Write design documents, review deeply, and make sound decisions easier across teams.

400+ PR reviews · mentored 3–4 · advised 30+ engineers

04

Founder mindset

Connect product needs, delivery constraints, and technical decisions without losing hands-on depth.

03 · Experience

A decade of building, scaling, and leading.

01

Chargebee

Remote, India

Lead Software Engineer

Senior → Principal → Lead

02

Novopay

Remote, India

Senior Software Engineer · Contract

Banking, payments & eKYC

03

Kadel Labs

Udaipur, India

Principal Software Engineer

OkayGo platform architecture

04

Gohiggs

Udaipur, India

CTO & Co-Founder

Product, platform & team ownership

05

Deerghayu Lifestyle

Udaipur, India

Java Developer

SaaS clinical-data workflows

04 · Technical expertise

Deep backend craft, from protocol to production.

Backend

  • Java
  • Go
  • Node.js
  • Spring Boot
  • REST
  • gRPC

Distributed systems

  • SQS
  • SNS
  • Kafka
  • Asynchronous workflows

Cloud & infrastructure

  • AWS
  • ECS
  • EC2
  • Lambda
  • Terraform
  • Docker
  • CI/CD

Data

  • RDS
  • DynamoDB
  • S3
  • ClickHouse (proof of concept)

Observability

  • OpenTelemetry
  • Datadog
  • Splunk
  • Grafana

05 · Contact

Hiring remotely?
Let’s talk.

I’m looking for a remote backend or platform engineering role where I can own complex systems, solve customer problems, and help teams deliver.

mehta.kapil25@gmail.com
LinkedIn Résumé