About
I’m a software architecture leader in Ontario, Canada, and an AWS Certified Solutions Architect. Fifteen years of building platforms that other systems depend on — in banking, life sciences, automotive IoT, and the electricity grid.
I started my career writing software for electricity distribution utilities, which is a strange and excellent place to begin. When your software misbehaves, someone’s lights go out. That never quite left me. Everything since — telemetry pipelines at Bosch, platform modernisation at GSK, lending infrastructure at U.S. Bank — has been a variation on the same question: how do you build something that keeps working when you’re not looking at it?
Lately the question has a new wrinkle. I’ve been building multi-agent systems that take on real parts of the delivery lifecycle — analysis, planning, code generation, validation — inside a pipeline that has to stay auditable. That’s most of what I’m thinking about right now, and a lot of what ends up here.
The road here
Feb 2023 — now
Toronto, Ontario
Lead Software Development Engineer
Architecture for a merchant lending platform that moves millions of transactions a day. Service boundaries, data contracts, API governance through APIGEE, and a secure SDLC that has to satisfy people whose job is to assume the worst. Hybrid on-prem and Azure, Rancher-managed Kubernetes, Kafka in the middle of it all.
Dec 2021 — Feb 2023
Toronto, Ontario
Software Architecture Lead
Took a Struts-and-WebLogic monolith apart and put it back together as Spring Boot services — cutting inter-module dependencies by sixty percent and letting teams deploy without asking each other for permission. Built a scaffolding generator so every new service started consistent instead of creatively different.
Nov 2016 — Nov 2021
Bengaluru, India
SDE III — IoT & Connected Systems
Connected vehicles, which is to say: telemetry arriving continuously from devices in the field, and a platform that has to make sense of it in real time. Twenty-plus microservices, CQRS and Project Reactor to keep queries sub-second under load, and a serverless alerting path that took infrastructure spend from roughly $65K a year to $17K.
Oct 2011 — Jun 2015
Visakhapatnam, India
Technical Analyst — Utility Software
Where I learned that software can have physical consequences. Distribution management, outage management, SCADA integration — grid topology models and data feeds for electricity utilities, built alongside engineers who thought in substations rather than sprints. Nothing since has taught me more about designing for consequences.
Before all of that: an M.Tech in Computer Science from JNTU Kakinada, and a stint at TCS building high-security authentication for a financial client. The formal portfolio ↗ has the case studies, numbers and architecture diagrams.
What I actually believe
Frameworks are interchangeable. Interfaces between teams, services and eras of a codebase are not — and that is where the interesting failures live.
Code, docs, diagrams, commit messages. Someone is going to read this in two years with no context and a production incident open. Write for them.
The measure of an architect is not the diagram. It is whether the engineers around you can make the next ten decisions without you in the room.
Every migration I have shipped kept a way back. Confidence to move fast comes from knowing exactly how you would undo it.