Manager or IC: Three Questions to Ask Yourself Honestly
Somewhere around senior/staff level the IC track and the management track fork. Most people make this choice passively — the boss asks you to take the team, or nobody else on the team is a plausible candidate — but it shapes the next five to ten years: what your days look like, which skills compound, what exits you have.
The most common reason people choose wrong is that they assume management is the higher rung. That belief runs especially deep in Chinese tech. In reality these are two parallel tracks. Different work, different wiring.
Three Myths to Kill First
Myth 1: management outranks IC
No. On big tech comp bands, an M and an IC at the same level make roughly the same money — top ICs often make more. On the M side pay tracks the size of the org you run; on the IC side it tracks the reach of your technical influence.
Myth 2: once you manage, you can't go back
Half true. Within a year or two you can still switch back. Past three years it gets hard — not because anyone forbids it, but because your technical instincts have gone stale.
Myth 3: the IC track is the safe one
It isn't. The ceiling on the expert track is that a company only has room for a handful of them. The day your technology gets deprecated or your org gets restructured, the "expert" label devalues overnight. Demand for people who can run an org is, comparatively, steadier.
Three Questions, Answered Honestly
Q1: You see a hard technical problem. What's your first instinct?
- A: your hands itch, you want to go solve it yourself
- B: you start thinking about who should solve it and how to get it moving
If you're honestly an A, forcing yourself into management will hurt. The job is swallowing "I could just do this faster myself" every single day — handing it off, watching someone go slower, correcting after the fact. For a technically twitchy person that's daily torture.
If you're a B, you're already framing problems the way managers do.
Q2: Which lands better — shipping something yourself, or watching someone grow because of your coaching?
- A: shipping it yourself
- B: watching them grow
A is IC wiring. B is manager wiring.
"Both" is not an available answer. Most people say both, but one of them satisfies you noticeably more. Answer that honestly, because it decides where your energy comes from every day for the next five years.
Q3: When you're in conflict with someone, what's your reflex?
- A: avoid it / concede / bury it in output
- B: go at it / resolve it / push hard when you have to
Seventy percent of management is conflict — between your reports, across orgs, with your boss, with your reports, with product. You have to start the hard conversations, not dodge them.
If you're an A, management will grind down your mental health over years. This isn't a "you'll get better with practice" thing. It's temperament.
Three Situations, Three Answers
You got voluntold into a lead role
Give it 6-12 months, seriously. If after a year you've found zero satisfaction in the work and your technical edge is visibly dulling, tell your boss straight and move back to IC. Switching back early is much easier than switching back late.
You want to manage, but there's no open headcount
Don't chase the title. Stay an IC and take the de-facto leadership work — project lead, mentoring new hires, running cross-team coordination. All of it is management preheating, and none of it costs you anything on the IC ladder.
You're an IC and you envy what managers make
Money shouldn't be the primary input. But if it's your actual motive, just admit it — then go check whether M and IC at the same level in your company really do have a meaningful gap. In most big tech companies they don't, which kills the financial case entirely.
The Thing Nobody Says
The best position isn't "pick a lane." It's "tried both early."
The ideal shape:
- Through senior, stay IC and build real technical depth
- Around the staff transition, do one 1-2 year stint as a line manager with 5-10 reports — not to switch tracks, but to learn what the world looks like from that chair
- Then decide from actual experience: stay M, go back to IC, or run hybrid as a tech lead
People who take that path have both muscles, and the most optionality later.
Closing
Don't let "management is more senior" push you around, and don't let "I just like writing code" keep you comfortable. Answer the three questions honestly and the result gets obvious fast. Almost everyone who picks wrong picked wrong because they never actually asked.