Sourcer Interview Questions: 30 Questions and What to Listen For

Build a Boolean string live for one of our open roles and explain each part as you go.

Listen for: Correct operators and brackets, title synonyms, skill groups joined by OR, exclusions with NOT, and quoting phrases. Strong sourcers check the first results, then tighten or widen the string and explain why.

Why ask: The single best predictor of sourcing skill you can observe.

Notes:

Your search returns 40,000 profiles. What do you do next?

Listen for: Narrow with must have skills, location, seniority signals and exclusions, test which terms add noise, and split the search into smaller targeted strings. They aim for a list they can actually review, not a bigger number.

Notes:

Your search returns 12 profiles. What do you do next?

Listen for: Widen with title and skill synonyms, adjacent industries, nearby locations or remote options, drop nice to haves, and try other platforms. They also question whether the spec itself needs a conversation with the recruiter.

Notes:

Write an X ray search to find resumes or portfolios for this role on the open web.

Listen for: Search engine operators such as site:, intitle:, inurl: and filetype:, combined with role keywords and location, with exclusions for job ads. They know which sites suit the profile and that operator support varies by search engine.

Notes:

How do you find candidates whose job titles do not match the role at all?

Listen for: Searching by skills, tools, projects or outcomes rather than titles, mapping company specific title conventions, and looking at who does the work at target companies. They give a concrete example of a hire found this way.

Notes:

How do you keep your search strings and methods organized so you can reuse them?

Listen for: A library of saved strings by role family, notes on what worked, version tweaks, and sharing with the team. It shows they build systems instead of starting from scratch on every req.

Notes:

How would you build a talent map of competitors for a hard to fill role?

Listen for: Listing target companies with the right teams, finding team structure and size from public sources, identifying people by level, noting signals like layoffs or reorganizations, and keeping it in a shareable sheet or ATS project.

Notes:

How do you find the right person at a company when their profile is hidden or out of date?

Listen for: Company pages, conference talks, patents, publications, team photos, press releases and community sites, then confirming identity before contacting. They stay within public information and respect privacy.

Notes:

How do you estimate how many qualified people exist for a role in a given market?

Listen for: Using platform search counts as a rough guide, filtering by must haves, sampling profiles to see what share truly fit, and adjusting for people unlikely to move. They present a range, not a precise number.

Notes:

A hiring manager asks you which companies we should target. How do you build the answer?

Listen for: Companies with similar products, tech or customers, those with recent layoffs or slow growth, where past hires came from, and pay and culture fit. They back the list with reasons and agree it with the manager.

Notes:

How do you research a candidate before reaching out without crossing privacy lines?

Listen for: Using public professional information only, focusing on work, talks or projects relevant to the role, and avoiding personal details such as family, health or social posts unrelated to work. They mention data protection rules where relevant.

Notes:

Write a first message to a passive candidate for this role in under 80 words.

Listen for: A specific opening tied to the person's work, one or two concrete reasons the role fits, pay range or key detail if allowed, and a low effort question as the call to action. No generic praise or long company story.

Notes:

What reply rate do you get on cold outreach, and how have you improved it?

Listen for: They know their numbers and how they measure them, then name tests they ran on subject lines, message length, timing, channels or personalization. Improvement comes from testing, not guessing.

Notes:

How do you plan a follow up sequence, and when do you stop?

Listen for: Two to four touches spaced over a couple of weeks, each adding a new detail or channel, and a respectful final note. They stop on a no and record the reason for future contact.

Notes:

How do you use email, phone and LinkedIn differently in outreach?

Listen for: A reason for each channel: LinkedIn for first contact and credibility, email for detail, phone for warm follow ups or senior roles. They respect opt outs and know rules on cold email and calls in their market.

Notes:

A candidate replies 'not interested'. What do you do?

Listen for: Thank them, ask a light question about what would interest them in future or if they know someone suited, note the reason and timing in the ATS, and set a reminder if they invited later contact.

Notes:

How do you use AI to personalize outreach at volume without it sounding generic?

Listen for: AI for research summaries and first drafts, with human edits for accuracy and tone, real details from the person's work, and checks for errors. They review every message and avoid sending anything they have not read.

Notes:

Which sourcing metrics do you track for yourself?

Listen for: Profiles contacted, reply rate, interested rate, candidates passed to recruiters, pass through to interview and hires from sourced candidates. They know which ratio tells them their search quality versus their messaging.

Notes:

Of the candidates you passed to recruiters last quarter, how many got interviews, and why did the rest drop?

Listen for: Real numbers or honest ranges, plus reasons such as pay mismatch, location, manager feedback or candidates going cold. They used that feedback to change their search or screen.

Notes:

How do you record sourced candidates in the ATS or CRM so others can use them later?

Listen for: Consistent tags for skills and role family, source, outreach status, last contact date, notes on interest and pay, and correct consent records. Others on the team should be able to search and reuse their work.

Notes:

How do you check that contact data is accurate before you send outreach?

Listen for: Verifying email addresses before sending, using more than one source, checking that the person is still at the company, and watching bounce rates. They know bad data hurts sender reputation and response.

Notes:

How do you rediscover candidates already sitting in the database?

Listen for: Searching past applicants, silver medalists and old projects by skills and stage reached, checking notes on why they were not hired, and sending a personal message that references the past conversation.

Notes:

What do you need from a recruiter at the start of a search?

Listen for: The intake notes, must haves, target companies, pay range, interview steps, examples of good and bad profiles and feedback timing. They ask to sit in on intake when possible.

Notes:

How do you hand a candidate over to a recruiter so nothing is lost?

Listen for: A short written summary covering background, interest level, motivation, pay expectations, timing and anything promised, logged in the ATS, plus a warm introduction to the candidate so the next contact is expected.

Notes:

How do you calibrate with a hiring manager in the first week of a search?

Listen for: Sending a small set of varied profiles, asking for a yes or no and a reason on each, then adjusting the search. Fast feedback loops early save weeks later.

Notes:

A recruiter keeps rejecting candidates you think are strong. How do you handle it?

Listen for: Asking for specific reasons, checking them against the agreed spec, reviewing together, and escalating to the hiring manager with evidence only if the gap persists. They focus on the outcome, not on being right.

Notes:

How do you manage sourcing for several recruiters and roles at once?

Listen for: Clear priorities agreed with recruiters or their lead, time blocks per role, weekly delivery targets, and transparency when a role needs more time. They avoid quietly dropping lower priority searches.

Notes:

How do you build diverse slates without breaking the law?

Listen for: Widening where they search, such as different schools, communities, groups and companies, and removing biased requirements. They do not filter or select by protected traits, and they know the rules differ by country.

Notes:

What privacy rules affect how you store and contact sourced candidates?

Listen for: Awareness of data protection laws such as GDPR in Europe and state privacy laws in the US, telling candidates where data came from when required, honoring removal requests and keeping only needed data.

Notes:

Tell me about a hard search you cracked. What was the breakthrough?

Listen for: A specific role, what they tried that failed, the insight that changed it, such as a new title, community or adjacent industry, and the result. Shows curiosity and persistence with evidence.

Notes: