Recruiter interview questions that test candidate experience, not just placements
A recruiter interview usually spends its time on placement numbers, which are the least portable thing about the role. They depend on the market, the brief, and the brand the recruiter was carrying. What transfers is different: whether they treat candidates well when the answer is no, whether they push back on an unrealistic brief instead of accepting it, and whether they report a pipeline honestly when it is thin.
What the job actually involves
A recruiter runs a pipeline from brief to offer: agreeing what the role actually needs, sourcing, screening, coordinating other people's interviews, and managing both sides of an offer. Much of the day is chasing (hiring managers for feedback, candidates for availability) and the skill is keeping momentum without becoming a nuisance to either.
The part that separates good recruiters is the front end. A brief accepted uncritically produces months of wasted sourcing against a role that doesn't exist at that salary. A recruiter who can say 'this combination isn't available for this money, here are two versions that are' saves more time than any sourcing technique.
The questions, and what a good answer sounds like
Ask these as written. Each one is paired with what a strong answer sounds like, so two people rating the same candidate reach the same conclusion for the same reason.
1. A hiring manager gives you a brief you think is unrealistic. What do you say?
A good answer: Says so with evidence (market data, comparable searches, what the salary actually buys) and offers alternatives rather than just objecting. This is the highest-value behaviour in the role and the one most recruiters can't demonstrate.
2. How do you tell a candidate who reached the final round that they didn't get it?
A good answer: Promptly, by phone or video for a final round, with a real reason. Strong answers mention doing it the same day the decision is made. Candidates who describe an email template are describing your employer brand in six months.
3. Your pipeline for a role is thin and the update meeting is tomorrow.
A good answer: Reports it accurately with a diagnosis and a proposed change. The failure mode is padding the pipeline with candidates who won't convert, which buys a week and costs a month.
4. How do you write a first outreach message to someone not looking?
A good answer: Specific to the person, short, and honest about what it is. Strong answers say what they would leave out. Anyone whose answer is a template with merge fields is generating the messages everyone deletes.
5. A hiring manager keeps not giving you interview feedback.
A good answer: Escalates the consequence instead of the annoyance — candidates dropping out, offers lost to faster competitors. Making it their problem in concrete terms is what actually changes behaviour.
6. Tell me about a hire that didn't work out.
A good answer: Owns a part of it, and names what they would screen differently now. A recruiter who has never had a bad hire has either not made many or isn't tracking them.
7. How do you screen for something you don't personally understand, a technical or specialist skill?
A good answer: Uses a structured input from someone who does: agreed criteria, a technical screen, or specific questions written with the manager. The wrong answer is keyword matching, which is how good candidates get filtered on formatting.
8. What do you do when a candidate accepts and then goes quiet before the start date?
A good answer: Stays in contact deliberately through the notice period, and treats silence as a signal rather than a formality. Strong answers describe a plan instead of hoping.
A scorecard you can rate against
Rate every candidate 1 to 4 on each row, and write the rating down before you watch the next one. Ratings drift badly when they're relative to whoever you just saw.
| Criterion | What a 4 looks like |
|---|---|
| Pushing back on a brief | Challenges with evidence and offers alternatives. A 2 accepts it and sources anyway. |
| Candidate experience at no | Rejects final-round candidates personally and same-day with a real reason. A 2 sends a template. |
| Honest pipeline reporting | Reports a thin pipeline with a diagnosis. A 2 pads it to buy time. |
| Outreach quality | Writes specifically to a person and says what they would omit; a 2 describes a template. |
| Screening outside their expertise | Builds criteria with the manager. A 2 keyword matches. |
How to run the screen
- Lead with the unrealistic brief question. It is the highest-value behaviour in the role and the one that separates recruiters most sharply.
- Ask them to write, not just speak. Much of recruiting is written outreach, so pair the recorded answers with a short written task: one outreach message to a named profile.
- Don't weight placement counts. They depend on market, brief and brand, and they transfer poorly. The behaviours above transfer.
- Check how they talk about candidates, not just about clients. A recruiter who describes candidates as inventory will produce the candidate experience that description implies.
- Use the live round on a real brief of yours. Give them one of your open roles and see whether they ask the questions the brief question suggested they would.
Running this on a large applicant pool is where it gets expensive. VoxScreen sends these questions as a single link, transcribes and scores every answer against criteria you set, and hands back a ranked list. Free for 50 candidates a month, no card.
Common hiring mistakes for this role
- Hiring on placement numbers. They are the least portable signal available and they mostly measure the desk someone sat at.
- Not testing the brief conversation. Accepting bad briefs is the most expensive habit in recruiting and it is invisible in a CV.
- Skipping the rejection question. It is the clearest window into candidate experience, which is the thing your employer brand is actually made of.
- Using only a recorded interview. Recruiting is heavily written, and a recorded answer doesn't test outreach writing at all. Pair it with a written task.
- Screening recruiters the way you would screen salespeople. There is overlap, but a recruiter who only optimises for closing will damage both candidate experience and hiring manager trust.
Common questions
What should I ask when interviewing a recruiter?
Start with what they say to a hiring manager whose brief is unrealistic: it is the highest-value behaviour in the role and the hardest to fake. Then ask how they reject a final-round candidate, what they do when a pipeline is thin before a review meeting, and how they screen for a skill they don't personally understand.
Should I hire a recruiter based on placements made?
Weight it lightly. Placement counts depend heavily on the market, the brief quality and the employer brand someone was carrying, and they transfer poorly between contexts. The behaviours that do transfer — challenging briefs, honest pipeline reporting, candidate experience at rejection — are all visible in a well-designed interview.
How do I test candidate experience in a recruiter interview?
Ask exactly how they deliver a final-round rejection, and listen for speed, channel and whether a real reason is given. Then listen to how they refer to candidates across the whole interview. A recruiter who talks about candidates as inventory will run a process that feels that way, whatever they say about experience when asked directly.
Should recruiter interviews include a written task?
Yes. A large share of the job is written outreach, and a recorded answer tests speaking rather than writing. One short task, an outreach message to a named public profile, tells you more about day-to-day effectiveness than a fifth spoken question, and it takes the candidate five minutes.