If the only path to more money and more say is “become a manager,” people take it who shouldn’t, and you get a mediocre manager and lose a great engineer in the same move. Fix the org’s comp structure before you let this be the default reason anyone chooses the track.

What each track actually asks of you day to day

	IC (Staff+)	Manager
Main output	Code, architecture, technical decisions	Other people’s output, unblocked
Success looks like	A hard problem solved well	A team shipping consistently, growing
Bad day	Stuck on a problem alone	A conflict between two people you can’t avoid
Skill that compounds	Technical depth	Judgment about people and priorities

Neither is a promotion over the other. They’re different jobs that happen to share a starting point.

The honest self-test

• Do you get energy from solving a hard technical problem, or from watching someone else solve one because you unblocked them? Both are real, but they’re different signals.
• When a teammate is struggling, is your instinct to fix their code or to have the conversation about what’s actually going on? Neither instinct is wrong, but one of them is the manager instinct.
• Can you be satisfied with a good week where you personally wrote zero code? If the honest answer is no, that’s real information, not a failure.

Try it before you commit

Ask to run point on a small project with one or two people reporting into the work, without giving up your IC role entirely, for a defined period, six to eight weeks. This gives you a real sample of the job instead of a guess, and it’s reversible if it’s not for you.

It’s reversible, but say so out loud

Going from manager back to IC gets treated as a demotion by default, and that stigma is the thing that traps people in a role they hate. If you’re the one deciding these tracks, say explicitly, in writing, to the whole team, that switching back is a normal, respected move, not a failure. Otherwise nobody will take you up on the trial period above, because they’ll assume it’s one-way.

The tell that you’re in the wrong track

If you’re a manager who’s still doing your best work at 11pm writing code instead of during the day managing people, or an IC who’s spending all their energy informally coaching teammates instead of shipping, the track and the actual work you gravitate toward have already diverged. That’s worth a direct conversation with whoever sets these tracks, sooner rather than after a year of resentment.

The actual decision criteria

Pick the track where your best days outnumber your worst days, evaluated honestly over a real trial, not the one that sounds more senior on a resume. Title inflation fixes nothing if the daily work makes you miserable.

---