I grew up in India and later earned my bachelor's and master's degrees in Computer Science, before starting out as an engineer — actually writing code, debugging production systems at 2am, and learning what breaks when you scale something past what it was designed for. Sixteen years later I'm still the person who wants to understand how something actually works before I tell anyone what to do about it. I love solving complex problems, and I try to leave every system in a better state than the one I inherited.

Most of my career has been in financial services and healthcare, which means I've spent a lot of time in systems where the consequences of being wrong are real — money moves, patients get billed, regulators audit. That context shapes how I think about architecture. I don't love complexity for its own sake. I like the simplest thing that holds.

The work I'm proudest of isn't the greenfield stuff. It's the systems nobody wanted to touch — large-scale portfolio conversions and post-merger migrations with no documentation, an event pipeline hitting a ceiling nobody'd measured, a legacy black box that everyone worked around for years. Across my career I've moved over 900 million records — roughly 1.5 TB combined — through conversions like these, spanning Walmart, the COF–DFS merger, and others.

Most of my career has meant wearing every hat on the org chart at some point — architect, developer, and the person explaining to a customer why any of it matters. That's on purpose. Architecture divorced from implementation and product reality tends to produce beautiful diagrams that don't survive contact with production.

On the side I'm building open-source tools and running LumenPaths, a coaching platform helping senior engineers build the extraordinary professional profile that opens doors. Based in Richmond, VA.

Outside of all that, I practice calligraphy, and I read almost exclusively nonfiction — enough of it that I ended up building a small home library just to hold it.