Should you go back to IC? A framework for making the decision

The question itself is diagnostic

Engineering managers at month 12 to 24 ask this more than any other group. That timing is not random. It maps exactly to the window when the initial enthusiasm has worn off, the learning curve is still steep, and the results aren't yet visible enough to feel like proof.

Before you answer the question, answer a smaller one: are you considering going back because management is wrong for you, or because you haven't had the tools to do it yet?

Signs it's a capability gap, not a fit problem

• You like your team but don't know how to help them
• 1:1s feel awkward because you don't have a structure for them
• You avoid hard conversations because you don't have a framework
• You feel productive when you code and unproductive when you're in meetings
• You haven't gotten meaningful feedback on your management

These are learnable. They're common at months 12-18 and they're solvable with the right input.

Signs it might actually be a fit problem

• You feel genuinely energized by individual contribution and drained by coordination, not just temporarily
• You've had coaching, frameworks, and peer support — and the core work still doesn't engage you
• Your best moments in the last year were all IC-mode

Fit problems are real and the right answer is sometimes to go back. Management is not the right career for everyone and there's no shame in that.

How to run the decision

Give yourself a fixed window — 90 days — to get the tools you don't have. Make a list of the three management situations you handle worst. Get deliberate help on those three things. At the end of 90 days, evaluate with a clearer baseline.

A lot of engineers who ask this question make the decision too early, before they've had structured support. A lot of them come back to management later, better equipped. The ones who go back to IC with no period of structured coaching often find themselves asking the same question again from the IC seat.