About Me

I grew up in India, built my career across 25 years in Australia, and now call the US home. Each chapter gave me a different lens — on engineering, leadership, and what it means to build teams that ship meaningful work.

"The best engineering leaders aren't the ones with all the answers. They're the ones who've learned to ask better questions."

In India, I learned to be resourceful. In Australia, I learned to build systems that scale. In the US, I learned to move fast without breaking trust. These aren't just places I've lived — they're perspectives I carry into every architecture review, every team standup, every decision about what to build next.

Where I've Been

Today I'm fortunate to be in the automotive industry, contributing to connected car platforms across 300+ microservices serving multiple brands and regions. It's the kind of work where architecture decisions, release management, and cross-regional coordination all collide — and I get to be part of a team that makes it work.

Before that, I spent three years helping deliver a connected car platform for the Australian market — shipping mobile apps with strong adoption and streamlining deployments across iOS and Android. I've worked in consulting on large-scale ERP transformations and enterprise mobile architecture. And for over a decade, I had the privilege of being the enterprise architecture lead across mining, energy, and utilities — learning something new from every project and every team I worked with.

The thread through all of it: being part of teams that take complex systems and make them work for the people who use them. Whether that's 300 microservices or an ERP landscape, the challenge is the same — clarity, delivery, trust.

What I'm Building With AI

I use AI every day — not to write code, but to be a better leader. It helps me stay organized, prepare sharper for meetings, and turn complex data into something my team, peers, and leadership can actually act on. I'm constantly exploring how AI can make the people around me more effective — not replace what they do, but remove the friction that slows them down.

This site itself is an example. It was built entirely with AI-assisted development — from design system to deployment pipeline. I believe the future of engineering leadership includes knowing how to work with AI, not just knowing how to code.

What I Write About

Every post follows a simple structure: 5 Steps to [outcome]. No fluff. No 3,000-word essays. Just practical, distilled advice you can use today.

• Technical Deep Dives — Architecture decisions, system design, and the trade-offs nobody warns you about.
• Career & Leadership — Growing as an engineer, leading teams, and navigating the politics of building software.
• Industry Trends — What's real, what's hype, and how to tell the difference.
• Tutorials — Step-by-step guides for tools and technologies I actually use.

Why I Write

"Writing forces clarity. If you can't explain it in 5 steps, you don't understand it well enough."

I started writing because I kept having the same conversations — with my team, with peers, with engineers just starting out. The "5 Steps" format forces me to distill what I know into something genuinely useful.

If you've ever wished someone would just tell you the practical version — without the jargon, the caveats, or the "it depends" — that's what I'm trying to build here.