One day, between beers, I caught myself asking a stupid question: what if I did this all the time?

The this was not writing code. It was the other stuff. Unblocking people, smoothing over an argument, defending my team from a manager who did not get it. I had been doing it on the side for years without really noticing. And that night I said it out loud: why could I not just be a manager?

Nobody I knew grew up wanting this. As a kid I never heard a friend say “I want to be a manager”. I heard “I want to be the boss”, which is not the same thing; a boss is not a manager, and a leader is neither. But that is another post.

In my case I never thought about any of it. I was not clear on what I wanted to be. I just walked step by step, focused on whatever was in front of me. A decent job, fingers crossed that I enjoyed it, and a good life around it. That was the whole plan.

So when does the transition really start? Not with a title. It starts the day you notice that working with people, and making their work a little better, satisfies you more than the code does.

The three usual reasons

I have watched a lot of developers make this move. Almost all of them came from one of three places. Let me lay them out honestly first; I will tell you what I think later.

The first is the natural. You genuinely like the tech. Shipping good code to production still feels great. But you also have a way with people, and it was always there. Sooner or later you feel the pull, and you start figuring out how to follow it.

The second is the accidental. You never planned this. You covered for someone who left, or a project pushed you into coordinating the team for a while. Management tasks landed on your desk by accident, and to your surprise, you liked them. That is usually good news: if it felt comfortable, you can probably grow the skills.

The third is the money. You do not really enjoy the management part. You are there, or thinking about going there, because it looks like the only door to a better salary. And of course we want more money; there is nothing wrong with that.

The money trap

Here is where I want to slow down, because the third reason is not really about you. It is about how our industry has worked for years.

For a long time the only ladder went up through management. Want a raise? Become a lead. Want the lead title to mean something? Manage more people. Growth and management were treated as the same road, so the “natural” next step for a good developer was to stop developing. Not because anyone needed another manager, but because that was the only box the salary lived in.

I have watched what that costs, more than once. A brilliant engineer gets promoted into a role that needs a completely different set of skills; skills they never asked to build and are not interested in building. The promotion looks like a reward. It slowly turns into a quiet frustration, for them and for the team they now lead. That is how you manufacture a bad manager out of a great engineer.

So be honest with yourself. Do you actually want that job, and do you know how to do it? If the answer is “I just want to earn more”, then say exactly that, and ask for more money. You can go deep and grow for years in a technical role without ever managing a single person. Seniority is not the same thing as authority over people.

The only reason that lasts

So what does make the move worth it? For me it comes down to one thing, and it is not the title or the pay. It is a genuine interest in the human, not just the engineer.

We are technical people. We are pushed to deliver, all the time. But underneath the results we are still people, with the same fears and feelings as everyone else, and most of the time nobody at work treats us that way. Traditional leadership tends to ask for results while ignoring the technical realities beneath them. When leaders don’t understand the work, they struggle to grant the autonomy and trust engineers need to perform. Ultimately, I think this applies everywhere: a lack of understanding leads directly to a lack of trust.

For years I lived in hybrid roles: writing code with one hand and, with the other, doing the thing nobody had asked me to do. I ended up in the conversations more than in the commits. Finding the agreement that unblocked two people who had stopped talking to each other. Sitting between the team and a manager who was “challenging” our work, and quietly defending it. Turning a tense room into one where people could get on with their job.

I was good at it before I had a word for it. I built the kind of atmosphere where relationships got better and blockers melted, and people simply worked better.

“Manager” was not a word that made me feel good. It brought up mediocrity, bureaucracy, politics, and authority for its own sake. Then I realized how unfair that was. There are good managers out there. I could be one; the kind I would have wanted above me.

That was the moment. Engineers are humans dealing with technology, and it turned out I cared more about the human than the technology. I wanted to work with the person behind the engineer.

So here is the one thing I would tell you; make this move if you care about people, and make it for them, not for the raise or the badge. And if you do not, stay technical, and stay proud of it. Both are real growth. Only one of them should be called management.