Interview guide · Recruiting and HR roles
Sourcer interview questions
In short
Good sourcer interview questions test whether a candidate can turn a vague job brief into a search strategy, find people who are not applying, write outreach that gets replies, and hand recruiters a pipeline that converts to interviews. Below are 32 questions with what to listen for, red flags, two sample answers, a live search exercise and a scorecard.
A sourcer finds and engages candidates before they apply. The job is part research and part sales: reading a requisition and working out who actually fits, building searches across professional networks, job boards, résumé databases, communities and the company's own ATS, then writing messages that get busy people to reply. Most sourcers are measured on interested, qualified candidates handed to a recruiter, and on how many of those reach interview and offer. In an agency or a high-volume team, a sourcer might work 10 to 20 open roles at once; in a technical or executive team, two or three hard ones. Either way, what separates good from average is judgment about where to look and who is worth contacting, not the number of messages sent.
Use these questions in a structured interview of about 60 minutes, followed by a 30 to 45 minute live search exercise. Ask every candidate the same core questions, push for numbers (response rates, submittals per week, conversion to interview) and score straight after. Many candidates can describe Boolean operators; far fewer can explain why a search returned the wrong people and how they fixed it. The live exercise shows that quickly.
What to look for in a sourcer
- Search craftStrong sourcers build and refine searches with Boolean logic, synonyms, title variations and X-ray techniques, and know which channel suits which role.
- Role understandingThey translate a job description into real signals: which companies, titles and skills predict a fit, and which must-haves are actually nice-to-haves.
- Outreach that gets repliesA pipeline is worthless if nobody answers. Look for personalized, short messages and a planned follow-up sequence.
- Data disciplineSourcers should track response, interest and pass-through rates by channel and message, and use the numbers to change approach.
- Partnership with recruiters and hiring managersThey run calibration, take feedback on profiles without getting defensive, and keep the ATS clean so handoffs work.
- Ethics and fairnessSourcing touches privacy rules, diversity goals and candidate trust. Candidates should know where the lines are.
Opening and experience questions
Describe the roles you sourced for in your last job: types, seniority, locations, and how many at once.
- Why ask it
- Establishes the scope and difficulty of their work.
- A strong answer
- Specific mix and volume, such as 12 open roles across customer support, sales and two backend engineers, US-wide, with notes on which were hardest and why.
- Red flags
- Vague ("all kinds of roles") or cannot name a single difficult search.
What were you measured on, and how did you do against it?
- Why ask it
- Shows whether they understand sourcing as a funnel with outcomes.
- A strong answer
- Names metrics such as interested candidates per week, submittal-to-interview rate and hires from sourced candidates, with actual numbers and a period.
- Red flags
- Only counts messages sent or profiles viewed.
Walk me through what you do in the first 48 hours after a new requisition opens.
- Why ask it
- Tests process and how they start a search.
- A strong answer
- Reads the req, joins or runs the intake, checks the ATS for past applicants and silver medalists, builds a target company and title list, runs test searches, sends a calibration batch of profiles to the hiring manager before full outreach.
- Red flags
- Starts mass messaging immediately without calibration.
How do you decide where to look for a particular role?
- Why ask it
- Channel judgment is central to the job.
- A strong answer
- Matches channels to the audience: professional networks for corporate roles, GitHub or technical communities for engineers, résumé databases and local job boards for hourly roles, associations for nurses or accountants, plus the company's own ATS first.
- Red flags
- Uses one platform for every role.
Why sourcing rather than full-cycle recruiting?
- Why ask it
- Checks motivation and career expectations.
- A strong answer
- Enjoys the research and first conversation, likes measurable output, and is honest about whether they want to move into full-cycle work later.
- Red flags
- Sees sourcing only as a step they want to leave as soon as possible, with no interest in the craft.
Search and research skills
Write a Boolean string out loud for a payroll specialist with multi-state experience in Texas or Arizona.
- Why ask it
- A practical test of search syntax and thinking.
- A strong answer
- Uses OR groups for title variants ("payroll specialist" OR "payroll administrator" OR "payroll analyst"), AND for skills (multi-state OR "multi state"), location handling, and mentions excluding managers or vendors with NOT if needed. Explains why each part is there.
- Red flags
- Cannot construct a valid string or uses AND for everything.
Your search returns 4,000 profiles and most look wrong. What do you do?
- Why ask it
- Refining searches is where skill shows.
- A strong answer
- Reviews 20 to 30 results to see why they are wrong, then adjusts: tighter titles, required skills in specific fields, excluding irrelevant industries, adding company targets. Re-checks a sample after each change.
- Red flags
- Just adds more keywords or gives up and scrolls.
Your search returns 12 people. Now what?
- Why ask it
- Tests ability to widen a search sensibly.
- A strong answer
- Questions which requirements are truly required, adds adjacent titles and industries, looks at transferable skills, expands location or remote, checks other channels, and goes back to the hiring manager with data.
- Red flags
- Messages all 12 and reports the role as impossible.
What is X-ray searching and when would you use it?
- Why ask it
- Checks knowledge of a standard technique. See our X-ray search definition.
- A strong answer
- Uses a search engine's site: operator to search within a site's public pages, useful when the platform's own search is limited or paid, for example finding public profiles, portfolios or conference speaker lists.
- Red flags
- Has never heard of it or confuses it with Boolean only.
How do you build a target company list for a hard-to-fill role?
- Why ask it
- Shows research depth beyond keyword search.
- A strong answer
- Starts with the hiring manager's best people and where they came from, competitors, companies with similar products or customers, companies with recent layoffs or reorganizations, and adjacent industries. Updates the list as calibration feedback comes in.
- Red flags
- Only lists the two or three biggest competitors.
How do you find contact details for someone who is not active on professional networks?
- Why ask it
- Tests resourcefulness within ethical limits.
- A strong answer
- Uses contact enrichment tools, company email patterns, public portfolios, professional associations, and mutual connections or referrals, and respects opt-outs and privacy rules.
- Red flags
- Suggests scraping private data or misleading people to get a number.
How do you use the ATS before you go outside?
- Why ask it
- Rediscovery is usually the cheapest source and is often skipped.
- A strong answer
- Searches past applicants, silver medalists and referrals for similar roles, checks why they were not hired, and contacts promising ones first with a message that references the earlier process.
- Red flags
- Never searches internal data.
How would your approach differ for 50 warehouse associates versus one senior data engineer?
- Why ask it
- Separates volume sourcing from precision sourcing.
- A strong answer
- Volume: job board résumé databases, text outreach, community and local channels, quick screening questions, speed and scale. Senior engineer: precise target list, deep profile review, highly personalized messages, longer follow-up and close hiring manager involvement.
- Red flags
- Same playbook for both.
Outreach and engagement
Read me the first outreach message you'd send for this role.
- Why ask it
- Outreach quality decides results.
- A strong answer
- Short, specific to the person (why them), clear about the role and one or two concrete selling points such as pay range, team or problem, and an easy ask like a 15-minute call. No wall of text.
- Red flags
- Generic template with "exciting opportunity" and no reason for contacting this person.
What response rates do you typically get, and what changed them most?
- Why ask it
- Shows whether they test and learn.
- A strong answer
- Gives realistic numbers by channel and role type, and names experiments that moved them, such as shorter subject lines, including pay, sending at different times, or personalizing the first line.
- Red flags
- No idea of their response rate, or claims rates that sound implausible without explanation.
How do you follow up when someone doesn't reply?
- Why ask it
- Most replies come after the first message.
- A strong answer
- A planned sequence of two or three follow-ups over about two weeks, each adding something new, across channels where appropriate, then stopping.
- Red flags
- Never follows up, or sends the same message eight times.
A candidate replies, "Not interested right now." What do you do?
- Why ask it
- Tests long-term relationship thinking.
- A strong answer
- Thanks them, asks what would make a move interesting in future, asks for referrals, tags them in the CRM with notes and a reminder to check in.
- Red flags
- Ignores the reply or keeps pushing.
How do you sell a role that has an obvious weakness, such as below-market pay or a long commute?
- Why ask it
- Honesty and persuasion together.
- A strong answer
- Leads with real strengths, targets people for whom the weakness matters less, and is transparent about the issue early rather than hiding it until the offer.
- Red flags
- Hides or misrepresents the weakness.
When would you use text or phone instead of email or InMail?
- Why ask it
- Channel choice affects reply rates, especially for hourly roles.
- A strong answer
- Text for hourly and frontline candidates who applied or opted in, phone for warm referrals or senior candidates who prefer it, and awareness of consent rules for texting.
- Red flags
- Texts cold lists without consent.
Behavioral questions
Tell me about the hardest search you've worked on. What made it hard and what did you do?
- Why ask it
- Shows persistence and problem solving.
- A strong answer
- Specific role, specific obstacles (tiny talent pool, low pay, unclear requirements), concrete changes in approach and the outcome, including what they would do differently.
- Red flags
- Blames the hiring manager entirely or has no clear outcome.
Tell me about a time a hiring manager rejected most of the profiles you sent.
- Why ask it
- Calibration conflict is common.
- A strong answer
- Asked why each was rejected, found the unstated requirement, adjusted the search, and set up a quicker calibration loop for next time.
- Red flags
- Got defensive or kept sending the same type of profile.
Describe a time you changed your approach based on data.
- Why ask it
- Tests analytical habits.
- A strong answer
- Noticed a pattern, such as one channel producing replies but no interviews, and moved effort elsewhere, with numbers before and after.
- Red flags
- Cannot name a single metric they track.
Tell me about a time you had too many open roles at once. How did you prioritize?
- Why ask it
- Sourcers juggle competing recruiter demands.
- A strong answer
- Prioritized by business impact, time open and pipeline health, agreed priorities with recruiters or their manager, and was transparent about what would slip.
- Red flags
- Worked whatever was loudest.
Give an example of how you helped build a more diverse pipeline for a role.
- Why ask it
- Diverse sourcing is often a sourcer's responsibility and must be done lawfully.
- A strong answer
- Widened channels (associations, community groups, schools), removed unnecessary requirements, reviewed job language, and tracked pipeline composition at an aggregate level without selecting individuals on protected characteristics.
- Red flags
- Describes filtering candidates by race or gender.
Situational questions
The hiring manager wants five years in a specific niche tool that has only existed for three. What do you do?
- Why ask it
- Tests ability to push back with tact.
- A strong answer
- Explains the issue with facts, proposes the real underlying skill, shows a few strong profiles without the exact requirement, and agrees revised criteria.
- Red flags
- Silently searches for an impossible profile.
A recruiter says your candidates are interested on paper but drop out after the first call. How do you investigate?
- Why ask it
- Shows ownership of downstream conversion.
- A strong answer
- Reviews call notes and drop-out reasons, checks whether outreach oversold the role, pay or location, and agrees with the recruiter on what to say upfront.
- Red flags
- Says it's the recruiter's problem.
You find a strong candidate who works for one of our clients. What do you do?
- Why ask it
- Agency and corporate teams often have no-poach agreements or client restrictions.
- A strong answer
- Checks the company's policy and any client agreements before contacting, and escalates if unsure.
- Red flags
- Contacts them without checking.
A candidate asks how you got their personal email address. How do you answer?
- Why ask it
- Tests honesty and awareness of privacy expectations.
- A strong answer
- Explains the source plainly, offers to remove their details and stops contact if asked, and knows that rules such as GDPR in Europe and some US state privacy laws give candidates rights over their data.
- Red flags
- Evades the question.
You're asked to find 200 interested candidates for a hiring event in three weeks. How do you plan it?
- Why ask it
- Tests volume sourcing and planning.
- A strong answer
- Works back from the funnel (expected reply, interest and show rates), uses ATS rediscovery, résumé databases, text campaigns to opted-in candidates, referrals and local channels, and tracks daily against target.
- Red flags
- No numbers or plan, just "post everywhere."
Questions for senior or lead sourcers
How would you set up a sourcing function for a team that has never had one?
- Why ask it
- Tests strategic and operational thinking.
- A strong answer
- Agrees which roles get sourcing support, defines intake and calibration steps, sets metrics, chooses tools, sets up CRM tagging and reporting, and starts with a pilot on a few roles.
- Red flags
- Only talks about buying tools.
How do you measure whether sourcing is worth the investment?
- Why ask it
- Leaders need to justify headcount.
- A strong answer
- Share of hires from sourced candidates, conversion rates compared with applicants, time to fill and quality of hire for sourced hires, and cost compared with agency fees.
- Red flags
- Only reports activity numbers.
How do you train a new sourcer?
- Why ask it
- Shows ability to teach the craft.
- A strong answer
- Shadowing, shared search strings and message libraries, reviewing their first calibration batches, weekly metric reviews and gradual move to harder roles.
- Red flags
- "They pick it up as they go."
Sample answers
First I'd stop and actually read about 25 of them, because the pattern tells me what's broken. Usually it's titles. Last year I searched for customer success managers and half the results were account executives who'd put "customer success" in their summary. So I moved the title terms into the title field only, added a NOT for sales-only titles, and added two must-have skills in the experience section. That got me to about 600. Then I added a target company list from the hiring manager's best hires and ran that as a separate search. I checked another sample of 20 after each change. If most of the sample looks right, I stop tuning and start reviewing properly.
I sent eight profiles for a senior HRIS role and the manager rejected six. Instead of guessing, I booked 15 minutes and went through each rejection. It turned out the real requirement was experience leading an implementation, not just supporting one, and the req didn't say that. Four of the six had only supported. I rewrote my search to look for implementation lead language and project scope, and I asked the manager for two profiles of people they'd love to hire. The next batch of six had four approved for interviews. Since then I always send a small calibration batch in the first week and ask for a reason with every rejection.
Interview scorecard
| Competency | Weight | Strong (4–5) | Weak (1–2) |
|---|---|---|---|
| Search craft | 25% | Builds and refines accurate searches across several channels; live exercise produces relevant profiles quickly. | Basic keyword searching; cannot explain or improve results. |
| Role understanding and calibration | 20% | Translates requirements into real signals and uses calibration feedback well. | Takes the job description literally; repeats rejected profile types. |
| Outreach and engagement | 20% | Personalized, concise messages with planned follow-up; knows their response rates. | Generic templates and no follow-up. |
| Data and pipeline management | 15% | Tracks funnel metrics by channel and acts on them; keeps ATS and CRM clean. | No metrics; poor record keeping. |
| Collaboration | 10% | Handles hiring manager pushback constructively and owns downstream conversion with recruiters. | Defensive or hands off. |
| Ethics and judgment | 10% | Respects privacy, consent and fair hiring rules, and is transparent with candidates. | Cuts corners on data or honesty. |
Score each competency from 1 to 5 straight after the interview, before discussing the candidate with anyone else, then multiply by the weight.
How to structure a sourcer interview
Start with a 20 to 30 minute phone screen covering role types, volume, metrics and pay expectations. The main interview is about 60 minutes with the TA manager or lead sourcer, using six to eight questions from the groups above. Include a recruiter the sourcer would support for 20 minutes, since that working relationship decides whether the hire succeeds.
The most useful step is a live search exercise. Give the candidate a real but closed requisition, 30 to 45 minutes and access to whatever tools they normally use (or a shared screen on a public platform). Ask for a search string, ten profiles they would contact with a one-line reason for each, and one outreach message. Then ask them to talk through what they would change after a hiring manager rejects three of the ten. You learn more in that hour than in any number of questions about Boolean syntax.
It helps to be clear about what a sourcer owns in your team before you interview. If the role also screens and manages candidates to offer, borrow from our recruiter interview questions; for engineering-heavy pipelines, add a few from the technical recruiter interview questions.
Mistakes interviewers make
The biggest mistake is testing tool familiarity instead of judgment. A candidate who knows every filter in one platform may still send hiring managers the wrong people. Ask why they chose each profile in the exercise and listen for reasoning about signals, not keywords.
The second is ignoring outreach. Sourcing teams often hire on search skills and then wonder why reply rates are poor. Always ask for a sample message, and ask what response rate they get and how they know.
Third, interviewers treat activity as output. A sourcer who sends 300 messages a week with a 3% interested rate is less useful than one who sends 80 with a 20% rate. Ask about conversion all the way to interview and hire.
Finally, test ethics. Sourcing involves personal data, cold contact and diversity goals. Candidates should know that filtering on protected characteristics is unlawful under Title VII and similar laws, that contact data must be handled under privacy rules that vary by state and country, and that they should stop contacting people who ask.
Hiring sourcers for high-volume and agency teams
In high-volume hiring, sourcing looks different. A sourcer supporting a contact center or distribution network is filling hiring classes of 20 to 60 people, mostly from résumé databases, job boards, past applicants and text campaigns to candidates who have opted in. Speed, list hygiene and follow-up matter more than finding one perfect profile. Ask how they would rediscover past applicants, how they would get from 500 names to 60 interviews, and how they track show rates.
Agency sourcers, covered more fully in our staffing recruiter interview questions, also need to manage candidate ownership and client restrictions, and often work several clients' roles in the same day. For both settings, ask how they use automation and AI-assisted search without losing the personal touch. Good answers describe automating the repetitive parts (search alerts, sequencing, enrichment, scheduling) while keeping profile review and first-line personalization human. The guide on using candidate sourcing software to build a strong talent pipeline is a useful background read for interviewers new to the role.
Frequently asked questions
What questions are asked in a sourcer interview?
Expect questions on how you start a new search, Boolean and X-ray techniques, choosing channels, refining searches that return too many or too few people, outreach messages and response rates, working with hiring managers on calibration, and the metrics you are measured on. Many teams add a live search exercise.
What should I ask a sourcing specialist candidate?
Ask them to build a search string live, critique their own results, write an outreach message, explain their response and conversion rates, and describe how they handled a hiring manager who rejected their profiles.
How do you test a talent sourcer's skills?
Use a 30 to 45 minute live exercise on a real, closed requisition: a search string, ten profiles with reasons, one outreach message, and a discussion of how they would adjust after feedback.
What is the difference between a sourcer and a recruiter?
A sourcer finds and engages candidates who have not applied and hands interested, qualified people to a recruiter. A recruiter manages the process from screening through offer. Some roles combine both.
What metrics should a recruitment sourcer know?
Response rate, interested rate, submittal-to-interview rate, interview-to-offer rate and hires from sourced candidates, ideally by channel and role type. Strong candidates also know time to first calibration and pipeline coverage.