the senior ic who isn't a lead

most engineering ladders have two columns: management track and ic track. the ic track is usually drawn parallel to management, with corresponding levels. on the diagram. in practice, the senior ic who isn’t a tech lead is invisible — they don’t run a team, don’t run a project, don’t have a recurring meeting that justifies their existence on the org chart.

they ship a lot. that’s their job. will larson’s staff engineer archetypes calls this person the “solver” — the one who tackles the hardest scoped problem and doesn’t run a team. most ladders i’ve seen acknowledge this archetype on paper and then fail to staff it.

the problem isn’t the role, it’s the staffing

the problem isn’t that the role is missing. the problem is that it’s understaffed because companies don’t know what to do with senior engineers who aren’t running anything. promotion rounds favour visible coordination work. the senior ic who shipped three hard things alone gets passed over for the lead who shipped one easy thing with a team.

what the role actually does

• they take the hardest piece of any project — the algorithm, the migration, the integration — and own it end to end.
• they raise the floor. their code becomes the reference. juniors learn from reading it. mids copy patterns from it.
• they say no to scope. they have the standing to push back on a feature request because they’ve seen what it’ll cost three quarters from now.
• they don’t run meetings. they’re in two or three a week.

the senior ic role exists as a counterweight to manager-creep. without it, every engineer over a certain seniority becomes a manager, and the organisation loses the people who can hold a hard codebase in their head. you can’t replace that with team velocity.

if your ladder doesn’t have a real, distinct, well-staffed senior ic track, you’re paying for management coordination overhead and losing the engineers who should have been keeping the system honest.