The promotion is a career change, and nobody tells you

You spent years getting good at one job, and on Monday you started a different one. Nobody announces the change. It took one of my reports to tell me.

24 August 2026 · 6 min read · Growing engineers

I learned what my new job was from someone who reported to me.

We were in a one-on-one. I was working through where delivery stood, what I thought the approach should be, which pieces I would pick up myself. He listened to all of it. Then he said he needed me to help him grow, rather than be the one at the front delivering.

He was right. I had not seen it, and he had been watching it for weeks.

The instinct that got you here

Nobody is promoted into leading engineers for being bad at engineering. You are promoted because you were good at the work, which means the habits that earned you the role are strong, practised and immediately available. They are also the wrong ones now, and nothing about the first week tells you that.

For my first month I defaulted to working as an individual contributor. I looked at my immediate work. I did not look at the team, and I did not look far enough at the product. If you had asked me at the time, I would have said I was busy and delivering, and both would have been true. I would have missed that I was delivering the wrong thing.

This is the part that catches people, and it caught me. The failure does not feel like failure. It feels like competence. You are shipping, you are unblocking, you are the person who knows. The signal is quiet precisely because the old measure is still giving you good news.

Solution mode

The habit I held on to longest was technical direction.

Someone would bring me a problem and I would go straight into solving it. Not rudely, not by taking the keyboard, but by arriving at the answer out loud while they were still describing the question. It felt like help. It felt like exactly what an experienced person should offer.

What it actually did was end the thinking early. Every time I supplied the answer, I took away the thing the person had come to do, which was work it out. Do that often enough and you have trained a team to bring you problems instead of solutions, and then you wonder why nothing moves unless you are in the room.

The role I should have been playing was supportive and enabling. That sounds soft until you try it, and then you discover it is much harder than being the one with the answer. Sitting with someone’s half-formed approach without correcting it takes more discipline than correcting it does.

The measure changed, and there was no announcement

Here is the thing nobody puts in the letter.

You spent years being measured on what you produced. As of the day the role changed, you are measured on what your team produces, and on what the people in it become. Those are different jobs. They need different skills. There is no handover document and, in most organisations, no moment where anyone sits you down and says the measure has moved.

So you go on optimising for the old one. It is the only scoreboard you can see.

That is why I call this a career change rather than a promotion. A promotion suggests more of the same with a larger title. This is not that. You have started a new profession, on the strength of being good at a different one, with no training and an audience of people whose working lives now depend on how quickly you pick it up.

Stepping back is not stepping away

The correction I needed was to step back and create the space for the team to work on the solution.

I want to be careful here, because “step back” is easy to hear as do less, care less, or disappear into meetings. It is none of those. Stepping back is active work, and it looks like this.

You state the problem and the constraints clearly, and then you stop talking. You let a silence run longer than is comfortable. When someone brings you a direction you would not have chosen, you ask what they considered before you say what you think, and quite often you do not say what you think at all. You take the interesting problem you were looking forward to and you give it to the person who will learn most from it. You make it safe to be wrong in front of you, which mostly means being visibly fine when someone is.

None of that is passive. All of it is harder than solving the problem yourself, and slower in the first month.

It feels like failure for a while

This transition feels bad before it feels good, and it is worth saying so plainly.

Your output drops to nearly nothing you can point at. You end weeks having written no code, made no design, shipped no feature, and the old scoreboard reads zero. There is a stretch of months where you are doing the new job properly and it still feels like you are getting away with something.

What helped me was changing what I looked at. Not “what did I produce this week” but “what moved that would not have moved without me, and who is further along than they were”. Those are slower signals and they are less satisfying, and they are the real ones.

The part I keep coming back to

It was my direct report who told me.

He had every reason not to. He was newer, he was more junior, and he was telling his manager that his manager was in the way. That he said it anyway is the only reason the first month did not become the first year.

Two things follow from that, and they are the closest thing to advice I have.

If you have just moved into leading engineers, the information you most need is held by the people you lead, and they will only hand it over if it is safe to. That safety is built well before the conversation where it matters, in how you react to much smaller things.

And if you are the engineer watching your new lead do this: they probably cannot see it. Not because they do not care, but because the habit is invisible from inside it. Saying something is a real risk and I will not pretend otherwise. But the person I was that year is grateful to the person who took it.