Interview questions

Recruiter interview questions with model answers (2026)

Questions that show whether a candidate can fill your pipeline with the right people, screen them fairly, keep your ATS honest and hand your managers a short list worth their time.

A recruiter decides who your hiring managers ever get to meet. Every search starts with them: the people they find, the ones they screen out on a phone call, the speed of their follow-up and the notes they leave in your applicant tracking system. A strong recruiter turns a vague request like "we need another account manager" into a clear profile, a steady flow of qualified candidates and a calendar of interviews that actually happen. A weak one sends you fifty résumés, loses good people to slow replies and leaves you guessing why the role is still open. These recruiter interview questions are built to tell the two apart.

They are written for owners and managers at small and mid-size businesses who are hiring their first in-house recruiter, adding sourcing help for a busy hiring season, or bringing recruiting for several locations under one person. The recruiter you hire finds, screens and schedules; you and your managers still decide who gets the offer. Each question below includes a model answer and a note on what separates a strong reply from a weak one.

How to use these questions

Choose eight to ten questions across the four groups below. If most of your roles are hourly or high volume, weight the screening and scheduling questions. If you hire a few specialized people a year, weight sourcing and hiring manager partnership. Ask every candidate the same core questions in the same order so your notes are comparable, and use the scorecard further down to rate them straight after each conversation.

Pay attention to how the candidate treats you as a stand-in for a hiring manager. Do they ask about the role before pitching themselves? Do they summarize what you said accurately? Recruiters who listen well in an interview usually listen well to your managers too. Close with the paid exercise, built around one of your real openings.

Sourcing and building a pipeline

I tell you we need "a great operations manager." What do you ask me before you start looking?

Model answer: I'd ask what this person will own in their first 90 days, who they report to, which two or three skills are truly required versus nice to have, the pay range, the schedule and where they'll work. I'd also ask who the best person in a similar seat has been and why, and what made past hires in this role fail. Then I'd play the profile back to you in writing so we agree on it before I post anything.

Strong vs weak: Strong candidates run an intake conversation and confirm it in writing. Weak ones start searching on the title alone.

Where do you look for candidates beyond posting the job?

Model answer: It depends on the role. For professional roles I search professional networks and résumé databases with specific keyword strings, and I look at past applicants already in the ATS. For hourly roles I think about referral programs, local community groups, trade schools and job boards people in that work actually use. I also ask the team for referrals early, because referred candidates often move faster.

Strong vs weak: Strong answers match channels to the role and mention re-engaging past applicants. Weak ones only post and wait.

Walk me through a search string you'd use to find a bilingual customer support lead.

Model answer: Something like a title group in parentheses ("support lead" OR "customer service supervisor" OR "team lead"), AND a language term, AND a tool like Zendesk or Gorgias, with NOT terms to drop sales titles. I'd run it, check the first page of results, and tighten or loosen it based on what comes back.

Strong vs weak: Strong candidates write a real Boolean string and talk about testing it. Weak ones say they "use keywords."

How do you write an outreach message to someone who isn't looking for a job?

Model answer: Short, specific and about them. I mention one thing from their background that fits the role, say in one line what the job is and why it might be a step up, include the pay range if I can, and ask for a 15-minute call rather than a résumé. I follow up once or twice, a few days apart, and then stop.

Strong vs weak: Strong messages are personal and easy to answer. Weak ones are long, generic or hide the pay.

The role has been open for six weeks with almost no good applicants. What do you do?

Model answer: I look at the funnel first: how many people saw the post, applied, passed screening and got an interview. If few apply, the post, the pay or the channels are the problem. If many apply but few pass, the requirements or the screen might be off. I bring that data to the hiring manager with one or two specific changes, such as dropping a requirement that isn't essential or adding a sourcing channel.

Strong vs weak: Strong candidates diagnose with numbers and propose a fix. Weak ones blame the market.

How do you build a pipeline for a role you expect to open again in a few months?

Model answer: I tag strong runner-up candidates in the ATS, add a note on why they were good and when to reach out again, and keep a short list of passive people I've spoken to. When the role reopens, I start with those people before posting.

Strong vs weak: Look for a habit of saving silver-medal candidates. Weak answers start from zero every time.

How do you make sure your sourcing reaches a wide range of qualified people?

Model answer: I use several channels instead of one, write job posts with plain language and only the requirements that matter, and screen everyone against the same criteria. If my pipeline keeps looking the same, I add a channel and check whether a requirement is filtering out good people for no reason.

Strong vs weak: Strong answers focus on consistent criteria and broad channels. Weak ones have no method at all.

Screening and assessing candidates

What happens on your first phone screen with a candidate?

Model answer: I confirm their interest, then cover the basics that end a process early if they don't fit: pay expectations, schedule, location or remote setup, and work authorization where the role requires it. Then I ask two or three questions on the must-have skills and give them an honest picture of the job. I end by explaining next steps and when they'll hear from me.

Strong vs weak: Strong candidates screen for deal-breakers first and sell the role honestly. Weak ones chat for 30 minutes and learn little.

