Two different people search this phrase, so let's separate them in one sentence.
If you are a candidate about to have a screening call with a recruiter, that's a different situation with different questions, and there's a guide for it: how to ace the recruiter screen. This article is for the other one — you are interviewing for a recruiting role, and the people across the table interview for a living.
That last part changes everything about how these questions are graded. A hiring manager evaluating a recruiter is watching a live demonstration of how you'll treat their candidates: how you listen, how quickly you generalise, whether you ask before advising. The content of your answer is only half of it.
The job itself is a series of judgement calls with no clean answer, and the interview is organised around the same five.
Who to source, and who to skip
The opening round, and often a live exercise rather than a question.
- Build me a pipeline for a role you know nothing about. Where do you start?
- Write the outreach message you'd send to a senior engineer who isn't looking.
- The hiring manager says there's nobody out there. How do you respond?
- You've sourced the obvious candidates and they all said no. Now what?
Saying it out loud: question 2 is frequently a real writing exercise, and almost every candidate produces the same message — a compliment, the company's funding round, and a request for fifteen minutes. What separates a good answer is naming why yours would get a reply: "I'd cut everything that could be sent to a hundred people. One specific line about their actual work, one sentence on the problem the team is solving rather than the company's stage, and a clear ask. And I'd say why them — if I can't finish that sentence honestly, the message shouldn't go."
Question 3 is a test of how you disagree with a hiring manager. "There's nobody out there" is almost always a search problem or a bar problem, and saying so requires evidence rather than opinion — which is the answer.
Who to pass, and who to reject
The assessment round. Where interviewers find out whether your screen means anything.
- What do you actually assess in a thirty-minute screen?
- A candidate looks excellent on paper and poor in the screen. What do you do?
- How do you avoid passing people who are just good at interviews?
- A hiring manager rejects everyone you send. What's your move?
Saying it out loud: question 5 is where weak candidates list what they ask and strong ones name what they're deciding: "Thirty minutes only answers three things honestly — can they do the core of the job, is the level roughly right, and do the practicalities work. I'm not trying to assess depth, because I'd get it wrong and the technical round exists for that. What I do want is enough specific detail that I could defend passing them to a sceptical hiring manager, which is a higher bar than 'seemed good'."
Question 8 is the most senior question in this section. The answer that scores treats the rejection pattern as data about the brief, not about the candidates — and includes going back and asking to see two people the manager would hire, so the standard becomes concrete rather than adjectival.
A pattern worth noticing in the first two sections: the strong answers all converted something vague into something specific — “nobody out there” into a search or bar problem, “seemed good” into a defensible detail, a generic outreach into one line that could only be sent to one person. Recruiting is largely the work of making vague things concrete before they become expensive, and every question in this list is a chance to demonstrate the habit.
When to push back on the hiring manager
The stakeholder round. Weighted heavily above junior level.
- The job description wants ten years of experience in a five-year-old technology. What do you say?
- How do you get feedback out of a hiring manager within a day?
- The bar seems to move between candidates. How do you handle that?
- How do you run a debrief where one loud opinion doesn't decide the outcome?
Saying it out loud: question 10 sounds like a chasing question and is really a design question. Candidates describe how politely they'd follow up; interviewers want to hear that you'd remove the need to follow up at all: "Chasing is a symptom. I'd agree the turnaround as part of taking the role on, put the debrief in the calendar before the interview happens rather than after, and make the feedback form short enough to complete in the meeting. Most delay comes from asking busy people to start a task later, so I'd rather they finish it while they're still in the room."
Escalating the moving bar
“I'd raise it with the hiring manager and ask them to be consistent.”
Reasonable, and it depends on the other person agreeing that they've been inconsistent — which nobody does when it's put to them that way. It also frames the problem as their behaviour rather than the process.
Making the bar visible
“I'd take the last four decisions back to them and ask what made the difference between the two we advanced and the two we didn't. Usually the criteria are real but unwritten — and once they're written, the inconsistency mostly resolves itself without anyone being told they were inconsistent.”
Same outcome, no confrontation, and you've produced a scorecard the next five candidates get judged against.
What to tell a candidate you might lose
Often role-played. This is where they find out how you behave under commercial pressure.
- Your best candidate has a competing offer. Take the call.
- How do you deliver a rejection to someone who reached the final round?
- A candidate asks for more than the band allows. What do you do?
- How do you keep a candidate engaged through a slow process you don't control?
Saying it out loud: question 13 is where an interviewer finds out whether you'd pressure someone. The instinct to avoid is selling harder: "I'd ask what the other offer gives them that ours doesn't, and I'd genuinely want the answer rather than a chance to rebut it. If it's money, I can find out quickly whether we can move. If it's the work, the team, or the manager, then more money won't fix it and pretending otherwise gets me a hire who leaves in six months. I'd rather lose a candidate honestly than close one badly."
That last sentence is not a throwaway. Everyone on the panel has inherited a candidate who was closed badly, and the cost landed on them.
What your numbers are saying
Short round, and the one that most often exposes a candidate who has coasted on relationships.
- Which recruiting metrics do you actually use, and which are vanity?
- Time-to-hire has gone up. Where do you look first?
- How do you know whether your screen is any good?
- What would you change about how your last team hired?
Saying it out loud: question 19 is the sharpest question in the list, because most recruiters have never checked. The honest answer beats a confident one: "The only real test is what happens after the screen — what share of the people I pass get an offer, and whether the ones rejected later were rejected for something I could have caught. If nearly everyone I pass fails the technical round, my screen is too generous. If nearly everyone passes, it's probably too harsh and I'm rejecting people the team would have hired."
Question 20 is an invitation to be specific about a former employer without being bitter about it. Interviewers are calibrating both.
What the panel is reading between the answers
Recruiting interviews are unusual in that your interviewers do this professionally. They notice whether you asked what the role actually needs before advising, whether you talked over the end of their question, and whether your written follow-up is as good as your outreach claims to be.
None of that is on the question list, and all of it is being scored. The most common self-inflicted wound is filler — a recruiter who is hard to listen to is a hard sell to candidates, and the panel hears it immediately. That's fixable, and worth fixing before the call: how to reduce filler words.
Practical target: record yourself answering question 2 out loud — the outreach message — then write it down and compare. If the spoken version is vaguer than the written one, that gap is exactly what a hiring manager will hear when you pitch their role to a candidate, and it's the single most transferable thing you can improve before the interview.
