One of the easiest mistakes to make in a growing startup is confusing seniority with leadership.
Someone becomes increasingly valuable.
They understand the product.
Other people trust them.
They solve difficult problems.
The organisation grows.
Eventually somebody asks the obvious question.
Should they manage the team?
Sometimes the answer is yes.
Sometimes promoting them removes an outstanding individual contributor and creates an average manager at exactly the same time.
The same problem appears in external hiring.
A startup needs more seniority, so it searches for a "Head of", "VP" or "Director" when the real requirement is someone capable of solving unusually difficult problems.
Or it does the opposite.
It hires another strong individual contributor when the organisation has reached the point where coordination, direction and people leadership have become the real constraint.
IC hiring and leadership hiring overlap.
But they are not the same problem.
Startups get into trouble when they assess them as though they are.
Start with the constraint, not the title
Imagine an engineering team that is struggling.
Delivery has slowed.
The architecture is becoming more complicated.
Engineers disagree about technical direction.
The founder concludes that the company needs an engineering leader.
Perhaps it does.
But what if the underlying issue is simply that nobody on the team has enough technical depth to make the hardest architecture decisions?
Hiring a VP Engineering may introduce management without solving the technical problem.
A senior Staff or Principal Engineer could be far more valuable.
Now reverse it.
The team contains several very strong engineers.
Technical decisions are generally good.
But priorities change constantly.
Nobody gives consistent feedback.
Poor performance is being ignored.
Product and engineering are misaligned.
The founder spends half the week resolving disagreements.
Another exceptional engineer may improve output.
They probably will not solve the organisational problem.
That situation needs leadership.
This is why the first question should never be:
"What level do we need?"
It should be:
"What is currently preventing this team from being more effective?"
Great ICs create leverage through expertise
The strongest individual contributors have influence well beyond the work they personally complete.
A senior engineer may shape architecture used by the entire team.
A senior product person may untangle a problem that has blocked several squads.
A commercial IC may open a market others assumed was inaccessible.
An experienced recruiter may completely change how a business approaches a critical search.
Their leverage comes primarily through judgment, expertise and execution.
They do not need direct reports to be senior.
This is particularly important in startups because leadership titles are often introduced too early.
Someone becomes the most experienced person in a function and is automatically made Head of that function.
But being the best practitioner and being responsible for other practitioners require different motivations and skills.
Not everyone wants both.
That should be treated as perfectly normal.
Leadership changes what success means
Once somebody becomes a leader, their personal output becomes less important than the output of the group around them.
That sounds obvious.
In practice, many companies continue assessing leaders primarily through what they can personally do.
The best engineer becomes Engineering Manager.
The best salesperson becomes Sales Manager.
The strongest recruiter becomes Head of Talent.
Then the company is surprised when the transition is difficult.
Management introduces a completely different set of responsibilities.
Setting direction.
Delegating.
Giving feedback.
Hiring.
Handling underperformance.
Resolving conflict.
Creating clarity.
Developing people.
Communicating upwards.
Protecting the team from unnecessary noise while making sure it remains connected to the rest of the business.
Some outstanding individual contributors find this deeply rewarding.
Others find themselves spending less time doing the work they were brilliant at and more time in conversations they never particularly wanted.
That is not a failure.
It is a mismatch.
Startup leadership is unusually hands-on
There is another complication.
Leadership inside a startup rarely means stopping individual contribution entirely.
A Head of Engineering may still write code.
A Head of Product may personally run discovery.
A Sales Lead may still close major deals.
A Head of Talent may personally run the most difficult searches.
That is normal.
The important question is how the balance changes over time.
At ten employees, a functional leader might spend most of their week doing the work.
At fifty, that may be impossible.
Someone who loves the first version of the job may hate the second.
When recruiting leaders, startups therefore need to understand not only whether somebody can do today's job, but whether the direction of travel fits what they want to become.
This is particularly important when hiring people from larger companies.
Their current title may sound exactly right.
Their actual role may be completely different.
Titles travel badly between companies
A Director at one company can have more scope than a VP somewhere else.
A Head of Engineering might manage three people.
Another might manage eighty.
A Principal Engineer may be the technical authority for an entire platform.
Somebody with the same title elsewhere may simply be a very experienced developer.
This is why title matching is a poor way to recruit.
Scope is far more useful.
How large was the team?
What decisions did they own?
Who did they report to?
Did they hire?
Did they manage managers?
How close were they to customers?
How much budget did they own?
How much of their role was strategic versus hands-on?
What changed because they were there?
Those questions tell you far more than whether the title on their CV matches the title on your job description.
Leadership interviews need different evidence
IC interviews should usually focus heavily on the work.
Can this person solve the problems the role requires?
Leadership hiring has to go further.
You need evidence of how somebody behaves through other people.
Ask about a person they developed.
What did that person struggle with?
What did the leader actually do?
Ask about underperformance.
Not the polished success story.
The uncomfortable example.
When did they realise there was a problem?
How long did they wait?
What conversation did they have?
What happened next?
Ask about disagreement with another leader.
How did they handle it?
Ask about a decision their team disliked.
How did they communicate it?
Ask about something they delegated badly.
The best leadership interviews contain imperfection.
Real leaders have made hiring mistakes.
They have handled conversations badly.
They have held onto work too long.
They have promoted the wrong person.
They have changed their minds.
Someone who can discuss those moments clearly often tells you more than someone presenting an uninterrupted history of perfect leadership.
References become particularly valuable
References are useful for many hires.
They become especially important for leadership positions because much of leadership is experienced by other people.
A candidate can explain their management style.
A former direct report can tell you what that style actually felt like.
A peer can explain how they behaved when priorities conflicted.
A former manager can describe how much support they needed.
Do not use references simply to confirm employment.
Use them to test the picture that emerged during the process.
If the candidate says they are highly autonomous, ask about that.
If they claim to build exceptional teams, explore how.
If they say they handled a difficult organisational change well, speak to someone who experienced it with them.
Good references add context.
Do not make management the only path upwards
Companies contribute to this problem when leadership becomes the only visible form of progression.
If the only way for an excellent engineer, product person or commercial professional to gain status, compensation and influence is to become a manager, people will naturally move towards management whether it suits them or not.
Strong organisations create meaningful senior IC paths.
That may include Staff, Principal, Distinguished or other titles depending on the function.
The title itself matters less than the principle.
People should be able to increase their impact without accumulating direct reports.
Startups often think they are too small to worry about career architecture.
You do not need a fifty-page competency framework.
But you do need to make clear that leadership is a different responsibility, not simply the next rung of the ladder.
Founder transitions are part of this too
The distinction between doing and leading also applies to founders.
At the beginning, founders do almost everything.
Sell.
Recruit.
Define product.
Support customers.
Make technical decisions.
Solve operational problems.
Growth gradually forces a different job.
The founder has to stop being the best individual contributor in every function and start building an organisation capable of operating without their involvement in every decision.
That transition is difficult precisely because the behaviour that made somebody effective at the beginning can become the behaviour that limits the organisation later.
Good leadership hiring helps with that transition.
The wrong leadership hire can make it worse.
A founder who hires a senior leader but continues making every decision has created an expensive messenger.
A leader who arrives expecting complete control without understanding the founder's context will create friction just as quickly.
Both sides need clarity around decision ownership.
Decide what kind of leverage you need
That is ultimately the difference.
Strong ICs create leverage through expertise, judgment and direct contribution.
Strong leaders create leverage increasingly through other people.
Startups need both.
The challenge is recognising which form of leverage the organisation is missing.
If the hardest problems remain unsolved because the team lacks depth, hire expertise.
If strong people are underperforming because the organisation lacks direction, accountability or coordination, hire leadership.
If you genuinely need both, be explicit about it.
There are exceptional player-coaches who can operate across the line.
Just remember that the balance will change as the company grows.
Do not use a leadership title to solve an expertise problem.
Do not use another IC to avoid a leadership problem.
And do not assume that somebody becomes more senior simply because they manage more people.
The best startup organisations make room for both forms of impact.
The hiring process should do the same.