Back to Resources
Hiring 7 min read

What to decide before you post the job

Most hiring problems are planning problems that surface later. Six decisions made before the job goes live will save you more time than anything you do afterwards.

A hiring plan sounds like something only large companies need. It is not. It is the half hour before you post the job, spent deciding six things, and it is the difference between a process that converges and one that goes round in circles for two months before someone says "actually, do we even need this role".

The symptoms of skipping it are familiar. The shortlist looks nothing like what the hiring manager expected. Interviewers ask different questions and reach incompatible conclusions. The offer gets stuck because nobody established the budget. The role is re-scoped halfway through and everyone quietly restarts.

1. Establish that the role is the answer

The first question is whether you should hire at all. Not as a cost-cutting reflex, as a definition exercise.

Work is arriving somewhere and not being done. Before you package that into a job, ask what is actually happening. Is the work permanent or is it a six-month project. Is it one coherent role or three people's overflow bundled together because that is who complained. Would a process change or a piece of software remove it entirely. Is the real answer a contractor.

Roles assembled from the leftovers of three teams are the hardest to fill and the fastest to turn over, because nobody can do all of it well and the person who takes it discovers that in month three.

2. Write the real requirement

Now define the role properly: outcomes first, then the capabilities those outcomes demand, then the genuine must-haves. This is the job description, and it is covered in full in how to write a job description.

Two things to settle here that people leave until too late.

What does good look like at twelve months. Write the sentence. If the hiring manager and HR write different sentences, you have found the disagreement now rather than at final interview.

What are you willing to trade. You will not get everything. Decide in advance which of the must-haves you would flex on and which you would not. Making that call under time pressure with a candidate in front of you is how bars slip.

3. Set the scorecard before you meet anyone

Four or five criteria, a defined rating scale, and the questions that will test each one. Written down, agreed, before the first interview.

Doing this in advance is what makes interviews comparable. Doing it afterwards is rationalisation. The structured hiring playbook covers how to build one.

The useful side effect is that writing the scorecard forces the requirements to become concrete. It is easy to say "strong stakeholder management" in a job description. It is hard to write the question that tests it, and if you cannot write the question, the requirement was never real.

4. Name the panel and give each person a job

Decide who is involved, what each person is assessing, and who decides.

Panels fail in two directions. Too few people and the decision rests on one person's impression. Too many and you get diffuse responsibility, a slow process, and a candidate experience of repeating themselves to five strangers.

Three or four interviewers is enough for most roles. Give each one a distinct area so they are not all asking the same question and so the coverage is deliberate. And name the decision maker explicitly. Consensus hiring sounds collaborative and in practice means the most risk-averse person holds a veto, which reliably selects for inoffensive over excellent.

5. Settle the money before you advertise

Approve the band, confirm it, and check it against the market before the job goes live.

The failure here is expensive and completely avoidable: you run a full process, find someone excellent, and discover the budget is fifteen percent below what they are on now. You have spent six weeks and burned the candidate, who will remember.

Check what the role actually pays, and publish the range in the advert. Pay transparency improves applicant quality, saves time on both sides, and is now a legal requirement in a growing number of jurisdictions.

Budget the whole cost, not just the salary: advertising, any assessment you use, the hours the panel will spend, and the recruiter fee if you use one. That number is what tells you whether to run it in-house or bring in help.

6. Decide how you will find them

Posting the job and waiting is a strategy for roles where supply is healthy. It is not a strategy for anything specialised.

Decide the mix deliberately. Your careers page and job boards for reach. Your existing talent pool, which is the cheapest source you have and the one most often forgotten: people who applied for something adjacent six months ago are already interested in you. Your team's networks, through a referral programme if you have one. Direct approach for the roles where the best people are not looking.

If the role is genuinely hard to fill, decide now whether you are running it yourself or bringing in outside help. Deciding that in week six, after the first approach has failed, costs you the six weeks.

Write the timeline down

Not a promise to anyone, an internal sequence: when the job goes live, when screening happens, when interviews are scheduled, when you intend to decide.

Two reasons. It surfaces the bottleneck in advance, which is almost always panel availability, and it gives you something to measure against so you can see where the process actually slowed rather than guessing afterwards.

Get the panel's interview slots into diaries before the job is posted. It feels premature. It is the single most effective thing you can do to stop a process drifting, because the delay is almost never screening and almost always finding a time when three busy people are free.

Common questions

How long should hiring planning take?

Around thirty to forty-five minutes for a standard role, with the hiring manager and whoever owns the process. Longer for a first-of-its-kind or senior hire. It is the highest-return time in the whole process.

Who should be involved?

The hiring manager, the person who owns hiring, and whoever holds the budget. Everyone else is consulted, not required.

What if requirements change mid-process?

Stop and re-plan rather than quietly adjusting as you go. A re-scoped role assessed against the original scorecard produces a decision nobody can defend, and candidates notice.

Do you need a hiring plan for a single role?

Yes, and single roles are where skipping it hurts most, because there is no second hire to correct the mistake against.

The takeaway

Confirm the role is the right answer, define what good looks like at twelve months, write the scorecard before you meet anyone, name the panel and the decision maker, approve the money before advertising, and put the interview slots in diaries before the job goes live.