Not everyone who gets good at this job wants to manage people, and not every team needs another manager. But “stay an IC” can quietly turn into “stay where you are,” because the case for the next title is much easier to make when you can point to a team you’re now running. Advancing without managing means building a different kind of evidence — and most people wait for someone else to define what that evidence is instead of naming it themselves.
What the case for the next level actually rests on
The scope that justifies a manager’s next title is legible at a glance: more people, more budget, more reports. The individual-contributor case has to be built out of less obvious material — the size and ambiguity of what you’re trusted to own end-to-end without someone checking your reasoning first, and how often you’re the one other people escalate to when a case doesn’t fit the usual pattern. That’s real scope, but unlike headcount it doesn’t show up on an org chart, which means it only counts as evidence if someone writes it down. The same discipline behind keeping a decision log pays off doubly here: a record of the calls you made and why becomes the concrete material for building the case for a title that has no team size to point to instead.
Building influence without a reporting line
Influence on this track looks like other people adopting your judgment without being told to — a convention you set for how your product area handles a certain kind of submission question, a review comment pattern colleagues start using on their own drafts, a newer hire who comes to you first and your manager second. None of that requires a reporting line, but it does require being specific about it when the conversation about the next title comes up: “people come to me” is vague, while “I set the team’s approach to X, and it’s now how three other people handle it too” is evidence. This is the same pattern behind teaching a colleague what the work actually involves, just aimed upward into a title case instead of outward into someone else’s ramp-up.
Where this goes wrong
Assuming visibility happens on its own
Good work that only you observed doesn’t count as evidence in a room you’re not in. If nobody else can describe what you own, the case has to be made explicitly, not assumed.
Confusing busy with senior
Being the person everyone routes questions to isn’t the same as being the person whose judgment carries the room on a hard call. The second is the actual bar; the first is just throughput.
Not asking where the track actually ends
Some companies have a real senior-to-principal-to-staff ladder past the point where headcount stops mattering; others quietly cap the IC track two levels up. Find out which one you’re in before spending years aiming at a title that may not exist where you work.
None of this means the management track is the wrong call, or that staying an IC is automatically the harder path. It means the evidence for the next level looks different when there’s no team size attached to it, and that difference is worth naming out loud — to yourself, and eventually to whoever decides the next title — rather than assuming the work will speak for itself.
Sources & further reading
- Regulatory Academy — The Regulatory Affairs Career Ladder, Explained regulatoryacademy.com
- Regulatory Academy — How to Build the Case for a Promotion regulatoryacademy.com
- Regulatory Academy — The Case for Keeping a Regulatory Decision Log regulatoryacademy.com
- Regulatory Academy — Moving From Individual Contributor to Manager regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.