Forward-deployed at four tier-1 banks.

I worked across multiple tier-1 financial institutions delivering and enhancing FinMechanics' high-performance treasury solutions, leveraging its cloud-ready microservices architecture to streamline cross-asset risk management, regulatory compliance, and front-to-back office workflows. Not from a desk at HQ: embedded on-site, inside the bank's own change-management process, where every release has a UAT sign-off and a go-live call attached to it.

Fixed Income go-live · South Indian client bank

My first engagement was the project implementation and go-live of the Fixed Income Module at a South Indian client bank. The work involved deep data consolidation: mapping and loading positions, transactions, and reference data into the right SQL table structures for OFSAA and ADF feeds, while simultaneously delivering a set of client-specific features the bank needed before sign-off. It meant constantly context-switching between data engineering, feature work, and coordinating with the bank's IT and treasury teams to keep the go-live timeline intact.

MRCC regulatory automation · International client bank

Mid-engagement, I voluntarily picked up a custom project at a second, international client bank — one nobody else on the team was handling. The ask: automate the preparation of input files required for MRCC (Market Risk Capital Charge) regulations, a process the bank was doing manually over two days each reporting cycle.

I built a native Java transformation engine inside FmConverge to process raw Murex data and produce the regulatory input files, and a standalone Python automation suite to handle secure conversion and direct submission to the CDS for RBS Tranche reporting. The full scope was scoped at 2.5 months. I finished development in one month and moved straight into UAT.

The result: a 2-day manual workflow compressed to 10 minutes, automated end-to-end. That number is on the homepage because it's the clearest thing I can point to.

Production support · Third international client bank

The pace of the MRCC project got noticed. I was assigned to lead the production support team for a third international client bank — post go-live, where the stakes are real and the error tolerance is zero. The work was optimizing live risk analytics: specifically Greeks (Delta) and Outstanding Notional reporting, tracking down data discrepancies that only showed up under production volumes, and being the person the bank's IT team called when something didn't reconcile.

Java modernization · Two client banks

In my final months, I led the technical modernization of the core project framework at two client banks — migrating from Java 8 (Ant) to Java 17 (Maven). This wasn't a lift-and-shift; it required resolving compatibility breaks across the entire dependency tree, updating build pipelines, and validating that production behaviour was preserved. Running two of these in parallel meant careful coordination to keep both banks' timelines on track.

Why I left

My father was diagnosed with a progressive neurological disease. I made the decision to come back home to Mumbai, and to put family first. After settling in, I chose to direct that same energy into his business — Rispri Labs, an environmental testing and water treatment company — and into building things of my own.

What it taught me

That enterprise software succeeds or fails in the last mile: data quirks nobody documented, approval chains nobody mentioned, and users who need to trust the number before they use the system. And that ownership — actually raising your hand for the hard problem — is what separates people who are there from people who matter. This is the kind of work I want more of.