Questions we answerHiring and headcount
Should I hire a junior or a senior?
Seniority is a decision about how much definition the role comes with. A senior defines the work; a junior needs it defined, and someone with time to do that.
Free · a few minutes · starts from “I think we need another person”
The short answer
Hire senior when the work is ambiguous, when it has to be owned from day one, or when nobody in the team could supervise someone learning it. Hire junior when the work is well defined, when someone has genuine time to teach, and when you are investing over a year rather than solving a problem next month. The constraint people underestimate is supervision: a junior hired into a team with nobody to teach them is an expensive way to reproduce the gap you started with.
This is usually debated as a budget trade-off — two juniors or one senior — which misses the thing that actually decides it. Seniority is about how much ambiguity the person can absorb, and how much definition they need in return.
A senior hire is partly a purchase of judgement: they will decide things you have not decided yet. A junior hire is partly a purchase of future capacity, and it comes with a bill for attention now.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- You can state the work clearly, and the main constraint is hours rather than judgement.
- Someone in the team is good at the work and would enjoy developing another person.
- The value of the role grows over years rather than being needed in full next quarter.
Signs it's something else
- Nobody can describe what good looks like, which means nobody can supervise it either.
- The role is expected to set direction as well as execute.
- Everyone who could teach is already the bottleneck.
What's usually behind it
- A budget that will stretch to one experienced person or two less experienced ones.
- Work that nobody has fully defined, where a senior is being asked to define and do it.
- A team that has grown quickly and has nobody with time to supervise anyone.
What people usually get wrong
- Hiring two juniors to save money into a team with no supervision capacity.
- Hiring a senior to do work that is fully defined and mostly execution, then losing them to boredom.
- Treating seniority as a proxy for speed — an experienced person in an undefined role is slow too.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Experienced hire
The work is ambiguous or must be owned immediately, and nobody internal can define it.
Junior or early-career hire
The work is defined, someone has time to teach, and the horizon is a year or more.
Develop someone internal
Somebody is already close and the main thing missing is time, support or a mandate.
When doing nothing is the right call
If the honest answer is that nobody has time to supervise and nobody has defined the work, neither hire will go well. Spending a month defining the role is more valuable than either, and it usually changes which one you were going to make.
What the diagnostic asks
- What the new person would mainly add: capacity, a missing skill, or both.
- Whether anyone internal is close to the work already.
- How soon this needs to be sorted.
- Whether the hire is fundable, or fundable only at a stretch.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
Develop
Build the capability in someone already in the team, with time and support.
Specialist support
Bring in a freelancer, consultant or specialist for a defined piece of work.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
What changes the answer
- Work that has to be owned immediately, with nobody to define it, points senior.
- A defined process and someone with time to teach points junior.
- A genuinely missing capability the team cannot supervise points senior regardless of budget.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- Should I hire a graduate?A graduate fits where the work is learnable, somebody has time to teach, and the capability is needed for years rather than months. You are buying potential and paying for it in supervision rather than salary.
- What should my next hire be?Start from the constraint rather than the wish list. The right next hire is the one that releases the most work or removes the largest risk — which is often not the role that feels most overdue.
- We have a skills gap. Should I train, hire or bring someone in?It depends on how long you need the skill, how soon, and whether anyone in the team is close to it. Each answer points at a different route.
- Should I promote internally or hire a manager?Promotion keeps context and risks losing a good contributor; hiring brings experience and starts from zero context. The deciding factor is usually support, not talent.
- Should I hire another salesperson?Only once you know whether the constraint is demand, conversion or capacity. Another salesperson adds capacity; it does not on its own create a pipeline or fix a way of selling that is not working.
- Should I hire full-time or contract?Contract buys speed and information; permanent buys accumulation. The right answer depends on how durable the need is and whether you need the knowledge to stay.