Most bad hires start before the job is posted. They start in a rushed ten-minute chat between a recruiter and a hiring manager, where "we need a strong communicator who can hit the ground running" passes for a plan.
An intake meeting fixes that. Done well, it takes about 30 minutes and saves weeks of wasted screening, mismatched interviews, and offers that get declined. Here is how to run one that actually changes the outcome.
Why the Intake Meeting Gets Skipped
Hiring managers are busy, and recruiters often feel pressure to open the requisition fast. So the conversation shrinks to a copied job description and a few adjectives.
The cost shows up later. Candidates get rejected for reasons nobody wrote down, interviewers ask overlapping questions, and the manager says "I'll know it when I see it" after the fifth finalist.
A short, structured intake replaces that guesswork with decisions made up front, when they are cheap to make.
Start With the Problem, Not the Title
Before talking about requirements, ask what is going wrong or missing on the team right now. A job title describes a seat; a problem describes the work.
Try questions like these:
- What is not getting done today that this person will own?
- What would a successful first 90 days look like, in concrete terms?
- If this hire fails in a year, what is the most likely reason?
The last question is the most useful. It surfaces the real risks, such as a difficult stakeholder, an unclear scope, or a skill the team lacks, and it tells you what to screen for.
Separate Must-Haves From Nice-to-Haves
Almost every job description lists ten requirements and treats them all as equal. They never are.
Ask the manager to sort skills into three groups: needed on day one, learnable within six months, and a bonus. Then push back gently on the first group. If the list has more than four or five items, something belongs in the second group.
Write the final list down and have the manager confirm it in the meeting. This single step prevents the most common failure in hiring: rejecting a strong candidate for missing a skill that was never essential.
Agree on What Good Looks Like
"Strong problem solver" means different things to different interviewers. Turn each must-have into something observable.
For example, instead of "good communicator," agree on "can explain a technical tradeoff to a non-technical stakeholder in under two minutes." Now interviewers know what to listen for, and a scorecard becomes possible.
Aim for a short rubric: three to five competencies, each with a one-line definition of strong, acceptable, and weak. Our guide on interview scorecards covers how to turn that into a rating sheet.
Calibrate With Real Examples
Abstract criteria drift. Concrete examples pin them down.
Ask the manager to describe the best person who ever held a similar role, and what set them apart. Then ask for someone who struggled and why. These two portraits often reveal expectations that never made it into the job description.
If you have a few anonymized resumes handy, share two or three and ask, "Would you interview this person?" Five minutes of that exercise teaches you more about the manager's real filters than any written spec.
Lock Down the Process and the Timeline
Candidates drop out when the process drags, and managers lose enthusiasm when feedback is slow. Settle the logistics before the search begins.
Cover these points:
- Who is on the interview panel, and which competency does each person assess?
- How many rounds will there be, and what is the target time from first call to offer?
- How fast will interviewers submit feedback after each conversation (a 24-hour limit works well)?
- Who makes the final call, and what happens if the panel disagrees?
Getting the decision rule agreed in advance avoids the awkward debate that happens when two finalists split the room.
Be Honest About Compensation and Market Reality
This is the part many recruiters avoid, and it is where intake meetings earn their keep. If the budget does not match the market for the skills requested, say so now.
Bring a few data points: current salary ranges for similar roles, how long comparable searches have taken, and what competing offers look like. Then offer options, such as adjusting the range, widening the location, or trimming the must-have list.
A manager who hears this in week one can adjust. A manager who hears it after six weeks of failed offers is frustrated, and so is everyone else.
Close With a Written Summary
End the meeting by repeating back the problem, the top must-haves, the rubric, the panel, and the timeline. Then send it in writing within a day and ask the manager to reply with corrections.
That email becomes your reference point. When a debate comes up in week three about whether a candidate "has enough experience," you can point to what was agreed.
A Simple Intake Agenda You Can Reuse
If you want a template, this 30-minute structure works for most roles:
- Minutes 0 to 5: the problem this hire solves and the first 90-day outcomes.
- Minutes 5 to 15: must-haves, learnable skills, and bonuses.
- Minutes 15 to 20: what strong looks like, with examples.
- Minutes 20 to 25: panel, rounds, feedback speed, and decision rule.
- Minutes 25 to 30: compensation reality check and next steps.
Repeat it for every requisition, even for roles you have filled before. Teams change, and so do the problems that need solving.
What to Expect After You Start
The first few intake meetings may feel slow, and some managers will resist the structure. Stick with it. Most come around after the first search that closes faster and with fewer surprises.
Over time you also build a record of what each team really values, which makes future searches quicker. Platforms like CareerGraph can then carry those agreed competencies straight into interview questions and scoring, so the clarity you built in the meeting shows up in every conversation with a candidate.
A clear brief will not guarantee a perfect hire, but it removes the most avoidable reason hires go wrong. Thirty minutes at the start is a small price for that.
