Nineteen years wiring the parts of a transaction that break quietly — duplicates, blown settlement windows, onboarding that eats a quarter. Here's what that journey looks like.
Authorize → Capture → Clear → Settle. Tap any node to see how it breaks — and where I fixed it.
The full story lives across three pages: how the career actually unfolded, the engineering problems worth showing in detail, and the resume itself.
From a junior Java developer in Pune to running a 10-person cloud engineering org — five roles, one obsession with payments that don't fail.
Read the journey 02Three engineering problems worth a closer look: the 8-hour settlement run, onboarding-as-a-project, and a cache that's never stale.
See the work 03The condensed version — roles, dates, and results, formatted for a hiring manager with fifteen seconds.
View resumeSame settlement run, before and after re-architecting the engine for parallel processing at Verifone. The bar is to scale.
Alongside the re-architecture: an idempotency key framework for exactly-once processing, and a shift to container-backed integration tests that catch real integration failures before release. Full case study →