The real reason engineering managers burn out at 18 months

June 15, 2026

The promotion nobody prepares you for

You were the strongest engineer on the team. That's why you got the role. Nobody mentioned that engineering skill and management skill are almost entirely unrelated.

At month six, you're still writing code because it feels productive. Your 1:1s are status updates. You have no framework for giving hard feedback, so you give soft feedback that lands as no feedback at all.

By month 18, you've been burning the same fuel for too long. You're working harder than you did as an IC and producing less visible output. The team doesn't trust you yet because trust takes longer to earn than a quarter. And you've started wondering whether you made a mistake.

What's actually happening

The 18-month burnout pattern is structural, not personal. Here's the sequence:

  1. Months 1-3: You do IC work while learning the management job. Double the workload.
  2. Months 4-9: You give up IC work but don't yet have management leverage. Output feels lower than before.
  3. Months 10-18: Team dynamics crystallize. If you haven't built trust and delegation by now, the gap compounds.

The engineers who survive this transition without burning out are almost always the ones who found a peer who'd done it before — someone who could tell them that the confusion is normal, that their team is probably doing fine, and that the job changes completely every six months for the first two years.

The fix isn't harder work

It's recognizing that you are learning a new job. Give yourself permission to be a beginner at it. Find people who've run teams at your stage and company size. Use frameworks for the hard conversations instead of improvising them every time.

That's what the first 90 days of structured coaching is for. Not inspiration — a set of tools specific to the IC-to-manager transition.

Keep reading

← Back to blog

Built with