By Johnny Campbell
Introduction
Every sourcer can find the people who are findable. Type the job title into LinkedIn Recruiter, add the location filter, add a skills filter, and you get the same 200 profiles your competitor got this morning, half of whom have already been messaged three times this quarter. That search is not the job. The job is the 40 people who do not appear in it — the ones whose title is “Member of Technical Staff” rather than “Backend Engineer,” the ones who left the industry for two years and came back, the ones who only exist as a name on a conference speaker list, a GitHub commit history or a professional body’s membership directory. The gap between a sourcer and a good sourcer is not Boolean syntax. It is whether they can look at a search returning nothing useful and work out where else those people leave a trace.
Three mistakes show up again and again in sourcer interviews. The first is testing tool familiarity instead of search reasoning — asking which platforms someone has used, as though LinkedIn Recruiter or SeekOut experience predicts anything. It does not. Tools are learnable in a fortnight; knowing which population to search for takes years. The second is measuring the wrong output. Candidates get asked how many profiles they sent, when the number that matters is how many were accepted by the recruiter and how many reached a screen. The third is never asking about response rates at all, which is remarkable, because it is the single number that exposes outreach quality. A sourcer who cannot tell you roughly what percentage of their messages get a reply either has not measured it or does not want you to know.
The questions below are behavioural and situational. Every one asks for something that happened, with a real role attached, so you can push on specifics until you find out whether the story holds. They cover search craft, market mapping, outreach, pipeline building for genuinely hard reqs, and how well the person works with the recruiters they hand over to.
Core Competencies for a Great Sourcer Hire
Sourcing is a research discipline with a sales function bolted on, and the best sourcers are unusually strong at both ends. Start with Technical Skill — search construction, data sources, and knowing what a job actually involves well enough to recognise an adjacent skill set — and Attention to Detail, because a mis-parsed date range or an unchecked location assumption quietly poisons a whole pipeline. Innovation matters more here than in almost any other TA role, since the searches that produce results are by definition the ones nobody else has run. Look for Communication Skills in the specific form of written outreach that a busy stranger will read to the end, and Ownership of outcomes rather than activity — sourcers who track their work through to hire behave differently from sourcers who track it to send. Finally, Influence and Persuasion and Business Acumen together determine whether the person can tell a hiring manager the talent pool they have asked for does not exist at that salary, and be believed.
Search Craft and Boolean Reasoning
What good looks like
A strong candidate can describe the actual search logic — which terms they used, why, and what didn’t work — rather than naming a tool. They can explain how they reasoned from a job title that returned nothing to a population that might actually hold the skill, and point to a specific search they abandoned and rebuilt, with the reasoning for the rebuild, not just the fact of it.
Behavioural questions
- Walk me through the hardest search you have ever run.
- What made this search harder than a typical one?
- What was your first approach, and why didn’t it work?
- What did you try that eventually got results?
- How long did the whole search take, roughly?
- Tell me about a time your first search returned nothing useful.
- What was the search, and what did you expect to find?
- What did you do in the first hour after it returned nothing?
- What population or source did you try next?
- What did you learn about the search that you use again now?
- Describe a search where you found strong candidates in a place your colleagues were not looking.
- Where did you find them, and why weren’t your colleagues looking there?
- What made you think to look there in the first place?
- How did you validate they were actually a fit?
- Did the approach get adopted more widely afterwards?
- Tell me about a time you realised you had been searching for the wrong job title.
- What was the original title, and what tipped you off it was wrong?
- How did you find the right title or terms?
- How much of the search did you have to redo?
- What do you check for now before committing to a title?
- Give me an example of a search you rebuilt from scratch partway through a req.
- What made you decide to start over rather than adjust?
- What was wrong with the original approach?
- What did the rebuilt search look like differently?
- Did the rebuild actually work?
Situational scenario
You’re three days into sourcing for a niche technical role. Your searches based on the job title and obvious skill keywords have returned the same 30 profiles your colleague already contacted last quarter, none of whom responded then.
Walk me through what you do next.
Then introduce a constraint: “The hiring manager tells you the title on the req is exactly what they’re looking for and doesn’t want you to widen it.”
What to listen for
Whether they reason about adjacent titles or communities rather than tweaking the same search, whether they can articulate the disagreement with the hiring manager in terms of population size rather than opinion, and whether they actually change where they’re looking rather than searching the same well again.
Talent Market Mapping and Intelligence
What good looks like
A strong candidate can give you an actual number or range from a market map, not a vague impression, and describe how they arrived at it. They can point to a specific decision — a salary band moved, a location widened, a headcount plan changed — that happened because of their map, and they’re willing to describe a market read that turned out wrong and what they’d missed.
Behavioural questions
- Tell me about a talent pool you mapped that turned out to be smaller than the business believed.
- What did the business believe the pool size was, and why?
- How did you actually establish the real number?
- What did you tell them, and how did they react?
- What changed as a result, if anything?
- Describe a market map you built that changed a hiring decision.
- What was the decision it changed?
- How did you build the map — what sources, what method?
- Who did you present it to, and what pushback did you get?
- What happened after the decision changed?
- Tell me about a time you told a hiring manager something they did not want to hear about the market.
- What was the uncomfortable finding?
- How did you decide to raise it rather than soften it?
- What did you actually say?
- How did they respond, and what changed?
- Walk me through how you mapped a market you knew nothing about at the start.
- What was the market, and what did you know at the start?
- Where did you go first to get oriented?
- What surprised you once you understood it better?
- How long did it take before you trusted your own read?
- Describe a time your read on a market turned out to be wrong.
- What was your original read, and what was it based on?
- What told you it was wrong?
- What did you do once you realised?
- What do you do differently now to sanity-check a read?
Situational scenario
A hiring manager asks you to map the market for a specialised role before opening a req, confident there are “plenty of people out there.” Your early digging suggests the real pool, in the location and salary band they want, is under twenty people globally.
Walk me through how you build and present that finding.
Then introduce a constraint: “The hiring manager’s director is in the meeting and visibly doesn’t want to hear that the plan isn’t realistic.”
What to listen for
Whether they bring a defensible number rather than an impression, whether they present the finding as a decision to be made rather than an obstacle, and whether they hold the line under pressure from someone senior in the room rather than soften the number.
Outreach and Response Rates
What good looks like
A strong candidate can quote or closely paraphrase their own outreach message and explain the specific choice — a subject line, an opening line, a personalisation detail — that they think drove the response. They can give you an actual response rate figure or a credible range for a campaign, and describe changing an approach mid-campaign based on real data rather than a hunch.
Behavioural questions
- Tell me about your best-performing outreach message and why you think it worked.
- What did the message actually say?
- What specifically do you think made it land?
- What was the response rate, roughly?
- Have you reused that approach since, and did it work again?
- Describe a campaign where your response rate was worse than you expected.
- What response rate were you expecting, and what did you get?
- What did you think was wrong with the message or targeting?
- What did you change?
- Did the change improve things?
- Tell me about a candidate who replied to you after ignoring several previous approaches.
- How many times had you approached them before, and how?
- What was different about the message that finally landed?
- What did they say when they replied?
- Did it turn into a hire?
- Walk me through a time you changed your outreach approach mid-campaign.
- What told you the original approach wasn’t working?
- What did you change, specifically?
- How long did you give the new approach before judging it?
- What was the result?
- Describe the most difficult person you have ever persuaded to take a first call.
- Who were they, and why were they hard to reach?
- What did you try that didn’t work?
- What finally got them to agree to a call?
- What did you learn about persuading reluctant people from it?
Situational scenario
You’ve sent forty personalised messages for a hard-to-fill role over two weeks and gotten three replies, none of them positive. The hiring manager is asking why the pipeline is empty.
Walk me through what you do next with your outreach.
Then introduce a constraint: “You discover the salary band you’ve been quoting in your messages is below what this population typically expects.”
What to listen for
Whether they diagnose the actual cause of the low response rate rather than just sending more messages, whether they raise the salary problem with the hiring manager directly rather than absorbing it as their own failure, and whether they can describe what they’d test differently in the next batch.
Pipeline Building for Hard-to-Fill Roles
What good looks like
A strong candidate can describe sustained effort over weeks or months — what they tried in month one versus month three, and how their approach evolved as the easy sources dried up. They’re willing to say plainly when the brief itself was unfillable as written, and can describe rebuilding a pipeline after a wholesale rejection without simply repeating the same search.
Behavioural questions
- Tell me about the longest-running req you have sourced for.
- How long was the req open, and why did it take that long?
- What did your approach look like in week one versus week ten?
- What kept you going back to it rather than deprioritising it?
- Did it eventually fill, and how?
- Describe a search where the brief itself was the problem.
- What specifically was wrong with the brief?
- How did you identify that the brief, not your search, was the issue?
- What did you say to whoever owned the brief?
- Did it change?
- Tell me about a role you sourced for that never got filled.
- What was the role, and why do you think it never filled?
- What did you try across the life of the search?
- At what point did you or the business give up?
- What would you do differently with a similar role now?
- Walk me through how you built a pipeline for a role in a location with almost no local talent.
- What was the location, and what made talent scarce there?
- What options did you explore beyond the local market?
- What pushback did you get, and from whom?
- What did the eventual pipeline actually look like?
- Describe a time you rebuilt a pipeline after the hiring manager rejected everyone in it.
- Why did the hiring manager reject everyone?
- What did you change about your approach the second time?
- Did you push back on the rejection pattern at all?
- What was the outcome the second time round?
Situational scenario
You’ve been sourcing for a role in a small regional office for six weeks. Local talent is essentially exhausted, and the hiring manager has ruled out remote candidates because they want someone in the building daily.
Walk me through what you do to build a viable pipeline.
Then introduce a constraint: “You find three strong candidates willing to relocate, but the hiring manager says relocation packages aren’t something they’d normally approve.”
What to listen for
Whether they widen the search intelligently rather than exhaust the same shrinking pool, whether they bring the relocation option to the hiring manager as a case rather than a complaint, and whether they keep the pipeline moving while that conversation plays out.
Recruiter Partnership and Handoff Quality
What good looks like
A strong candidate can name specifically what made a recruiter partnership work — shared criteria, fast feedback, trust — rather than “good communication.” When profiles were rejected, they can describe what they did with the feedback rather than just accepting or resenting it, and walk through a real handover, including what they made sure the next person knew.
Behavioural questions
- Tell me about a recruiter you worked well with and what made it work.
- What specifically did that recruiter do that made the partnership work?
- How did you two agree on what a good profile looked like?
- What did you do differently with them versus a weaker partnership?
- What did you learn from it that you use with other recruiters?
- Describe a time a recruiter rejected most of the profiles you submitted.
- What reason did they give for rejecting the profiles?
- Did you agree with the feedback, or push back on it?
- What did you change about your submissions afterwards?
- Did the acceptance rate improve?
- Tell me about a candidate you sourced who dropped out later in the process.
- Where in the process did they drop out?
- Did you see it coming, or was it a surprise?
- What, if anything, could have been caught earlier?
- What did you change about how you qualify candidates now?
- Walk me through how you handed over a pipeline when you moved off a req.
- What was the state of the pipeline when you handed it over?
- What did you document or brief the next person on?
- What did you make sure they knew that wasn’t obvious from the ATS?
- Did anything get lost in the handover despite that?
Situational scenario
You’ve built a strong pipeline of six candidates for a role over three weeks. You’re being moved onto an urgent new req and need to hand this one to a colleague by end of day.
Walk me through what you do in the handover.
Then introduce a constraint: “The colleague picking it up has never worked this market before and the hiring manager is expecting a shortlist by Friday.”
What to listen for
Whether they hand over the reasoning behind each candidate, not just the profiles, whether they flag which candidates need a particular touch, and whether they set realistic expectations about the Friday deadline rather than let it become a surprise on Thursday.
Red flags to watch for in Sourcer interviews
Volume as the only story. They describe the work entirely as profiles sent and InMails fired, with no reference to what percentage converted to a screen. Ask twice; if the number still does not arrive, it was never tracked.
No idea of their own response rate. Not the exact figure — a range is fine. But a sourcer who has never looked at it has never iterated on their messaging.
Has never pushed back on a brief. If they have never told a recruiter or hiring manager that the talent pool they are asking for does not exist at that salary, in that location, or with that combination of skills, they have been taking orders rather than doing the job.
Tool answers to search questions. You ask how they found a difficult population; they answer with a product name. The interesting part is always the reasoning about where those people are documented, not the interface they typed into.
Only ever sourced from one place. LinkedIn-only sourcers hit a ceiling fast on genuinely hard roles.
Blames the recruiter for everything. Rejected profiles, stalled pipelines, dropped candidates — all someone else’s fault. Sourcers who never examine their own submissions do not improve.
How to structure a Sourcer interview loop
Keep it to three stages.
Stage one is a 30-minute screen with the recruiting manager, covering the roles they have sourced for, the markets they know, and their own numbers — submissions, acceptance rate, response rate. Anyone who cannot discuss those three figures in some form is unlikely to survive stage two.
Stage two is the one that matters, and most organisations skip it. Give them a live hard req from your own desk — the one that has been open four months — and have them talk through the search out loud for 30 to 40 minutes. No prep, no take-home, no scoring rubric for Boolean syntax. You want to hear them ask what the team actually does, question the title, name adjacent populations, and say out loud where those people would be documented. A strong sourcer will interrogate your brief before they build anything. A weak one will start listing search strings.
Stage three is a conversation with a recruiter they would partner with, focused on handoff quality, submission standards and how disagreements get resolved.
The risk with a loop like this is inconsistency — different interviewers asking different questions and scoring on instinct, which is exactly how good sourcers get rejected and confident talkers get through. See how Interview Intelligence standardises this across your team →
Frequently asked questions
Should sourcers be tested live in the interview?
Yes, but test reasoning rather than output. A live search walkthrough on a real open req tells you how someone thinks about a population, questions a brief and handles ambiguity. Take-home sourcing exercises are easy to outsource and mostly reward time spent rather than judgement. Forty minutes of talking through a hard search out loud is the highest-signal stage in the loop.
What is the difference between a sourcer and a recruiter?
A sourcer builds the pipeline; a recruiter owns the process. Sourcers specialise in finding and engaging people who are not applying — search, market mapping, outreach — and typically hand over at the point of interest. Recruiters manage the candidate through screening, hiring manager relationships, interviews, offer and close. The skills overlap, but the depth of search craft required for hard-to-fill roles is genuinely specialist.
What metrics should I ask a sourcer about?
Three: response rate on outreach, recruiter or hiring manager acceptance rate on submitted profiles, and candidates sourced who reached a screen or hire. Profiles sent is not a metric, it is an activity count. If a candidate volunteers submission volume without conversion, ask directly what happened to those profiles afterwards.
Can you hire a sourcer with no recruitment background?
Often, yes. Researchers, analysts, journalists and investigators bring the core instinct — finding people and information that are not surfaced by an obvious query. What you cannot skip is the outreach half. Test whether they can write something a stranger will read to the end, and whether they are comfortable being ignored most of the time.
How many questions should a sourcer interview cover?
Six to eight well-chosen behavioural questions per stage, with real follow-up on each. Depth beats coverage. One question about a hard search, pushed for four or five minutes on specifics, reveals more than eight surface-level questions. Use the capability sections in this guide to pick a spread rather than working through the whole list.