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.
MRCC reporting workflow, automated end-to-end
tier-1 banks served across engagements
Java modernization, Ant → Maven, led end-to-end
Regulatory automation
I developed and integrated a native Java transformation engine inside FmConverge to process raw Murex data for MRCC reporting, turning a manual 2-day workflow into a 10-minute automated process. Alongside it, I engineered a standalone Python automation suite handling the secure conversion and direct submission of generated reports to the CDS for RBS Tranche reporting, eliminating manual validation entirely.
Treasury MIS, end to end
I spearheaded the end-to-end implementation and adoption of FmConverge treasury MIS at a client bank · designing and deploying cross-asset dashboards for Market Risk, Asset Quality, and Mutual Funds, with front-end configuration tools so the bank's own teams could enhance reports dynamically instead of raising tickets.
Production, where it counts
- Provided critical production support for post-go-live risk analytics, specifically optimizing Greeks (Delta) and Outstanding Notional reporting.
- Led the technical modernization of core project frameworks from Java 8 (Ant) to Java 17 (Maven).
- Worked daily with treasury, risk, and IT stakeholders on the client side, the human half of forward deployment.
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. This is the job I want more of.