I've seen this play out more times than I'd like.
A brilliant engineer. Writes clean, elegant code. Solves problems nobody else sees coming. The team leans on them. Leadership notices. And then comes the reward: a promotion to engineering manager.
Six months later, they're miserable. Buried in one-on-ones, performance reviews, and sprint planning sessions. Their best work... the thinking, building, solving... is gone. Replaced by coordinating other people's work. The team has lost their best engineer and gained a manager who wishes they were somewhere else.
This isn't one person's story. It's a pattern baked into how most tech organizations operate. And it costs companies far more than they realize, in morale, in output, and in people walking out the door.
We Call It a Reward. It's Often a Punishment.
When someone excels in a technical role, the system has one response: move them up. And "up" almost always means managing people.
It's how we signal someone has arrived. Title changes. Pay bumps. A direct team to call their own. The implicit message: managing people is more valuable than doing the work yourself.
But these are fundamentally different jobs. Not a ladder... a fork.
Being a great engineer requires deep focus, pattern recognition, and holding complex systems in your head for hours at a time. You work largely alone, or in tight collaboration with a small group of peers who speak the same technical language.
Being a great manager requires patience, empathy, difficult conversations, and an ability to work through ambiguity with a wide variety of humans. You measure success not by what you build, but by what others build around you.
One person rarely excels at both. When we promote someone based on technical excellence, we're making an enormous assumption: the skills carrying them here will carry them forward.
They won't. The job description has changed entirely.
There's Research on This
Gallup has studied management selection across thousands of organizations. Their finding: companies fail to select the right person for management roles 82% of the time.
Eighty-two percent. Nearly every single time.
When Gallup asked U.S. managers why they got the job, the two most common answers were: success in a previous non-managerial role, and tenure. Neither tells you anything about management ability.
Gallup estimates only 1 in 10 people have the natural talent to manage well. Think about the management chain in your organization right now. Statistically, most of those people shouldn't be there. Not because they're bad people, but because nobody checked whether they wanted the job or were built for it.
And the financial cost is real. Organizations who select and develop talented managers achieve approximately 147% higher earnings per share compared to their competitors. Getting this wrong isn't a culture problem. It's a business problem.
The Cost Is Double
Here's what companies don't talk about enough. When you promote your best engineer to manager, you don't gain a new manager. You lose your best engineer.
Those aren't separate events. They're the same transaction.
The work this person was doing... the architectural decisions, the mentorship through code review, the debugging nobody else wanted to touch... now sits unassigned. Or gets distributed across people who aren't as good at it. Or falls to the newly-promoted manager, who's now trying to do two jobs and doing neither well.
Meanwhile, your new manager is learning leadership the hard way: through trial and error, on your team, on your watch. The people they manage are the test subjects.
Some grow into it. Many don't. And many leave entirely because managing people turned out to be nothing like what they signed up for when they chose a career in engineering.
You got rid of a great engineer and created both a mediocre manager and a retention problem. All in one decision.
The System Only Has One Track
The root of this is structural. Most organizations offer one progression path: individual contributor to manager.
Want more money? Become a manager. Want more prestige? Become a manager. Want to be seen as a leader? Become a manager.
For someone who loves coding, loves solving hard problems, loves building systems... this is a terrible deal. But they often take it anyway. Because it's the only deal on the table.
And then they're miserable. Or mediocre. Or both. And they start looking elsewhere.
The Fix Is a Second Track
The organizations getting this right offer two paths upward.
The IC track goes from senior engineer to staff engineer to principal engineer to distinguished engineer. Each level brings more scope, more autonomy, more influence, and more pay... without requiring you to manage people.
The management track is separate and intentional. It's for people who genuinely want to lead teams, who get energy from developing other people, who are willing to trade keyboard time for conversation time.
You recruit for these tracks deliberately. You don't assume your top performer wants to manage.
Some companies get this wrong by offering parallel tracks where they aren't equal. The IC track tops out at a lower salary band or a title with less prestige. Engineers see through this immediately. A "Staff Engineer" who earns less and gets less visibility than a middle manager is going to take the management path even when they don't want it.
If you're going to offer two tracks, they need to be genuinely equivalent. Same pay bands. Same access to senior leadership. Same signal to the organization: this person is valued.
How to Know If Someone Should Manage
Before promoting anyone into a management role, ask them directly: do you want to manage people?
Not whether they'd like a promotion. Not whether they want more money. Whether they want to spend their days on one-on-ones, performance conversations, hiring decisions, and team dynamics.
Watch for someone who already does these things without being asked. The engineer who mentors new hires on their own initiative. The one who runs meetings well, who notices when a teammate is struggling, who cares about the team's output more than their own velocity. Those signals matter.
Technical excellence is not one of those signals. It's the most common reason we promote people into management. It's almost completely irrelevant to whether they'll succeed there.
What to Do If You're Already There
If you've been promoted into management and you hate it, you're not failing. You're in the wrong role. Different problem entirely.
Name it. Tell your manager. Ask whether there's a path back to technical work at a senior level. Some organizations will say yes. Some won't. Staying in a role you're miserable at, pretending to be fine, helps nobody... least of all the team depending on you.
For those making these decisions: before you promote your best engineer, sit down with them and ask what they want. Not what they think you want to hear. What they want.
The answer might surprise you.