When a hiring process drags, the diagnosis usually points at sourcing or at candidate quality. More often the cause is thirty minutes that never happened: the conversation where the recruiter and the hiring manager agree what they are actually looking for.
Without it, the recruiter is guessing, the hiring manager rejects candidates for reasons never stated, and the loop discovers the requirements by trial and error over six weeks.
The nine questions
1. What does this person do in the first six months?
Not the job description — the actual work. Three or four concrete outcomes. If the hiring manager cannot describe them, the role is not ready to open, and that is the single most valuable thing this meeting can discover.
2. Why is this role open?
Growth, backfill, or a new capability. A backfill has a reference point and usually a known reason for the departure. A new capability means nobody in the company has done this job, which changes who can credibly interview for it.
3. What are the three must-haves?
Three, not twelve. The test for each: would you reject an otherwise excellent candidate for lacking it? Everything failing that test goes on the nice-to-have list, and stays off the job posting requirements section.
4. What does a strong candidate look like on paper?
Ask for two or three real profiles — people at other companies, previous colleagues, anonymised examples. This calibrates the recruiter faster than any written specification, and it surfaces disagreement immediately.
5. What is the range, and is it approved?
Confirmed, not assumed. An unapproved range discovered at offer stage is the most expensive failure in the process, and it happens because nobody asked in week one.
6. Who interviews, and what does each of them assess?
Names and assigned criteria, not roles. This is where a loop gets designed rather than assembled — see how to run a structured loop. Also confirm availability. An interviewer travelling for three weeks is a three-week delay nobody planned for.
7. What is the decision rule?
Agree it now, while no candidate is in front of you. Consensus with a manager veto, a threshold on must-have criteria, or majority with recorded dissent. Deciding this after seeing scores is how the bar moves.
8. What is the timeline, and what is driving it?
A real constraint — a project start, a departure date, a seasonal peak — changes how you run the process. "As soon as possible" is not a timeline and produces no useful behaviour.
9. What would make you say no to someone who looks perfect?
The most useful question on the list and the one nobody asks. It surfaces the unstated criteria that would otherwise emerge as a rejection in week five with no articulated reason.
Two things to leave with
A written summary, circulated the same day. Three or four lines covering the must-haves, the loop, the range and the decision rule. Not a document nobody reads — a note that makes disagreement visible now rather than in a month.
A first-week sourcing sample. Five or ten profiles for the hiring manager to react to before any real screening begins. Reacting to concrete profiles surfaces criteria that abstract discussion never reaches, and it is far cheaper to recalibrate on five profiles than on five interviews.
How long it takes
Thirty minutes, done properly, for most roles. Longer for a genuinely new capability. Compared against a six-week process that fails because the requirements were never agreed, it is the highest-return half hour in hiring.
The one thing to resist is treating it as a form to complete. The value is in the disagreement it exposes — particularly on questions 3, 7 and 9.
For turning the output into an actual loop, see interviews and scorecards.