About
Hi, I'm Vibhor.
Engineering manager and solution architect. I lead cross-functional teams and write about the move from engineer to manager.
I started out as a software engineer and still think like one. These days I lead cross-functional teams of up to 20 people, and I'm also the person clients call when they need a technical decision explained in plain terms. This blog is where I write down what that work has taught me.
Why I write this
When I moved from writing code to leading the people who write it, I found plenty of advice on management and plenty on engineering, and very little on the space between them. Nobody told me that the hardest part would be letting go of the technical answer I could already see. So I write the guide I wanted at the time: practical, specific, and honest about what is awkward.
What I've done
My path has gone through both architecture and management, and I draw on both here.
- Leading teams. I run delivery across several projects at once. That covers planning and estimation, budgets, risk, and the day-to-day work of keeping people focused and growing. I run my own hiring, onboarding, feedback, and mentoring.
- Architecture and consulting. I've led presales work, proofs of concept, and MVPs. I've built as-is to to-be roadmaps for existing systems, and advised clients on when, why, and how to adopt a technology, including when not to.
- Cloud and delivery practice. I've worked on cloud designs spanning compute, serverless, storage, databases, and messaging, and on the CI/CD, testing, and code-quality practices that keep them shippable.
- GenAI in real teams. I help teams choose and adopt GenAI tools, measure whether they help, and use them safely. I care as much about prompt injection and over-reliance as about the speed-ups.
- Working across cultures. Most of my teams span countries and time zones, so clear written communication and shared ways of working matter a lot to me.
How I think about the job
I believe most team problems are system problems, not people problems. I would rather fix an unclear process than blame the person caught in it. I take ownership when something goes wrong, say so openly, and try to learn from it. I also like to coach more than I like to instruct: ask a good question, then let the person find the answer.
Who this blog is for
Engineers wondering whether management is for them, new managers in their first year, and experienced leads who want to compare notes. Nothing here is theory I haven't tried. Where I'm drawing on someone else's research, I link to it, and where I got something wrong, I say so.
If a post helped or you disagree with it, I'd like to hear from you. The best way to follow along is the Sunday letter below.