Core banking, payments, and cloud storage platforms — architected, shipped, and run in production at Kotak Mahindra Bank, AWS Aurora, Tide, and Amazon. Available for architecture consulting, fractional staff-engineering, and hands-on builds.
Trusted in production at Kotak Mahindra Bank · AWS (Aurora Storage) · Tide · Amazon · OYO · Druva
Whether you need a second opinion on an architecture, a senior engineer embedded in your team, or a system built end to end — the common thread is banking-grade correctness without banking-grade slowness. Full details on the consulting page →
A focused, two-week deep dive into a system that worries you. Written assessment, prioritised risk list, a design you can implement.
Part-time, ongoing. I own technical direction, run design reviews, and level up your engineers — without a full-time Staff hire.
Fixed-scope software delivery: payment flows, statement platforms, pricing engines, data pipelines on AWS.
Numbers I'm accountable for, not numbers I sat next to.
| Outcome | What it took | Where |
|---|---|---|
| 50M+ / month | PDF statements generated and delivered across email, SMS, push, post and links; moved off the Finacle monolith so it scales independently. | Kotak Mahindra Bank |
| ₹700 Cr / month | Charges recovery platform: configurable onboarding, alert-to-charge orchestration, pre-debit notices; SQS + DynamoDB conditional writes so retries never double-charge. | Kotak Mahindra Bank |
| ₹10 Cr / year | Third-party statement vendor replaced with an in-house platform; regulatory delivery gaps closed. | Kotak Mahindra Bank |
| 3h → 1.5h | Average incident resolution, after unifying on-call across US/EU/APAC with component ownership, SOPs and automated routing. | AWS Aurora Storage |
| 8× · −30% | Virtual-thread pub/sub library (8× throughput) and an S3/SNS/SQS micro-batching framework (30% infra cost cut). | AWS Aurora Storage |
| 3.5 mo → 1 h | Seller VAT-registration validation SLA, by re-engineering the questionnaire workflow and automating DLQ handling. | Amazon |
| 150M+ / day | Check-in/check-out events on a re-architected communication platform and IAM. | OYO |
The same discipline that keeps a bank's ledger correct is what lets a small team ship fast without fear.
DDD workshops with the people who own the process, not just the code. The model comes before the microservices.
Every path assumes retries, restarts and duplicates. Idempotency and auditability are requirements, not add-ons.
Thin vertical slices to production early. Configuration-led onboarding so the second product is cheap.
Runbooks, SOPs, dashboards, and a team that understands the system. AI accelerates the drafting; engineers verify.
Banking, cloud storage, payments, hospitality, e-commerce, disaster recovery, mobility.
Lead two teams across architecture, delivery and mentoring. Own the statement delivery platform (50M+/month) and the charges recovery platform (~₹700 Cr/month). Introduced AI-assisted design and review workflows with human verification for security and compliance.
Enabled Aurora Storage for Aurora Global Database and Neptune Global Database. Cluster autoscaling control plane, virtual-thread pub/sub (8×), micro-batching framework (−30% cost), unified follow-the-sun on-call.
Led two teams (10 engineers). Architected the payment platform for multi-market expansion, launched Tide India, designed the in-house ledger.
IAM re-architecture and communication-platform scaling for 150M+ daily check-in/checkout events on Kafka-based microservices.
Cut seller VAT validation from 3.5 months to 1 hour. Built the multi-tenant, multi-language QuizStoreService for Hireon.
VMware disaster-recovery restore into customer AWS VPC/VMC with RTO in minutes, for 10,000+ servers of ~1 TB each.
Digital Campaign Tracker for Sony Entertainment; multi-master offline sync with last-write-wins reconciliation.
Short, specific pieces on distributed systems and the staff-engineer path. Read all posts →
The shelf I actually recommend to people I mentor. See all 15 books, plus 10 foundational papers →
Still the fastest way to give a team a shared vocabulary for "this is hard to read".
See details →Habits that outlast any specific stack — the 20th-anniversary edition holds up.
See details →The clearest short book on what "complexity" actually costs and where it hides.
See details →Reply within two working days. If it isn't a fit, I'll say so and point you somewhere better.