Someone on my team asked me recently whether they should move into engineering management. Strong senior IC — technically excellent, good communicator, starting to feel the ceiling.
Three years ago my answer would have been a qualified yes. Today it’s different.
Not because management has become less important. It hasn’t. But because the calculus has shifted in a way most career advice hasn’t caught up with.
The Default That No Longer Makes Sense
The traditional logic for going into engineering management was leverage. An Individual Contributor (IC) reaches a ceiling on individual output. Management becomes a multiplier — you stop writing code and start making other people more effective. The career value proposition is tied to scope: more people, more impact, more seniority.
That logic made sense when the leverage an individual could achieve was bounded by time and cognitive bandwidth. When one person could only do so much, scaling through people was how you scaled output.
That constraint is dissolving. Senior ICs who’ve genuinely integrated AI into how they work are delivering outputs that would have required a small team two years ago. Gregor Ojstersek noted this recently: AI tools are shifting the leverage point. The senior IC who used to hit a ceiling is now a force multiplier in their own right.
Which means the “I’ve hit my ceiling, time to manage” move is no longer the obvious one. The ceiling moved.
What Actually Changes When You Become an EM
When you become an engineering manager, you stop writing code. That’s the most obvious change, but it’s not the hardest one. The hardest change is that your success is no longer measurable by the quality of your own work. It’s measured by the quality of other people’s work, over a time horizon much longer than a sprint.
You become a context-builder, a blocker-remover, a career-shaper. The feedback loops are long. The rewards are mostly invisible. The frustrations are immediate and interpersonal.
There is real satisfaction in watching someone on your team solve a problem they couldn’t have solved six months ago. In seeing a team you’ve built function with the kind of trust that makes hard problems easier. In running the kind of 1:1 that genuinely changes someone’s trajectory.
But that satisfaction requires genuinely caring about those things — not as a means to an end, but as the actual point of the work.
The people who go into management because they want more scope or a bigger title, then discover they don’t actually want to spend their weeks in difficult conversations about performance and growth — those are the managers who do the most damage. They resent the work, and the team absorbs that resentment.
The New IC Story
Here’s what’s changed.
A senior IC who is genuinely AI-native — who can prototype, architect, and ship with AI as a co-pilot — is not operating at the ceiling they would have hit three years ago. They’re operating at a substantially higher ceiling, and it’s still rising.
The AI-assist numbers being reported from the most AI-native engineering teams are no longer outliers. They’re a direction signal. The senior IC who invests in that capability compounds differently than before. The leverage case for management — “you can only do so much alone” — is weaker than it was.
That doesn’t mean IC is always the right path. But it means the choice between IC and EM is more genuinely a choice now. Not a de-facto escalator.
My Honest Answer
So what do I actually tell people when they ask?
Go into management if — and only if — you find genuine satisfaction in other people’s growth. If watching a junior engineer solve something hard gives you the same kind of satisfaction that solving it yourself used to. If the interpersonal complexity of teams feels interesting rather than draining. If you want to build something through people, not just alongside them.
Don’t go into management because you’ve hit a ceiling. Raise the ceiling first. If you’re a strong senior IC in 2026 who hasn’t seriously invested in working with AI, that’s your next move — not a people management role.
Don’t go into management because the title reads more senior. Titles drift. The work doesn’t.
And don’t go into management because no one told you the IC path goes further now than it used to.
It does. The question is what you actually want to do with it.
This post was prompted by Gregor Ojstersek’s recent piece on whether the engineering management route still makes sense in 2026.
Leave a Reply