HR and recruiter interviews test how you run a hiring process end to end — sourcing, structured interviewing, negotiating offers, and building a pipeline instead of triaging one candidate at a time. Below are the most common questions with model answers.
Every question comes with a model answer you can compare yours against.
1
How do you decide which sourcing channels to use for a hard-to-fill role?
Answer
Start from where the target candidates actually spend time, not from the channels you're used to — a niche technical role needs targeted outreach on LinkedIn or GitHub, while a high-volume role is better served by job boards and referrals. Track cost-per-hire and quality-of-hire by channel so the mix is a decision based on data, not habit. When a channel stops converting after a few weeks, that's the signal to pivot rather than push more requisitions through it.
2
What do you cover in a 20-minute phone screen?
Answer
Confirm the basics that would disqualify someone outright — location, visa status, salary expectations, notice period — before spending time on anything else. Then probe motivation and one or two must-have qualifications with a specific example, not a yes/no question. The goal isn't to fully evaluate the candidate, it's to decide whether the next 45 minutes of a hiring manager's time is worth spending.
3
How do you use an ATS to keep a pipeline organized rather than just log candidates?
Answer
Every candidate needs a current stage, an owner, and a next action with a date — an ATS that just stores resumes is a filing cabinet, not a pipeline. Use it to spot where candidates are stalling: a stage where people sit for two weeks longer than any other is a process problem, not a coincidence. Tagging rejection reasons consistently also means six months later you can answer why a role took so long to fill.
4
How do you write a job description that attracts the right candidates without scaring off good ones?
Answer
Separate what's actually required from what's nice-to-have — a list of fifteen "must-haves" filters out qualified people who'd have applied for eight. Lead with what the person will actually do and own, not a wall of company boilerplate, because that's what candidates skim for first. And watch for gendered or exclusionary language — "ninja," "rockstar," unnecessary degree requirements — since it measurably shrinks the applicant pool without improving quality.
5
What is a structured interview, and why does it reduce bias compared to an unstructured one?
Answer
A structured interview asks every candidate for a role the same core questions in the same order, scored against a shared rubric — the structure is what makes comparisons fair rather than a comparison of who the interviewer liked more. Unstructured interviews feel more natural but let first impressions and affinity bias drive the outcome, which research consistently shows correlates poorly with job performance. The trade-off is that structure takes more upfront design work, but that's cheaper than a bad hire.
6
How do you build a compensation band, and what do you do when a candidate has a competing offer?
Answer
Start from market data for the role, level, and location — not from what the last person in the seat made — and set a band wide enough to cover a range of experience without being so wide it's meaningless. When a competing offer comes in, find out what actually matters to the candidate — is it the number, the role, the growth path — before assuming it's a bidding war, because sometimes a faster process or a clearer growth conversation wins over a slightly higher number. Chasing every counteroffer with money trains your best candidates to always ask for more, so I'd rather lose one hire than break the comp structure for everyone else.
7
What does a good onboarding plan look like in the first 90 days?
Answer
The first week should answer "do I have what I need and do I know who to ask," not throw someone into their first real task with no context. By 30 days they should have completed a small, real piece of work with feedback; by 60 they're contributing independently on routine tasks; by 90 there's a formal check-in tied to the goals set at hire. Onboarding that's just paperwork and a laptop setup is why new hires quit in the first three months — they never actually got oriented.
8
How do you use exit interview data to actually reduce attrition, not just collect it?
Answer
A single exit interview is an anecdote; the same reason showing up across a team or a manager over two quarters is a pattern worth acting on. I look for clusters by team, tenure, and manager rather than treating each departure as an isolated case, and I cross-reference exit reasons against engagement survey data to catch problems before people are already out the door. The failure mode is collecting the data and filing it — it only works if it changes a manager's behavior or a policy.
9
How do you improve candidate experience without slowing down a lean hiring process?
Answer
Most of candidate experience is just communication — telling people where they stand and by when, even when the answer is no. Automating status updates and rejection emails through the ATS covers the volume; that frees up personal time for the handful of finalist conversations that actually need a human touch. A slow, silent process costs you good candidates who accept elsewhere before you've even decided, so speed and communication are part of quality, not a trade-off against it.
🦎
Reading answers is not enough
In a real interview you speak under pressure. Cam asks these same questions, scores every answer, and shows exactly what to fix.
Practice a HR / Recruiter interview →Free · 3 interviews per month