A team grows past six or seven people, delivery starts to wobble, and the instinct is to hire a manager. It is a reasonable reflex but, increasingly often, it’s the wrong hire.
The problem being described is usually a lack of technical direction, rather than coordination: nobody owns the architecture, decisions get relitigated, and the same design arguments resurface every quarter. A manager won’t fix that, but a senior individual contributor will.
The market has already moved
This is not a contrarian position any more. SignalFire’s 2026 State of Tech Talent report found that senior IC and staff roles are growing as a share of hiring while engineering manager roles are flat or declining. Spans of control have widened with it, to around 12 engineers per manager at the largest tech employers and roughly 15 at startups.
The layer that thinned was middle management. What replaced it was a smaller number of managers doing less coordination, and senior ICs holding technical scope that would once have sat with a director.
What a senior IC does
The title varies – staff engineer, principal engineer, lead architect. The job is consistent: own the technical direction of something larger than a single team, make the decisions that are expensive to reverse, and raise the standard of everyone’s work without managing anyone.
In practice that means design ownership across services, unblocking other teams, writing the documents that settle arguments, and being the person who can say what the system will do under load. It is a leadership role. It just does not come with reports.
How to design the role so it works
- Give it real scope. A senior IC without a defined area of ownership becomes a floating reviewer. Name the systems, the domains, or the problems they own.
- Grant authority without headcount. If every architectural decision still needs a manager’s sign-off, you have hired an expensive senior engineer, not a technical leader.
- Make the ladder honest. If the IC track stops at senior while the management track runs to director, candidates will read that correctly and decline. Parity in level, pay and influence is the whole proposition.
- Be clear about what it is not. It is not a holding pattern for someone waiting on a management role, and it is not a reward for tenure.
Interviewing for it
The failure mode is interviewing a senior IC like a very good senior engineer. Coding exercises tell you little about whether someone can hold direction across teams.
Better approaches:
- Ask them to walk through a design decision they got wrong and what they changed afterwards.
- Ask how they brought a team round to an approach the team initially disagreed with.
- Ask what they would want to understand in their first month before changing anything.
You are testing judgement, influence and restraint, in that order.
When you do need the manager
Sometimes the problem really is people. If delivery is stalling because priorities are unclear, performance is unmanaged, or the team has no career conversations, that is a management gap and a senior IC will not close it.
The question worth asking before the requisition goes out is simple: is this team unclear about what to build, or unclear about how to work? The answers point at different hires.
Talk to Intec Select about senior technical hires
Senior IC roles are a harder brief than they look, because the strongest candidates are usually well placed and assessing you as closely as you are assessing them. We can help you shape the role and reach the people who will not respond to an advert.
