Intake meeting questions: 30 questions to ask a hiring manager or client

Intake meeting questions are what a recruiter asks the hiring manager, or an agency recruiter asks the client, before a search starts. They pin down why the role is open, the three to five genuine must-haves, what success looks like, pay and logistics, and how fast feedback will come. The 30 questions below are grouped in the order most intakes run, each with what a useful answer sounds like and a warning sign, followed by a one-page summary template to send back the same day.

The intake decides the quality of everything after it. A vague intake produces screens that test the wrong things and submittals that miss. Here is how to run one that does not.

Before the meeting: ten minutes of prep

• Read the job description twice and mark every requirement. You will ask which ones are real.
• Check your history with this client or team: previous hires into similar roles, candidates they rejected and why, how fast they gave feedback last time.
• Find three real profiles at different levels that roughly match. Showing them in the meeting gets faster, more honest answers than abstract questions.
• Send a short agenda: "Role and why it's open, must-haves, what success looks like, pay and logistics, interview process and feedback." Hiring managers who see "feedback" on the agenda come prepared to commit to it.

The role and why it is open

1. "Why is this role open now: a new position, a backfill, or a change in the team?"
   • Useful answer: a clear reason, and for a backfill, why the last person left.
   • Warning sign: the third backfill in two years with no explanation. Candidates will ask, so you need the answer.
2. "What happens if this role stays unfilled for three months?"
   • Useful answer: a real cost such as a delayed project, overtime or a lost client. That tells you the true urgency.
   • Warning sign: "Not much." Expect slow feedback and a search that stalls.
3. "If the person who had this job before was great, what made them great? If not, what went wrong?"
   • Useful answer: specific behaviors. This is often where the real must-haves come out.
   • Warning sign: a description of the previous person's personality rather than their work.
4. "Which parts of the job description are accurate, and which are copied from an older version?"
   • Useful answer: honest edits. Most job descriptions carry at least one inherited requirement.
   • Warning sign: "It's all accurate" for a description with twelve requirements.
5. "Where does this role sit: who does it report to, who reports to it, and who does it work with most?"
   • Useful answer: names or roles for each, and the one relationship that will be hardest.
   • Warning sign: a reporting line that is "being worked out."

Must-haves and nice-to-haves

6. "If you could only screen for three things, what would they be?"
   • Useful answer: three things, in their words, that you can test on a phone screen.
   • Warning sign: a list of eight, or soft traits only ("hungry", "team player").
7. "Would you interview someone without [requirement]?" Ask this for every requirement on the job description.
   • Useful answer: a quick yes or no each time. Every yes becomes a nice-to-have.
   • Warning sign: "Maybe, if they were strong enough" for every item, which means there are no must-haves yet.
8. "What does [must-have] look like in practice? What would someone have done to show it?"
   • Useful answer: an observable example: "run payroll for 200 people on their own", not "payroll experience."
   • Warning sign: the requirement cannot be described beyond its label.
9. "Is a degree, certification or number of years a real requirement, or a proxy for something else?"
   • Useful answer: either a hard requirement with a reason (licensing, client contract) or the skill it stands in for.
   • Warning sign: "That's just what we always put."
10. "Here are three profiles. Which would you interview, and why or why not?"
    • Useful answer: reasons tied to the must-haves. This is the fastest calibration you will get.
    • Warning sign: rejecting all three for reasons not mentioned so far. Add those reasons to the brief.
11. "What would make you reject a candidate who looks good on paper?"
    • Useful answer: job-related deal-breakers such as job length patterns, a type of employer or a gap in a critical skill.
    • Warning sign: anything touching age, family, health or background. Redirect to the job: "What would that tell you about their ability to do the work?"

Success, the team and the manager

What success looks like

12. "Twelve months from now, what will the person in this role have done that makes you glad you hired them?"
    • Useful answer: two or three outcomes you can describe to candidates.
    • Warning sign: "Just get up to speed." Either the role is not defined or the manager has not thought about it.
13. "What does the first 90 days look like?"
    • Useful answer: onboarding, a first project, who trains them.
    • Warning sign: no plan for a role where the previous person has already left.
14. "What is the hardest part of this job, the thing people underestimate?"
    • Useful answer: an honest difficulty you can pre-screen for and tell candidates about.
    • Warning sign: nothing hard. Candidates will find it anyway, often after they start.
15. "How will this person be measured?"
    • Useful answer: specific metrics or deliverables.
    • Warning sign: measures that do not match the must-haves you just agreed.

The team and the manager

16. "How would your team describe the way you manage?"
    • Useful answer: self-aware and specific: "I'm hands-on for the first month, then weekly one-to-ones."
    • Warning sign: no answer. Candidates ask this about the manager more than anything else.
17. "Who has done well on your team, and what do they have in common?"
    • Useful answer: behaviors you can screen for.
    • Warning sign: "People like me." Probe for what that means in the work.
18. "How does the team work day to day: on-site, hybrid, remote, core hours?"
    • Useful answer: the actual pattern, not the policy on paper.
    • Warning sign: "Hybrid" that turns out to mean four days in the office for new starters.
