The most common way to create your first engineering manager is to promote your best engineer. It's also one of the riskiest moves in tech, because the transition fails far more often than leaders admit, and when it fails you can lose two people: the manager who quit, and the great engineer who no longer exists.
Key Takeaways
- By one experienced leader's estimate, at least half of new engineering managers eventually retreat to an IC role (First Round Review).
- Managers account for about 70% of the variance in team engagement, so a bad manager hire poisons the whole team, not one seat alone (Gallup).
- Great IC skills don't automatically transfer to management.
- De-risk it: make the choice deliberate, support it heavily, and cover the IC capacity you're removing.
The Failure Rate Nobody Talks About
Marcel Weekes, an experienced engineering leader, put it bluntly in First Round Review: at least half the time, newly minted engineering managers eventually retreat back to being an IC. As he noted, if a service failed at that rate, you'd run a postmortem. Yet companies keep making the same bet: take the strongest IC, hand them a team, and hope.
The core mistake is assuming the skills transfer. As Pat Kua has written, organizations routinely set new managers up to fail by promoting them and then providing no support.
Why the Stakes Are Higher Than One Role
Here's what makes a botched EM promotion so costly. Gallup, analyzing 27 million employees across more than 2.5 million work units, found that managers account for roughly 70% of the variance in team engagement (Gallup). They call it "probably" their most profound finding ever. In plain terms: if you know nothing about an employee except who their manager is, you can predict their engagement with surprising accuracy.
So a first-time manager who's struggling doesn't just underperform in one seat. They drag the engagement, and eventually the retention, of every engineer under them. The bad promotion can quietly cost you the team.
Why Great ICs Don't Automatically Make Great Managers
The traits that make someone an exceptional engineer, deep focus, solving problems yourself, technical judgment, are not the traits of a good manager. Management is about growing other people, communicating, and making decisions through a team. Those are learnable, but they're different skills, and being the best coder on the team is no guarantee of them.
| What made them a great IC | What management actually needs |
|---|---|
| Solving it yourself | Growing others to solve it |
| Deep individual focus | Context-switching for the team |
| Technical judgment | People judgment + communication |
A Concrete Version
Your best engineer, call her Ana, gets promoted to manage the five people she used to sit with. Nobody trains her, because she's smart and will "figure it out." Three months in, she's drowning: still doing her old IC work at night because she can't let go, doing management badly during the day because no one showed her how, and her five reports are quietly frustrated because 1:1s keep getting cancelled. The Gallup math kicks in: engagement on the team slides. Six months later Ana asks to go back to IC (the coin flip landed where it usually does), and now you've spent half a year turning your strongest engineer into a burned-out one and dinging five other people's morale.
The Honest Counterpoint
None of this means "don't promote from within." Internal promotions often make the best managers, because they already have the team's trust and the technical credibility to lead engineers. The failure isn't the promotion. It's the unsupported promotion: handing someone a team with no training, no coaching, and no backfill, then acting surprised when the coin flip lands badly. Promote from within, but treat it as onboarding someone into a genuinely new job, not as a reward you can set and forget.
How to De-Risk It
Three moves lower the odds. First, make it a deliberate choice, not a default reward for tenure, and confirm the person actually wants to manage (plenty of great engineers don't). Second, give real support: mentoring, training, and a manager who coaches them through it. Third, cover the IC capacity you're removing, because promoting your best engineer means losing your best engineer's output.
That last point is where augmentation helps: bring in senior IC capacity to backfill the hands-on work while your new manager learns the role, so you're not down a strong engineer and a functioning manager at the same time. See available engineers.
Frequently Asked Questions
How often does the IC-to-manager transition fail?
By one experienced leader's estimate, at least half of new engineering managers eventually return to an IC role. It's a high-failure transition that rarely gets a postmortem.
Why is a bad manager promotion so costly?
Gallup found managers account for about 70% of the variance in team engagement. A struggling first-time manager doesn't just underperform in one seat; they drag the engagement and retention of the whole team under them.
Why do great engineers struggle as managers?
The skills are different. Individual technical excellence doesn't automatically translate into growing people, communication, and leading through a team.
How do I avoid losing my best engineer to a failed promotion?
Make the move deliberate, provide real support and mentoring, and backfill the IC capacity you're removing so the team keeps shipping while the manager learns.
The Bottom Line
Promoting your best engineer to manager is a coin flip that can cost you two roles at once. Make it deliberate, support it heavily, and cover the IC capacity you lose, and you turn a risky default into a real decision.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers in 72 hours. See available engineers.
