How to become an engineering manager.

First, whether you want it

The honest question is not whether you are ready. It is whether you want this job, or whether you want the recognition that people assume comes with it. Those are easy to confuse, because in most organisations management is the only visible way up, and wanting to progress feels identical to wanting to manage right up until the moment you are doing it.

The tell is what you would miss. If the idea of not writing code again fills you with relief, that is useful information. If it makes your stomach drop, that is also useful, and it does not mean you are not leadership material. It means the senior individual contributor track may be the one that actually fits, and the fork between those two is worth taking seriously rather than defaulting through. I have written about the choice between staff engineer and engineering manager in more detail, including why it is not a promotion in either direction.

I am not the best software engineer on my team, or on any team I have managed. I am proud of that. If that sentence reads as a loss to you, sit with it for a while before you take the job.

How the decision actually gets made

Promotions into management are rarely decided in the conversation where you hear about them. By the time a director asks whether you would consider it, other people have already been asked what they think of you, and they answered from whatever they happened to have seen.

I have promoted engineers at every level from junior through to principal, and I have sat in the calibration conversations where a promotion has to be signed off by other managers. What I want when I walk into that room is simple. When I go to promote you, I want other managers to question why we had not done it already, and not be having to convince them.

That is the whole game, and it is mostly built long before anyone mentions a title. It comes from work other teams noticed, from being the person who made a difficult project legible to people outside engineering, from mentoring somebody who then got promoted themselves. None of that is self promotion. It is making sure the people who will be asked about you have something to say.

I spent years of my own career chasing promotions built on promises from people who could not articulate what the next level actually required. If your manager cannot tell you specifically what would make the case, that is not you failing to be ready. Ask for it in writing, and treat the inability to produce it as information about the organisation rather than about you.

The interview, and the thing that stops people

Engineering manager interviews test something different from engineering interviews, and the shift catches people out. They are not checking whether you can design the system. They are checking whether you can hold a difficult conversation, whether you can be honest about a failure, and whether you have thought about people as a subject rather than as an obstacle to delivery.

If you have never managed anyone, that is workable, and it is a more common starting position than most job specs imply. What panels are listening for is evidence you have already been doing parts of the job without the title. The questions first-time manager panels actually ask goes through what they are scoring and how to answer without stretching a mentoring story further than it goes.

The part worth naming is what happens before the interview. As a junior I had one booked with a well-known stock broker in London. Good pay, real training, the kind of opportunity I had been working towards. And as the date got closer I got less excited every day. I was crawling the job spec, the careers site and Glassdoor every thirty minutes, looking for something that would justify cancelling. I was about to phone the recruiter with an excuse they had heard ten times that week when I worked out what was actually going on. It wasn't me making that phone call, it was fear.

I used it to drive revision instead. I got the job, and it turned into one of the greatest opportunities of my career. I mention it because the same thing happens to engineers in front of management interviews, and it does not present itself as fear. It presents itself as a sensible reconsideration of whether the timing is right.

What kind of manager you are going to be

You already have a default. It was set by the managers you have had, the ones you admired and the ones you swore never to become, and it will show up in your first month whether you have thought about it or not.

Most engineering managers land on one of five instincts. The protective one, the delivery one, the technical one, the mentoring one, the diplomatic one. Each has a genuine strength, and each has a blind spot that grows out of the same instinct, which is why it is so hard to see in yourself. The five types of engineering manager sets out all of them alongside the specific situation where each one costs you.

Knowing which one you default to before you start is worth more than any amount of reading about management in general, because it tells you which advice you can safely skim and which advice is written specifically about the thing you are going to get wrong.

Final thoughts

None of the above tells you whether you will enjoy it, and I do not think that is knowable in advance. The first year is genuinely hard for almost everyone, including people who turn out to be very good at it, so struggling early is not the signal people take it for.

What did surprise me is how little of the job is the part you can prepare for. You can rehearse the interview, read about feedback, and plan your first ninety days, and then the actual difficulty turns out to be sitting with someone who is upset and not rushing to fix it. Nobody interviews for that, and it is most of the work.