About

I started my engineering career in India in 2001, working on mainframe batch processing and CICS programmes in financial services. Moved to the UK in 2007 and have spent the last two decades architecting and delivering complex transformation programmes across consumer credit, payments, and banking platforms.

The journey from individual contributor engineer to leading architecture functions has spanned every major technology paradigm shift of the last quarter century. Mainframe batch processing and COBOL. Client-server architectures and distributed computing. Service-oriented architecture and SOAP integration. The shift to cloud-native platforms, domain-driven design, and event-driven systems. API-first architecture and the unbundling of monolithic platforms. Now building at the intersection of enterprise architecture and AI – multi-agent orchestration, autonomous systems at scale, and the practical constraints of deploying intelligence in regulated environments.

Twenty-five years across retail banking, consumer credit, payments, and platform modernization. The constant has been navigating the gap between what should work architecturally and what actually delivers in complex organizational environments under real-world constraints.

Currently leading architecture across payments, consumer credit, and retail lending platforms in financial services. Managing architecture teams of 60+ across programmes and platforms, running governance forums, and steering transformation initiatives through complex organizational and technical landscapes. Recent delivery includes national credit card product launches serving hundreds of thousands of customers, cloud-native consumer credit platforms built on domain-driven and event-driven architecture, and payments transformation programmes navigating legacy modernization alongside strategic platform builds. Prior consulting leadership included building and leading cloud platform engineering capability teams, running multi-million pound bids and RFP responses in the financial services sector, and operating across both delivery execution and commercial growth simultaneously.

The technical work spans event-driven architecture at scale, API-first platform design, cloud-native application development on AWS, and the organizational challenge of landing modern architecture patterns in environments built on decades of accumulated technical debt. Recently exploring AI deployment at enterprise scale—designing multi-agent systems, implementing guardrail frameworks for autonomous operation, and validating what works and what fails when AI meets regulatory constraints and organizational complexity.

Two decades navigating external paradigm shifts—from mainframe to cloud-native, monolithic to event-driven, waterfall to continuous delivery—taught me that technical transformation is fundamentally about managing change in complex human systems. The learning from Edition 5 of the newsletter: these shifts succeed when you focus on the work, maintain an open disposition to what’s emerging, and recognize that the situational nuances matter more than the framework. What works in one context fails in another. The Architect’s Field Guide captures 50 situations across six zones—the decisions, politics, and tradeoffs that textbooks don’t prepare you for.

The transition from individual contributor to leading teams brought its own internal paradigm shift, explored in Edition 10. Learning to execute work through others. Facilitating rather than doing. Filtering organizational stress so the team can function. The realization that uncertainty and chaos aren’t obstacles to be eliminated—they’re the breeding ground for opportunities. The only way forward is harvesting them in the fields of uncertainty. And right now, AI is the biggest opportunity of them all. Not just for architects or technologists, but for everyone willing to learn what autonomous systems can actually do at scale versus what the marketing promises.

I’m currently finishing The Architect’s Field Guide, a comprehensive practitioner’s manual for navigating the real challenges of architecture work in large organizations. 100+ pages of situational guidance covering six zones of architectural practice: making decisions under constraint, building influence without authority, navigating organizational friction, establishing technical credibility, maintaining intellectual honesty, and managing the personal toll of the role. Each zone contains practical situations you’ll recognize from your own work, with guidance on how to navigate them effectively. The Field Guide launches in May 2026.

Connect

I publish weekly on LinkedIn and through the newsletter. If you’re navigating similar terrain—transformation complexity, architecture decisions under organizational pressure, or responsible AI deployment—I’d be glad to connect.