Intake meeting questions for recruiters: bring a draft, not a blank form

Intake meeting questions are the questions a recruiter asks a hiring manager, or a client, before a search starts, to pin down what the role does, what the bar is, and how candidates will be judged. A good intake ends with an agreed list of requirements that every candidate will be measured against.

Here's our view. Don't walk into an intake with a blank form. Walk in with a draft requirement list the hiring manager has to cut and rank. People describe roles badly from memory, but they're very good at editing a list someone else wrote.

Key Takeaways

Our position: bring a draft requirement list to the intake and make the hiring manager cut and rank it. Editing forces trade-offs that open questions let people dodge.
Ask about the work first (the first 90 days, a strong week), then the bar, then how each requirement will be tested.
Six to ten requirements is plenty. If everything is critical, nothing separates a strong candidate from an average one.
Agency recruiters need a second set of questions on fees, exclusivity, submission format and feedback turnaround.
The list you agree in the intake should become the scoring criteria for first-round screening, word for word.

What a recruiter intake meeting is for

A recruiter intake meeting has one job. It turns a hiring manager's idea of the role into criteria you can screen against. Everything else (the timeline, the pitch, the salary range) supports that.

Most intakes miss it because the output is a profile, not criteria. You leave with "strong communicator, startup experience, great with stakeholders", and none of that tells you how to compare two candidates on a Tuesday afternoon.

The test for a good intake is simple. Could a second recruiter, reading your notes, screen the same ten resumes and reach the same shortlist? If not, the intake isn't finished.

Before the call: bring a draft requirement list, not a blank form

Start from the job description. Pull out every requirement it implies, then cut the list to the ones you'd actually ask about. Bring that draft to the meeting.

The hiring manager's job in the room changes. Instead of describing the role from memory, they delete, add and rank. Asking someone to pick the two or three requirements that really decide the role surfaces disagreements in five minutes that would otherwise show up in the debrief.

In Expert Hire, this step happens when you create a job. Press Suggest requirements and it reads the JD and proposes a list. Each requirement gets a level of its own, for example Critical, nothing is saved until you review it, and the X on each row removes it.

That's a starting point for the conversation, not a decision. Our guide to setting requirements and levels puts it plainly: six to ten requirements is usually enough.

Intake meeting questions about the work itself

Start with the work, not the job description. These intake meeting questions get the hiring manager talking about real tasks.

What will this person be doing in the first 90 days? Push for specific projects, not responsibilities.
What does a strong week look like six months in? This shows what success actually means to the manager.
What's the hardest part of the job that the JD doesn't mention? Every role has one.
Who will they work with most, and how? Team, other functions, customers.
Why is this role open now? Backfill, growth, or a new problem. Each one changes who you're looking for.

Listen for verbs. "Ship", "negotiate", "debug" and "train" become requirements. "Rockstar" and "self-starter" don't.

Questions that set the bar: must-haves, trade-offs and the last rejection

This is where the draft list earns its keep. Walk through it row by row during the intake meeting with hiring manager present, and ask:

Which two or three of these decide the role? If everything is critical, the score can't separate candidates.
Which would you trade, and for what? For example, two years less experience for a stronger domain fit.
What's missing from this list? Give them room to add.
Tell me about the last candidate who looked good on paper and didn't get the offer. Why? This is often the most useful answer you'll get, because it reveals the real bar.
What would make you reject someone in the first five minutes? Deal-breakers people won't write down still shape decisions.

Write every answer back into the list. By the end, each row should have a level, and nobody should be surprised by which rows matter most.

Questions that decide how each requirement will be tested

Most intakes stop at the profile. The best ones keep going and decide how each requirement will be checked. Ask for every critical row:

How would we know a candidate has this? A specific answer, not "you can tell".
Which round tests it? First-round screen, technical round, final panel.
Is there a work sample or question that shows it directly? A short task often beats a long conversation.
What does a strong answer sound like? Get one example in the manager's own words.

