Recruiter Interview Questions and How to Answer Them

Interviewing for a recruiter job is odd, because the people across the table do your job every day and they'll spot a vague answer instantly. They want to hear how you actually fill roles: where you find people, how you run an intake, how you handle a hiring manager who keeps moving the goalposts. Below are the questions you'll get, what's behind each one, and what a strong answer sounds like.

12 questions8 minute read

Part 1

1.Walk me through how you run an intake meeting with a new hiring manager.

Why they ask

The intake decides whether the search works. A recruiter who skips it ends up sending the wrong people for six weeks.

How to answer

  • Say you book it before posting anything and come with prep: the old job description, a few sample profiles, and questions.
  • Separate must-haves from nice-to-haves, and ask what the person will actually do in their first few months.
  • Agree on the interview loop, who's on it, and turnaround times for feedback.
  • Show a calibration step, like sending three profiles in the first week to check you're aiming at the right target.
  • Mention writing it up and sending it back so nobody can claim later that the brief was different.

2.Tell me about a hard-to-fill role and how you eventually filled it.

Why they ask

Anyone can fill an easy req. They want to see what you do when the usual channels dry up.

How to answer

  • Name the role and why it was hard (niche skill, tight location, below-market pay band).
  • Explain what you changed: new sourcing channels, a reworked pitch, a conversation to loosen one requirement.
  • Be specific about the channel that worked, such as a GitHub search, a community Slack, or referrals from the team.
  • Close with the result and what you'd do sooner next time.

3.Write me a Boolean search for this role.

Why they ask

Sourcing is a hands-on skill. Talking about it and doing it live are very different.

How to answer

  • Ask a clarifying question or two first (which titles count, which location, which platform).
  • Group title variations with OR inside parentheses, then combine skills with AND.
  • Use NOT to strip out noise like recruiters or students, and explain why.
  • Say how you'd test it: run it, scan the first page, and tighten or widen based on what comes back.
4.A hiring manager has rejected every candidate you've sent for a month. What do you do?

Why they ask

This happens constantly. They want to know if you'll keep sending resumes into a void or fix the actual problem.

How to answer

  • Pull the rejection reasons and look for a pattern you can show them.
  • Book a short recalibration call instead of arguing over email.
  • Bring evidence: how many people fit the full list, and what the pay band attracts.
  • Propose a trade, like dropping one requirement or adjusting the level.
  • Loop in your own manager or the HRBP if it stays stuck, and say so openly to the hiring manager.
5.How do you approach a passive candidate who isn't looking?

Why they ask

The best people often aren't applying. Your outreach decides whether they ever reply.

How to answer

  • Personalize the first line with something real from their profile or work.
  • Keep it short and say why this role fits them, not just what the company is.
  • Ask for a brief chat, not a commitment to apply.
  • Follow up a couple of times with something new each time, then stop politely.
  • Mention tracking reply rates and tweaking the message when it isn't working.

Part 2

6.How many open reqs have you carried at once, and how do you keep them all moving?

Why they ask

Load is real. They need to know you can run a full desk without candidates falling through the cracks.

How to answer

  • Give an honest number and the mix (for example, several senior roles plus a batch of volume hires).
  • Explain how you prioritize, usually by business urgency and how close each req is to an offer.
  • Describe your daily system: ATS views, a pipeline review each morning, time blocked for sourcing.
  • Say how you keep candidates warm, like a same-day reply rule after interviews.
7.Tell me about an offer that fell apart. What happened?

Why they ask

Closing is where recruiters earn their keep. How you talk about a loss shows whether you learn from it.

How to answer

  • Pick a real loss, like a counteroffer or a competing offer you didn't know about.
  • Admit what you missed, usually that you didn't ask about other processes or motivations early enough.
  • Explain what you do differently now, such as pre-closing on every call and asking what would make them say no.
  • Keep it short and don't trash the candidate.
8.How do you talk about pay with a candidate early in the process?

Why they ask

Misaligned pay kills offers late, after everyone has invested hours. They want someone who surfaces it early and handles it fairly.

How to answer

  • Raise it on the first call, not at the offer stage.
  • Share the range where you can, and follow any pay transparency rules in the locations you hire for.
  • Ask for expectations in a way that doesn't pressure them, and never lowball because you can.
  • Flag a gap to the hiring manager right away rather than hoping it resolves itself.
9.What recruiting metrics do you watch, and how have you used them?

Why they ask

Good recruiters manage their own funnel. They want to see you notice problems in the numbers before your manager does.

How to answer

  • Name the ones you actually track: time to fill, pass-through rates at each stage, offer acceptance, source of hire.
  • Give an example where a number told you something, like a big drop between screen and onsite.
  • Say what you changed because of it, such as a tighter phone screen or better interviewer prep.
  • Show you know metrics can be gamed and quality of hire matters more than speed.
10.How do you make your hiring process fairer?

Why they ask

Recruiters shape who even gets considered. They want concrete habits, not a slogan.

How to answer

  • Write job descriptions around what the job needs and cut requirements that screen people out for no reason.
  • Use the same structured questions and scorecards for every candidate on a req.
  • Source from places that reach people your usual channels miss.
  • Push back when feedback is vague, like 'not a culture fit', and ask for specifics.
  • Stay within employment law and bring in HR or legal on anything unclear.

Part 3

11.Tell me about a time you gave a candidate bad news.

Why they ask

Rejections are most of the job. How you handle them shapes the company's reputation and your future pipeline.

How to answer

  • Pick a case where the person had invested a lot, like a final round rejection.
  • Say you called rather than emailed, and did it quickly.
  • Share whatever useful feedback you could, within company policy.
  • Mention staying in touch, and if it happened, that they later came back for another role or referred someone.
12.Why recruiting, and why in-house (or agency) now?

Why they ask

Agency and in-house are different jobs. They want to know you understand the switch and won't miss what you're leaving.

How to answer

  • Give a real reason you like the work, tied to something you've done.
  • Be clear about what's different: fewer clients, deeper partnership, longer relationships, or faster pace and commission if it's the other way.
  • Say what you'll bring from your past setup, like agency speed or in-house stakeholder skills.
  • Tie it to this company's hiring plan if you know it.

Questions to ask them

Ask at least two. It shows you're picking them too.

  • How many reqs would I carry, and which of them are the hardest right now?
  • How involved are hiring managers here, and how fast do they usually give interview feedback?
  • What does the team use for sourcing and the ATS, and is there budget for tools or job boards?
  • How do you measure a recruiter's performance in the first few months?
  • What's one hiring process problem the team is trying to fix?