Free download. Use it offline or customize it for your company.
Welcoming questions
Can you tell us about yourself and the roles and industries you have hired for?
What to look for: A strong answer covers breadth of functions and seniority levels with rough volumes, showing they know which markets they are fast in and which they'd need to learn.
Sample answer: I've been in talent acquisition for five years, first at a staffing agency doing high-volume retail and logistics hiring, then in-house at a fintech scale-up. There I owned engineering and product roles, roughly 40 hires a year, plus occasional leadership searches. My sweet spot is technical hiring in competitive markets, though the agency years taught me speed and pipeline discipline I still use daily.
What does great talent acquisition look like to you, beyond filling seats?
What to look for: Look for a view of TA as a forward-looking system, with pipelines, data, and candidate experience; a red flag is describing it purely as reacting to requisitions.
Sample answer: To me it's the difference between fishing when you're hungry and keeping the pond stocked. Great TA means when a critical role opens, I already have five warm people to call because I mapped that market months ago. It also means the process itself is an asset: structured interviews that predict performance, and candidates who speak well of us even when rejected. Filling seats is the output; the pipeline and the process are the actual job.
Role-specific and technical questions
Walk us through a sourcing strategy you built for a hard-to-fill role.
What to look for: Expect a specific role, a market analysis, multiple deliberate channels, and results in numbers; vague talk about posting on more job boards is a red flag.
Sample answer: We needed a senior DevOps engineer with Kubernetes experience in a city with maybe 200 people fitting the profile. Job ads had produced nothing in two months, so I mapped the local companies running similar stacks and built a list of about 80 names from LinkedIn and GitHub activity. My outreach referenced their actual open-source work, which got a 34 percent reply rate versus our usual 12. I also asked our own engineers to review the list for people they knew, which surfaced two referrals. We hired one of them in week seven.
How do you build a talent pipeline for a role before it officially opens?
What to look for: A strong answer includes partnering with leadership on headcount plans and concrete nurture tactics, not just collecting resumes in a folder.
Sample answer: It starts with the headcount plan: I meet department leads quarterly to learn what they expect to open in the next six months. For each likely role I build a shortlist of passive candidates and start light-touch contact, a relevant article, a coffee chat, an invite to a company event, nothing salesy. I tag them in the ATS by readiness so that when the requisition lands, my first week is calls to people who already know us. For a product manager role last year that cut time to fill from about 60 days to 24.
Which sourcing tools and Boolean techniques do you actually use day to day?
What to look for: Look for hands-on fluency with specific operators and platforms and knowing when Boolean beats a platform's own filters; buzzword lists without examples are a warning sign.
Sample answer: LinkedIn Recruiter is my base, but I still write raw Boolean because the filters miss people who describe themselves unusually. A typical string for a backend search would combine title synonyms with OR, the must-have stack in quotes, and a NOT block to strip out agency recruiters and students. For engineers I also do X-ray searches on GitHub through Google, site:github.com plus language and location terms, because activity there tells me more than a resume. And I keep a spreadsheet of which string produced which hires, so I stop reinventing searches.
How do you design a structured interview process, and how do you train interviewers on it?
What to look for: Strong candidates define success criteria first, map each competency to a specific stage with scoring anchors, and describe realistic interviewer calibration, not just a slide deck.
Sample answer: I start from the scorecard: with the hiring manager I define four or five competencies that actually predict success in the role, then assign each one to a specific stage so nothing is assessed twice and nothing is skipped. Every competency gets behavioral questions and a simple anchored scale, one to four with written descriptions of what each score means. For training, I run a one-hour session with practice scoring on a recorded mock interview, because watching people score the same answer differently is what convinces skeptics. Then I sit in on each interviewer's first two panels and debrief with them after.
Which funnel metrics do you monitor, and can you describe a change you made because of them?
What to look for: Look for stage conversion and source quality metrics tied to an actual intervention with a measured outcome, not just a recitation of time to fill.
Sample answer: My core set is pass-through rate per stage, source of hire quality, offer acceptance rate, and pipeline coverage for upcoming roles. The most useful catch: our onsite-to-offer conversion for sales roles was 65 percent, but offer acceptance was only 55, well below our 80 percent average elsewhere. Exit surveys showed candidates were hearing the compensation range for the first time at offer stage. We moved the comp conversation to the first screen, and acceptance climbed to 78 percent within two quarters.
Behavioral and culture fit questions
Tell us about a time you pushed back on a hiring manager's unrealistic profile. What happened?
What to look for: A strong answer uses market data to negotiate scope rather than either caving silently or fighting without evidence.
Sample answer: A hiring manager wanted ten years of experience in a framework that had existed for six, plus fluency in three languages, at a mid-level salary. Instead of arguing in the meeting, I ran a quick market scan and came back with numbers: 14 people in the country matched the full wishlist, and their current salaries. Then I asked which requirements actually predicted success versus which were nice to have. We agreed to drop one language and trade years of experience for a practical assessment. The role filled in five weeks, and that person got promoted within a year.
Describe how you kept candidates warm during a slow or frozen hiring process.
What to look for: Look for proactive, honest communication on a set cadence; a red flag is going silent and hoping candidates wait around.
Sample answer: During a two-month budget freeze we had three finalists for a role that suddenly stalled. I called each one personally, told them the truth without overpromising, and asked whether they wanted weekly or biweekly check-ins. On each check-in I gave them something real, a company update or a piece of relevant news, so the message wasn't just still frozen, sorry. Two of the three were still available when we reopened, and one told me the honesty was why he waited.
What have you done to improve an employer brand with little or no budget?
What to look for: Expect scrappy tactics that leverage existing employees and content, with some signal of impact rather than aspiration.
Sample answer: At my last company we had almost no employer brand presence, so I started with what was free: our own people. I interviewed five engineers about their projects and turned each into a short blog post and a LinkedIn post they shared themselves, which reached far more relevant candidates than the company page ever did. I also cleaned up our review-site responses, replying to every review including the rough ones. Within six months our inbound applications for technical roles roughly doubled, and candidates started mentioning the posts in screens.
Problem-solving and case questions
We need to hire 20 engineers in two quarters in a competitive market. Sketch your plan.
What to look for: Strong candidates work the math backwards from funnel conversion, address interviewer capacity as a bottleneck, and combine channels rather than betting on one.
Sample answer: First the math: at typical conversion rates, 20 hires means roughly 400 to 500 qualified candidates entering the funnel, so this is a capacity problem before it's a sourcing problem. I'd check interviewer bandwidth immediately, because 20 hires can mean 150 onsite loops and that breaks teams if unplanned. On sourcing, I'd run three channels in parallel: an aggressive referral push with a temporary bonus increase, targeted outbound on the top two or three competitor talent pools, and one agency for the hardest two or three profiles. Weekly funnel reviews against a hiring plan per role, so we know by week four, not month four, if we're behind.
Your best-performing source suddenly dries up. How do you diversify quickly?
What to look for: Look for a diagnosis step before action and a portfolio mindset about channels; panic-spending on agencies as the first move is a red flag.
Sample answer: First I'd confirm it's actually the source and not us: did our response time slip, did a competitor raise salaries, did the job ad change? If the channel is genuinely dead, I'd look at where our last 20 good hires actually came from and double down on the second and third sources while they're still warm. Referrals usually bounce back fastest, so I'd relaunch that program with fresh energy, personal asks rather than a mass email. Longer term, this is why I track source mix monthly; no single channel should ever carry more than about 40 percent of hires.
Candidate drop-off doubles at the technical interview stage. How do you investigate and fix it?
What to look for: Expect them to segment the data into withdrawals versus rejections before proposing fixes, and to gather evidence from candidates and interviewers.
Sample answer: First question: are candidates failing the interview or withdrawing from it? Those are opposite problems. I'd pull the data by interviewer, by role, and by time period to see when it started, and I'd call five recent drop-offs personally, since exit surveys understate the real reasons. If it's withdrawals, common culprits are scheduling lag, an interviewer being hostile, or a take-home that grew too long; I once found a four-hour assignment that a well-meaning team lead had quietly doubled. If it's failures, either sourcing quality slipped or the bar drifted, so I'd review scorecards for calibration. Then fix the specific cause and watch the stage conversion for the next month.
Generate custom Talent Acquisition Specialist interview questions
Need questions tuned to your industry, seniority level, or interview stage? Describe the role and our AI interview questions generator will draft a set in seconds.
