Skip to content

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.

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.