Most searches that drag on for three months were broken in the first week. Not by a bad market, not by a weak pipeline, but by a kickoff conversation that lasted eight minutes and ended with "just send me some resumes."
The intake meeting is the highest leverage half hour in the entire hiring process. It is also the one most often skipped, shortened, or replaced by a forwarded job description. Here is what a real one looks like.
Why Searches Actually Stall
Watch a stalled search closely and you will usually find the same pattern. The recruiter sources ten candidates. The hiring manager rejects nine of them with feedback like "not quite senior enough" or "I did not feel the spark." The recruiter recalibrates, sources ten more, and gets a similar result.
By candidate twenty, the two of them finally have the conversation they should have had at the start. What does senior mean here? What does the spark look like in practice? Six weeks are gone and the role is still open.
The intake meeting front-loads that conversation. You pay thirty minutes now instead of six weeks later.
Question One: Who Did This Work Before, and What Happened?
Every open role has a history. Either someone held it and left, someone is doing pieces of it badly because they are stretched, or nobody has done it and the team is drowning.
Ask which one it is. If someone left, ask what they were good at and where they struggled. If the work is currently scattered across three people, ask what each of them is handing off. The answers tell you more about the actual job than any requirements list.
This question also surfaces a specific risk: a manager who is hiring a replacement for a person they liked will unconsciously screen for that person. Naming it early keeps it from quietly shaping every debrief.
Question Two: What Does This Person Do in Their First 90 Days?
Job descriptions describe categories of work. First 90 day plans describe actual work. The gap between them is where most misalignment lives.
Push for specifics. Not "own the analytics roadmap" but "ship the churn dashboard the exec team has been asking for since April." Not "improve our processes" but "rebuild the onboarding checklist so new reps ramp in three weeks instead of six."
If your hiring manager cannot describe the first 90 days concretely, the role is not ready to open. That is a useful finding, and it is much cheaper to discover now.
Question Three: Which Requirements Are Real?
Take the requirements list and go down it line by line. For each item, ask a version of this: if a candidate is excellent everywhere else and missing this, do we pass?
You will find three categories. A small number of genuine dealbreakers, usually two or three. A larger group of strong preferences that can be traded against other strengths. And a surprising amount of text that nobody remembers writing and nobody would enforce.
That third category is worth deleting from the posting entirely. Long requirements lists suppress applications from strong candidates who self-select out, and they do it disproportionately among people who read the list as a checklist rather than a wish list.
Question Four: Show Me Two People You Would Hire Today
Ask your hiring manager to name two people, real ones, who would be an instant yes. Former colleagues, people at competitors, someone whose work they admire from a distance.
Then pull up those profiles together and talk through what makes them good. This is calibration by example, and it is far more precise than adjectives. You learn whether the manager values depth or range, whether the target company profile is enterprise or startup, whether the bar is about output or about judgment.
You also get a concrete sourcing starting point, since people who look like your ideal hire tend to be findable near your ideal hire.
Question Five: Who Else Says Yes, and What Do They Care About?
Find out now who is on the interview loop and what each person is evaluating. If three interviewers are all probing general problem solving, you are collecting redundant data and leaving real risks unexamined.
Assign areas explicitly. One person on technical depth, one on collaboration and conflict, one on the specific domain challenge in the first 90 day plan. Write down who covers what.
Also ask who has veto power. Sometimes it is a skip level manager or a peer team lead who was not in the room. Finding that out at the offer stage is a painful way to learn it.
Question Six: What Is Our Answer to "Why This Job"?
Strong candidates ask this in the first ten minutes of a screen. If your answer is generic, they disengage before you finish.
Get your hiring manager to make the case out loud. What is genuinely interesting about the problem? What will this person get to build or own that they could not somewhere else? What is hard about the role that an ambitious person would find appealing rather than off-putting?
Also ask what the honest downsides are. Legacy systems, a demanding stakeholder, a team in the middle of a rebuild. You want to know these before a candidate discovers them in the final round.
Write It Down and Get Agreement
The output of an intake meeting is a short document, not a good feeling. One page covering the first 90 days, the two or three real dealbreakers, the calibration examples, the interview panel assignments, and the pitch.
Send it to the hiring manager and ask them to confirm it. That confirmation is what you point back to when candidate seven gets rejected for a reason that appears nowhere on the page.
Searches rarely fail because nobody good was available. They fail because the definition of good kept moving. Thirty minutes and one page is a cheap way to hold it still.