Most searches that drag on for months were doomed in the first week. Not because the market was thin or the budget was tight, but because the recruiter and the hiring manager never actually agreed on who they were looking for.
That agreement is supposed to happen in the intake meeting. In practice, intake is often a 15-minute calendar squeeze where the hiring manager forwards an old job description, says "someone like Priya, but more senior," and rushes off to their next call. Six weeks later, everyone is frustrated: the recruiter because every candidate gets rejected, the manager because "recruiting keeps sending me the wrong people."
Here is how to run an intake meeting that prevents that outcome.
Start with the work, not the resume
The default intake question is "what qualifications does this person need?" It produces a wish list: years of experience, tools, degrees, certifications. Wish lists are easy to write and nearly useless for screening.
Ask a different question instead: what will this person actually do in their first six months? Push for specifics. Which project will they own? What is currently broken that they need to fix? Who will they work with every day?
When a manager says "we need eight years of experience," ask what task requires the eighth year. Usually there is no answer, and the real requirement surfaces: they need someone who has run a migration before, or managed a vendor, or shipped under a hard deadline. Those are things you can screen for. "Eight years" is not.
Force the trade-off conversation early
Every hiring manager wants a candidate who is technically deep, a strong communicator, cheap, local, and available immediately. That person rarely exists, and pretending otherwise is how searches stall.
So make the manager rank. A simple exercise works: list the top six requirements, then ask which two they would give up if a candidate nailed the other four. The answers are often surprising. A manager who insisted on industry experience may admit they would trade it for someone who has scaled a team. That single admission can double your qualified pool.
Get explicit about deal breakers versus preferences. A deal breaker means you will reject an otherwise perfect candidate over it. Most "requirements" fail that test once you frame it that way.
Calibrate on real profiles, not adjectives
Words like "strong," "senior," and "scrappy" mean different things to different people. The fastest way to close that gap is to calibrate on actual candidates before the search starts.
Pull three or four real profiles (from LinkedIn, past applicants, or your ATS) and review them together in the meeting. Ask the manager: would you interview this person? Why or why not? Ten minutes of this reveals more about the manager's actual bar than an hour of abstract discussion.
This exercise also exposes contradictions early. If the manager rejects every profile at the stated salary band, you have a compensation problem, and it is far better to discover that in week one than in week seven, after a favorite candidate declines the offer.
Agree on the process before the first resume goes out
Intake is not just about the profile. It is about the machine that will evaluate it. Before you leave the meeting, lock down four things.
First, the interview loop: who is on it, what each person assesses, and roughly how long the whole process takes. Candidates drop out of slow, vague processes, and the best ones drop out fastest.
Second, feedback turnaround. Get a commitment that the manager will review resumes within 48 hours and interviewers will submit feedback within 24. Put it in writing. Slow feedback is the single most common reason good candidates go cold.
Third, the selling points. Ask the manager directly: why would a great candidate take this job over their other offers? If the answer takes more than a minute to form, workshop it now. Every interviewer will need it.
Fourth, decision rights. Who makes the final call, and what happens if the panel splits? Ambiguity here turns debriefs into stalemates.
Put it in a one-page brief
End the meeting by writing everything down in a single page: the mission of the role, the top four requirements in priority order, the explicit non-requirements, the loop, and the timeline. Send it to the manager and ask them to confirm it in writing.
This document does two jobs. It keeps the search honest, because when a manager rejects a candidate for missing something that never appeared in the brief, you have a concrete way to reopen the conversation. And it makes the eventual job posting dramatically easier to write, because the hard thinking is already done.
Schedule the two-week recalibration
Even a great intake is a hypothesis. The market gets a vote.
Book a 20-minute check-in for two weeks after the search opens. Bring data: how many candidates were contacted, response rates, where candidates are dropping off, and what feedback patterns are emerging. If the first five interviews all failed on the same requirement, the requirement may be miscalibrated, or the sourcing profile is wrong. Either way, you want to adjust in week two, not month three.
Searches rarely fail because of one bad interview. They fail slowly, through weeks of misalignment that nobody stops to name. A rigorous intake meeting, plus one scheduled recalibration, removes most of that risk before the first candidate ever picks up the phone.
The 30-minute version
If you can only get 30 minutes with the hiring manager, spend them like this: ten minutes on what the person will do in the first six months, ten minutes ranking requirements and naming deal breakers, five minutes reviewing two real profiles, and five minutes locking the loop and feedback commitments. Skip the pleasantries and the job description read-through; the document can follow the meeting instead of leading it.
A search that starts aligned moves faster at every stage that follows. The intake meeting is 30 to 60 minutes of work that saves weeks. Treat it like the highest-leverage meeting in your hiring process, because it is.