Hiring Manager Intake Meeting: 30 Questions to Ask, With an Intake Form
Thirty intake meeting questions to ask a hiring manager before a search starts, grouped by purpose, with a free intake form and the decisions to leave with.
An intake meeting is the 30 to 45 minutes a recruiter and a hiring manager spend agreeing what a role needs before the search starts: why it's open, what the hire must achieve, which requirements are real must-haves, how candidates will be assessed, who decides, and by when. Below are 30 intake meeting questions grouped by purpose, what each answer gives you, and a form with all of them to send the hiring manager the day before.
The meeting is short, but it decides more than any interview that follows. Every screening question, scorecard and shortlist in the search is built on what gets agreed here, and every disagreement that isn't settled here comes back later, usually as a strong finalist turned down for a reason nobody wrote down.
What should an intake meeting decide?
Leave the room with seven things agreed and written down:
| Decision | What it becomes |
|---|---|
| What the hire must achieve in 90 days | The outcome every interview question points at |
| Three must-haves | The competencies every interview scores |
| The knockouts | The hard requirements asked early in every screen |
| The interview stages, owners and focus | A plan you can share with candidates |
| Who makes the final decision | One name, agreed before the first interview |
| The pay range | Something you can say in the first conversation |
| The dates | A target start date, and a hiring deadline counted back from it |
Searches drag without these. In Gem's 2025 benchmarks, a vendor report, the number of interviews per hire rose from 14 in 2021 to 20 in 2024 (Gem). Some of that is a harder market, but extra rounds are also what a hiring team adds when it never agreed what it was looking for.
The 30 intake meeting questions
The role and why it's open
- Why is this role open now: a new role, growth or a replacement? A replacement tells you what to repeat or avoid. A new role needs its purpose defined before anything else.
- If this role stays empty for three months, what happens? The real urgency, and the case for the timeline.
- In one sentence, what will this person own? That sentence is how you'll describe the role to every candidate, so get the hiring manager's version.
- Who held the role before, and what made them succeed or struggle? The most concrete evidence you'll get of what the role demands.
What success looks like
- What must this person have achieved after 90 days? Point every interview question at this.
- And after a year? Whether the role grows, and what candidates should be able to grow into.
- What does the best person in a similar role do differently from the rest? The behavior to listen for in candidates' answers.
- How will you measure performance in this role? The measures to ask candidates about in the interviews.
Must-haves and nice-to-haves
- Which three skills or experiences must every hire have on day one? These become the competencies the interviews score.
- Would you turn down an otherwise excellent candidate without each of them? The test that separates a real must-have from a preference.
- Which of the other requirements could someone learn in their first 90 days? Moves trainable skills off the must-have list.
- Which requirements in the job description are nice to have? A long list of requirements discourages good applicants who don't tick every box.
- Do you require a degree, certification or a number of years of experience? Why? Checks whether a credential is standing in for a skill you could test directly.
Knockouts and deal-breakers
- Is there a license, certification, shift pattern or location the role can't do without? These are your knockout questions, asked early in every screen.
- What would make a candidate a definite no, whatever else they offer? Deal-breakers, written down before anyone gets attached to a candidate.
- Has a past hire not worked out? What would have shown it earlier? The warning sign to probe for in the interviews.
The team and the manager
- Who will this person work with most closely? Who should meet the finalists, and what collaboration looks like day to day.
- Do you manage with close direction or a lot of independence? Lets you describe the job honestly and check candidates' working styles against it.
- What's hard about this role or this team that candidates should hear early? Honest framing keeps the wrong people from accepting, and the right ones from being surprised.
- Why would a strong candidate choose this role over a similar one elsewhere? Your pitch, in the manager's words.
The candidate market
- Where have good people for this role come from before: companies, titles, schools, referrals? Where to source first.
- Is anyone already in mind: an internal candidate, a referral or a past applicant? People to contact before the job is posted.
- If we can't find every must-have, which one would you trade, and for what? The fallback, agreed before the search stalls rather than after.
Pay and logistics
- What is the approved pay range, and is there any flexibility? Lets you share the range in the first conversation, which saves time for everyone.
- Where will the person work, and how often in the office? The location answer every screen needs.
- What's the latest start date that still works? Count the hiring deadline back from it.
The interview process
- Which stages will candidates go through, and who runs each one? The plan you can share with candidates up front.
- Which competencies will each stage assess, so no two stages ask the same thing? Avoids repeated questions and extra rounds.
- Who makes the final decision, and who else must agree? Names the decision-maker before the first interview, not after the last.
- How soon after each interview can you give feedback, and which interview slots can you hold each week? Held slots and a feedback deadline keep the search moving.
How do you separate must-haves from nice-to-haves?
Job descriptions often list ten or more requirements. Asked directly, hiring managers usually name far fewer that really matter. Two questions find them:
- Would you turn down an otherwise excellent candidate without it? If the answer is "probably not", it's a nice-to-have.
- Could a capable person learn it in the first 90 days? If yes, assess the ability to learn it, not the skill itself.
Here is how that sorts the requirements for a customer support team lead:
| Requirement | Turn down an excellent candidate without it? | Learnable in 90 days? | Becomes |
|---|---|---|---|
| Has led a team of five or more | Yes | No | Must-have |
| Handles escalated customers calmly | Yes | Partly | Must-have |
| Coaches people through quality reviews | Yes | Partly | Must-have |
| Knows our ticketing system | No | Yes | Taught in onboarding |
| A degree | No | Not relevant | Removed |
| Five years in support | No | Not relevant | Replaced by the must-haves above |
The last two rows are the usual result. Credentials and years of experience often stand in for a skill nobody has named; once the skill is named, the proxy can go. Our guide to turning a job description into interview questions takes the must-haves from here to a question set.
What should you send after the intake meeting?
Within a day, send the hiring manager a one-page summary and ask them to confirm it before you contact a single candidate:
- The role in one sentence, as you'll describe it to candidates
- The 90-day outcomes
- The three must-haves, each with how it will be assessed
- The knockout questions, flagged for review rather than used to reject anyone automatically; our guide to knockout questions explains why
- The interview stages, who runs each and what each one covers
- The pay range, start date and hiring deadline
- The first check-in: a date, usually a week in, to review the first candidates together
The first check-in is easy to skip, and it's the most useful. Reviewing three real candidates against the summary shows quickly whether the brief was right, while there's still time to change it.
What goes wrong in intake meetings?
- Treating the job description as the brief. Job descriptions are written to attract applicants, and often copied from the last search. Ask the questions anyway.
- Accepting "I'll know it when I see it." That means the criteria exist only in one person's head. Ask what the best person in a similar role does differently, and write it down.
- Leaving without a decision-maker. If two people can each say no and neither has to say yes, finalists stall.
- No feedback deadline. Candidates wait while interview feedback sits in someone's inbox; agree a deadline here, when it costs nothing.
- Never reopening the brief. If the first ten candidates all miss the same must-have, the market is telling you something. Bring it back to the hiring manager.
Once the brief is agreed, the rest of the search can be built from it: a structured interview on the must-haves, an interview scorecard with written anchors, and a first-round screen that asks the knockouts early. Our evidence-based hiring playbook covers the full process.
Where does DIO fit?
The intake summary is also the interview plan. DIO, Dio's AI interviewer, drafts an interview plan from the job description, which the recruiter reviews and edits before publishing it. Put the must-haves agreed at intake into that plan as the competencies the interview scores, each rated 1 to 5 against anchors written for the role, and the deal-breakers as knockout questions, which flag an answer for the recruiter to review. Candidates then take the same structured interview whenever it suits them, and the team sees scores that quote what each candidate said, measured against the criteria agreed at intake. Watch how it works.