19. "What should I tell candidates about the team that will make the good ones interested?"
    • Useful answer: a real selling point: a project, a technology, progression, stability.
    • Warning sign: nothing beyond pay. Expect a harder search.

Pay, location and logistics

20. "What is the pay range, and where in it do you expect to land for the person you described?"
    • Useful answer: a range and a realistic target. In states that require ranges in postings, you need this before anything goes live; see salary expectation questions for the rules.
    • Warning sign: "Depends on the candidate" with no range. Ask what they would pay the three profiles you showed.
21. "How flexible is the top of the range, and who approves an exception?"
    • Useful answer: a clear yes or no and a named approver.
    • Warning sign: "We'll find the money for the right person" with no approver. Plan as if the range is fixed.
22. "What else is in the package: bonus, benefits, equity, schedule, time off?"
    • Useful answer: enough detail to answer candidate questions and meet posting rules that require a benefits description.
    • Warning sign: the recruiter has to find out from HR later. Ask who can confirm it this week.
23. "Can you sponsor visas, and will you consider candidates who need to relocate or who are fully remote?"
    • Useful answer: three clear answers that become your knockout questions.
    • Warning sign: "Case by case." Get the cases.
24. "When do you need someone to start, and what notice period can you wait for?"
    • Useful answer: a date and a maximum notice period.
    • Warning sign: "Yesterday" combined with a four-week interview process.

Process and feedback

25. "Walk me through the interview steps, who is in each, and what each step tests."
    • Useful answer: named stages with a purpose each, so no two stages test the same thing.
    • Warning sign: five stages where nobody owns a competency. Suggest a plan; an interview scorecard helps.
26. "How quickly will you review resumes I send, and how quickly after an interview will I get feedback?"
    • Useful answer: numbers in business days that you write into the summary.
    • Warning sign: "As soon as I can." That means no commitment; propose one.
27. "Who makes the final decision, and who can veto?"
    • Useful answer: one decision-maker and a short list of people whose objection stops a hire.
    • Warning sign: a consensus of six. Plan for a longer process and tell candidates.
28. "Are other recruiters, agencies or internal referrals working on this role?"
    • Useful answer: a straight answer. For agencies it decides how much time the search deserves; for in-house it avoids duplicate outreach.
    • Warning sign: reluctance to say. Assume yes.
29. "How do you want candidates presented: call, email, ATS or portal, and in what format?"
    • Useful answer: a preferred channel and whether they want a written summary with each resume.
    • Warning sign: portal-only with no contact. Ask for a named person for questions.
30. "If we haven't found the right person in [three weeks], what would you change first: pay, location, requirements or process?"
    • Useful answer: a ranked answer. You now know your fallback before you need it.
    • Warning sign: "Nothing, keep looking."

Agreeing must-haves and feedback times

Two agreements matter more than any single answer, so close the meeting by stating them back.

Must-haves

Read out the three to five must-haves in the manager's words and ask: "If someone has these and none of the nice-to-haves, you'll interview them?" If the answer is yes, those are the must-haves your screen tests and your submittals argue for. If it is "probably", keep going until it is yes. Offer to send three calibration profiles within two business days and get a yes or no with a reason for each. That round usually surfaces the requirement nobody mentioned.

Feedback times

Propose specific numbers rather than asking for them. For example: resume feedback within two business days, interview feedback within one business day, and a named backup if the manager is away. Those numbers are an example, not a standard; what matters is that they are written down and agreed. Also agree what happens when they are missed: "If I haven't heard by then, I'll call you, and if a candidate has another offer I'll tell you the same day."

The one-page intake summary template

Send this back the same day and ask for a reply confirming or correcting it.

INTAKE SUMMARY — [Role] — [Client / Team] — [Date]
Hiring manager: [ ]   Decision-maker: [ ]   Veto: [ ]
Why open: [new / backfill: reason]   Cost of vacancy: [ ]

MUST-HAVES (their words, each testable on a screen)
1. [ ]  — looks like: [observable example]
2. [ ]  — looks like: [ ]
3. [ ]  — looks like: [ ]
NICE-TO-HAVES: [ ]
DEAL-BREAKERS (job-related): [ ]

SUCCESS
12 months: [2–3 outcomes]
First 90 days: [ ]
Hardest part of the job: [ ]

TEAM
Reports to: [ ]   Direct reports: [ ]   Works most with: [ ]
Work pattern: [on-site / hybrid X days / remote + time zones]
Selling points for candidates: [ ]

PAY AND LOGISTICS
Range: $[ ]–[ ] base; target $[ ]   Exceptions approved by: [ ]
Package: [bonus, benefits, equity, time off]
Sponsorship: Y/N   Relocation: Y/N   Remote: Y/N
Start by: [date]   Max notice: [weeks]

PROCESS
Stages: [stage — who — what it tests]
Presentation format: [channel, summary needed Y/N]
Other recruiters or agencies: [ ]

AGREED TIMES
Resume feedback: [ ] business days   Interview feedback: [ ] business days
Backup contact: [ ]
If no hire by [date], first lever: [pay / location / requirements / process]

CALIBRATION: [3] profiles to send by [date]

The must-haves in this summary are the ones you copy into the phone screen template, and the presentation preferences feed straight into how you present candidates.

Intake red flags and what to say