This step isn't just tidy. US federal guidance on selection, the Uniform Guidelines on Employee Selection Procedures, treats a selection procedure that has an adverse impact as discriminatory unless it has been validated. Writing each requirement as something you can test makes it far easier to defend.

It also lines up with the evidence. The OPM guidance on structured interviews describes them as built to measure job-related competencies, with every answer judged on the same rating scale and standards. In the 2022 update by Sackett and colleagues, structured interviews came out as the top-ranked selection procedure, at a mean validity of about .42. Structure starts at intake.

Intake questions for agency recruiters on a client call

A staffing recruiter taking a req from a client needs everything above plus a commercial layer. Nobody else in the room will ask these, so you have to.

Is this exclusive, and who else is working it? Other agencies, internal recruiters, referrals.
Who owns the fee and terms, and are they signed? Don't start sourcing on a handshake.
What format do you want submissions in? Resume only, a written summary, or a structured report.
What do your own interviews test after we submit? So you screen for what the client will actually check.
How fast will you give feedback, and who gives it? Agree a turnaround, like 48 hours, and write it down.
What will make you say no that isn't in the JD? Location, notice period, past employers, salary history rules.
How many candidates do you want to see, and by when? Three strong ones beat ten maybes.

Keep each client's criteria separate. If you run several clients in Expert Hire, each one gets its own workspace with its own jobs and candidates, and nothing leaks between them. The guide to setting up a client workspace shows the structure, and our post on AI tools for staffing agencies covers the wider workflow.

A recruitment intake meeting template you can copy

Here's a hiring manager intake meeting template that fits on one page. Copy it into your notes, or use it as a recruiting intake form the manager fills in before the call.

Role basics

Role title, team, location or remote, and level
Why the role is open now
Salary range and who approved it

The work

First 90 days: three specific outcomes
A strong week at six months
The hardest part of the job

Requirements (six to ten)

Requirement, level, and how it will be tested
The two or three that decide the role
Trade-offs the manager will accept

Process

Stages, owner of each, and what each tests
Feedback turnaround agreed
Target date for the first shortlist

Open questions

Anything unresolved, with an owner and a date

That last section matters. A template that only records answers hides the gaps. Writing down what's still undecided stops it turning into a surprise in week three.

Frequently asked questions

What questions should I ask in an intake meeting?

Ask about the work (first 90 days, a strong week, the hardest part), then the bar (which requirements decide the role, what's tradeable, why the last good candidate was rejected), then the evidence (how each requirement will be tested and in which round). Agency recruiters should add fee, exclusivity and feedback questions.

What happens at an intake meeting with a hiring manager?

The recruiter and hiring manager agree what the role needs and how candidates will be judged. A good meeting ends with a short, ranked list of requirements, a process with owners, and a feedback turnaround. A weak one ends with a list of adjectives.

How long should an intake meeting be?

Most can be done in 30 to 45 minutes if the recruiter brings a draft requirement list. Starting from a blank form usually takes longer and produces a vaguer result. A new or unusual role may need a short follow-up once the first candidates come in.

How do you prepare for an intake meeting as a recruiter?

Read the job description, draft a list of six to ten requirements from it, and note your questions about anything vague. Check comparable roles and pay ranges if you can. Send the draft list ahead so the manager arrives ready to edit it.

What is the difference between an intake form and an intake meeting?

An intake form collects the basics in writing, often before the call. The intake meeting is where the trade-offs get made, because ranking requirements and agreeing how to test them needs a real conversation. Use the form to prepare and the meeting to decide.

The intake sets the criteria everyone else uses

The best intake meeting questions don't just describe the role. They produce a ranked list of requirements and a plan for testing each one. That list should follow the role all the way through: into the screen, onto the report card, and into the interview debrief where the team decides.

If you want the requirements you agreed in the intake to become the criteria every first-round answer is scored against, see how to create a job and set requirements in Expert Hire.

By TK, Growth at Expert Hire. Last updated October 13, 2026. Reviewed by Anand Suresh, CPO at Expert Hire.