How do you decide whether a résumé moves forward?

Model answer: I compare it against the must-have list we agreed on, not a gut feel. Job titles vary a lot between companies, so I read what the person actually did. If it's close, I'd rather do a short call than reject someone who might be strong.

Strong vs weak: Strong answers use agreed criteria. Weak ones filter on school names, titles or gaps.

A candidate's résumé has a two-year gap. How do you handle it on the screen?

Model answer: I don't treat it as a problem by default. If it's relevant, I ask an open question like "What have you been doing since your last role?" and move on. People take time out for family, health, study or a business that didn't work, and none of that tells me whether they can do this job.

Strong vs weak: Strong candidates stay neutral and focus on the job. Weak ones probe for personal details.

What questions would you never ask a candidate?

Model answer: Anything about age, religion, marital status, pregnancy or family plans, health, national origin or other protected characteristics. If I need to confirm something like work authorization or the ability to work certain hours, I ask it the same way for everyone and only when the job requires it. When I'm unsure about a rule, I check your policy or ask before I ask the candidate.

Strong vs weak: Strong candidates know the basics and know when to check. Weak ones are vague or say "it depends on the vibe."

How do you check references?

Model answer: With the candidate's permission, I call former managers rather than friends, ask the same questions for every candidate, and ask for examples instead of ratings. A useful question is "Would you hire them again, and for what kind of role?" I write down what was said, not my interpretation.

Strong vs weak: Strong candidates run structured reference calls. Weak ones send a form and accept "they were great."

A hiring manager loves a candidate you have doubts about. What do you do?

Model answer: I share the specific concern and the evidence, for example two references that both mentioned missed deadlines, and suggest a way to test it, like a work sample. Then the decision is theirs. My job is to make sure they decide with the full picture.

Strong vs weak: Strong candidates raise concerns with facts and respect the manager's decision. Weak ones stay quiet or try to overrule.

Scheduling, ATS and candidate experience

Which applicant tracking systems have you used, and what did you keep up to date in them?

Model answer: For example Greenhouse, Lever, Workable or BambooHR. In each one I moved candidates through stages the same day something changed, logged every screen with notes and a recommendation, and kept rejection reasons consistent so we could report on them. If it isn't in the ATS, the next person can't see it.

Strong vs weak: Strong candidates describe stage hygiene and notes. Weak ones only name the tool.

You need to schedule a three-person panel this week and calendars are packed. How do you do it?

Model answer: I ask the panel for their available blocks first, then offer the candidate two or three specific times rather than "when are you free?" If one panelist can't make it, I suggest a separate short slot instead of delaying everyone. I send one confirmation with the agenda, names, links and the role summary, and a reminder the day before.

Strong vs weak: Strong answers reduce back and forth and prepare everyone. Weak ones send a dozen emails.

How quickly do you get back to candidates after each stage?

Model answer: I aim to update every active candidate within a couple of business days of a stage, even if the update is "still deciding." Good candidates have other options, and silence is the most common reason they drop out.

Strong vs weak: Strong candidates set a response habit and keep it. Weak ones contact people only when there's news.

How do you tell a candidate they didn't get the job?

Model answer: Promptly and kindly. After a phone screen, a short personal email is fine. After interviews, I'd rather call. I thank them, tell them clearly that we're moving forward with someone else, and if they were strong, ask whether I can keep them in mind for future roles.

Strong vs weak: Strong candidates close the loop with respect. Weak ones let people find out by silence.

A candidate no-shows for an interview. What do you do?

Model answer: I email and text once to check they're okay and offer one new time. If they don't respond, I update the ATS, let the hiring manager know and move to the next candidate. I also check whether my reminder process had a gap.

Strong vs weak: Look for a calm, quick reset. Weak answers either chase forever or write the person off without a message.

What does a good interview packet for a hiring manager include?

Model answer: The résumé, my screening notes with the key strengths and open questions, the agreed scorecard, the interview questions they own and the time and link. One page, sent the day before, so the manager walks in prepared.

Strong vs weak: Strong candidates make the manager's job easy. Weak ones forward the résumé and nothing else.

Offers, reporting and working with managers

How do you work with a hiring manager who is always too busy to give feedback?

Model answer: I make feedback as easy as possible: a short scorecard right after each interview and a standing 15-minute check-in each week. I share what the delay is costing, for example a strong candidate who has another offer. If it keeps happening, I raise it with the owner, because slow feedback loses people.

Strong vs weak: Strong candidates create a routine and escalate politely. Weak ones wait.

The manager decides to make an offer. What is your part?

Model answer: I prepare the offer details the manager has approved, check that they match what the candidate told me about expectations, and present it, usually by phone first. I answer questions, flag anything that might be a sticking point, and bring counter requests back to the manager. I don't promise anything that hasn't been approved.

Strong vs weak: Strong candidates know the decision and the terms belong to the company. Weak ones negotiate on their own authority.

Which numbers do you track for your recruiting work?

Model answer: Time to fill, applicants and screens per opening, pass-through rates at each stage, where hires came from, offer acceptance, and whether hires are still with us after 90 days. The last one matters most, because a fast hire who leaves isn't a win.

Strong vs weak: Strong answers include quality, not just speed. Weak ones only count résumés sent.

You're working ten open roles at once. How do you decide where to spend your time?

Model answer: I agree priorities with the owner each week, usually based on which empty seats cost the business most. I batch similar tasks, like sourcing in the morning and screens in the afternoon, and I tell managers of lower-priority roles honestly what pace to expect.

Strong vs weak: Strong candidates prioritize by business impact and communicate it. Weak ones work whatever is loudest.

Tell me about a hire you made that didn't work out. What did you change afterwards?

Model answer: A good answer names a real case, explains what was missed (for example, the screen never tested how the person handled pressure), and describes a concrete change, like adding a work sample or a specific reference question.

Strong vs weak: Strong candidates own the miss and changed the process. Weak ones blame the hire or the manager.

How do you keep candidate information private?

Model answer: Candidate data stays in the ATS and approved tools, not personal email or spreadsheets on my desktop. I share résumés only with people involved in the hire and follow your rules on how long records are kept.

Strong vs weak: Strong candidates are specific about where data lives. Weak ones haven't thought about it.

What would you want to know about our business in your first week?

Model answer: Which roles matter most this quarter, what great looks like in each, how managers like to interview, our pay ranges and benefits, what candidates say when they turn us down, and which tools and approvals I need. I'd also sit in on a few interviews to hear how the team sells the company.

Strong vs weak: Strong candidates ask about priorities and people. Weak ones only ask about logins.

Why recruiting, and what kind of recruiting do you want to do more of?

Model answer: Look for a specific reason, such as enjoying matching people to work that suits them, and an honest view of the parts they like less. Someone who says they love high-volume hourly hiring is a different fit from someone who wants long searches for senior people.

Strong vs weak: Strong answers fit the hiring you actually do. Weak ones are generic.

Red flags to watch for

A practical exercise

Give finalists a short paid exercise based on one of your real openings. Share a one-page brief for the role (duties, must-haves, pay range, schedule) and 20 anonymized sample résumés, then allow two to three hours. Ask them to return:

Then run a ten-minute role-play where you act as a busy hiring manager who wants to add three new requirements halfway through the search. Score how they handle intake, judgment, writing and pushback separately.

Recruiter interview scorecard

Rate each area from 1 to 4 after the interview and exercise. A hire should score 3 or higher everywhere, with no 1s.

AreaWhat a 4 looks likeWhat a 1 looks like
IntakeClarifies must-haves, pay and success before searchingSearches on the title alone
SourcingUses several channels, real search strings and past applicantsPosts and waits
ScreeningConsistent criteria, fair questions, clear notesGut feel, off-limits questions
Candidate experienceFast updates, respectful rejectionsSilence between stages
ATS and reportingStages current, funnel numbers on handNotes scattered or missing
Manager partnershipRaises concerns with evidence, respects the decisionStays quiet or overrules

Hire a recruiter who already works this way

Rather skip running this search yourself? Ryz can place a dedicated recruiter on your team. Your recruiter sources, screens and schedules for your open roles in your ATS, keeps your US business hours in your time zone, writes and speaks fluent English, and reports to you, month to month. You and your managers still choose who gets hired. Every recruiter we put forward has been through our vetting process, and you meet a named shortlist before anyone starts. Most start in under two weeks. Tell us the role and we'll send a plan and a price, or book a call. Writing the role first? Start from our recruiter job description template, and see the in-house numbers in our recruiter cost guide.

Related

FAQ

How many interview rounds should a recruiter hire have?

Three usually works: a short screen, a structured interview with a hiring manager role-play, and a paid exercise with a debrief. Include at least one manager the recruiter will support day to day.

Should I hire a recruiter from an agency background?

Agency recruiters tend to be strong at sourcing and pace. Check that they can also handle intake with managers, keep an ATS clean and care about how hires do after they start, which matters more in-house.

Does the recruiter make the hiring decision?

No. A recruiter finds, screens and schedules candidates and keeps the process moving. You and your hiring managers interview, decide and approve the offer.

Can an operations coordinator or assistant handle recruiting?

For one or two hires a year, scheduling help from an assistant may be enough. When you have several roles open at once, a dedicated recruiter keeps the pipeline full. See our operations coordinator interview questions for that broader role.

What should a recruiter's exercise test?

Intake, résumé judgment, outreach writing and how they handle a manager who changes the brief. Base it on a real opening so you see how they'd work on your roles.

Questions we didn't answer? Email info@ryzlabs.com.

Explore Ryz Labs

Staff augmentationDedicated development teamsAI pod teamsForward deployed engineersNearshore software developmentAI engineering teamsHire engineers by roleRyz Labs vs competitorsAlternatives guidesBuyer guidesCase studiesHow we vet engineers
Ryz Labs

Senior engineers in your time zone. AI pod teams that ship.

Tell us who you need. You'll get a scoped plan, a price and the names of the people who would do the work.

Start a conversation →