A technical sourcer finds and engages candidates for engineering, data, and IT roles, then hands them to a recruiter to screen and close. The job stops before the intake meeting, the pay negotiation, and the offer. It starts with a search string and ends with a warm reply in someone's inbox.
Interviewers want to see how you find people with no resume posted anywhere. That takes Boolean strings that return the right 40 people instead of 4,000, X-ray searches that pull public profiles off sites with no internal search worth using, and outreach that gets a reply from an engineer who ignores 10 recruiter messages a week.
They also check your numbers. Response rate, sourced-to-submit ratio, and how many of your candidates a recruiter actually moves forward are all things a sourcing manager expects you to know cold.
Technical sourcer at a glance
| Item | Details |
|---|---|
| Closest BLS occupation | Human resources specialists (BLS groups sourcing under recruitment specialists) |
| Median pay | $75,940 for HR specialists overall (BLS, May 2025) |
| Job outlook | 6% growth from 2025–2035, about 73,700 openings a year (BLS) |
| Education | Bachelor's degree is typical (BLS); many sourcers move up from a recruiting coordinator role |
| Certifications | Optional: AIRS Certified Internet Recruiter (CIR), covers Boolean and X-ray search |
| Key tools | LinkedIn Recruiter, an ATS such as Greenhouse or Lever, GitHub search, a sourcing or enrichment platform such as SeekOut or hireEZ, an outreach tool such as Gem |
| Interview format | Sourcing screen, sourcing manager interview, a live or take-home Boolean and X-ray exercise |
How the interview usually works
Sourcing-only roles don't follow one fixed process across companies, so treat this as the common pattern at companies with a split sourcer and recruiter model.
- Recruiting coordinator or TA screen. About 30 minutes on the searches you've run, your tools, and your req load.
- Sourcing manager interview. Deeper on your channels, your metrics, and how you decide a search is exhausted.
- Recruiter or hiring manager conversation. Since you hand candidates to a recruiter, some teams have that recruiter interview you to see how you'd work together.
- Practical exercise. Build a Boolean string and an X-ray search for a real or sample req, write 2 outreach messages, or source live while someone watches your screen.
General and background questions
1. Why sourcing instead of full-cycle recruiting?
Why they ask: Sourcing-only roles lose people who miss screening, negotiating, and closing. They want someone who chose the top of the funnel on purpose.
How to answer: Say what you like about the search itself, and be honest about whether you see this as a step toward full-cycle recruiting or a specialty you want to stay in.
Sample answer: I like the puzzle part of the job more than the sales part. Building a search string that goes from 8,000 profiles down to the 30 people who actually fit, and then getting 3 of them to reply, is the piece I look forward to. I spent 8 months doing full-cycle recruiting at a small agency and the screening calls and offer negotiations drained me. Sourcing lets me spend my day where I'm strongest. I'd like to specialize further, maybe into a sourcing lead role that trains other sourcers.
2. What's your req load, and what tools do you use?
Why they ask: A sourcer covering 4 reqs for niche roles works differently than one covering 15 volume reqs. They're matching your experience to their team's setup.
How to answer: Name your req count, the role types, your main tools, and how many recruiters you support.
Sample answer: At Ferro Systems I sourced for 10 to 12 open reqs at a time, mostly backend, data engineering, and 2 or 3 security roles, supporting 3 recruiters. I used LinkedIn Recruiter and GitHub for search, SeekOut to pull emails and expand past LinkedIn's limits, and Gem to build and track outreach sequences. Everything I found went into Greenhouse so the recruiter could see it without me forwarding a list. I haven't sourced for hardware roles, so I'd expect a learning curve there.
3. Walk me through your sourcing metrics.
Why they ask: Sourcing produces clean numbers at every stage. A sourcer who can't quote a response rate or a sourced-to-submit ratio probably isn't tracking their own work.
How to answer: Give response rate, sourced-to-submit ratio, and submit-to-interview ratio, and explain what one number told you.
Sample answer: Over the last 12 months my cold outreach reply rate ran about 28%. Of the people who replied and qualified, I submitted 65% to the recruiter, and of those, 55% got a recruiter screen scheduled. That submit-to-screen number used to sit near 35%, so I started sitting in on 2 recruiter debriefs a month to hear exactly why a profile got passed over, and adjusted what I sent forward. It moved to 55% over about a quarter.
4. How do you decide a search is exhausted?
Why they ask: A sourcer who keeps working a dead search wastes weeks. They want a real stopping rule, not "I just know."
How to answer: Give the signals you track: reply rate decline, repeat profiles across channels, and when you escalate instead of continuing to search.
Sample answer: I track reply rate by week. If it's held steady for 3 weeks and then drops for 2 straight, I'm hitting the same pool of people from different angles. I also watch for repeat profiles: once LinkedIn, GitHub, and a conference speaker list start surfacing the same 15 names, the channel is exhausted, not the search. At that point I go to the recruiter with what I've tried and ask whether the requirements can flex, rather than quietly running the same searches again.
Role-specific questions
5. Write a Boolean search for a senior site reliability engineer with Kubernetes experience.
Why they ask: This is the core skill. They want to see operators, synonyms, and how you narrow or widen results.
How to answer: Cover title variants, skill synonyms, and exclusions, and explain your next move if the result count is off.
Sample answer: In LinkedIn Recruiter:
("site reliability engineer" OR SRE OR "platform engineer" OR "infrastructure engineer") AND (kubernetes OR k8s OR EKS OR GKE) AND (terraform OR ansible OR "infrastructure as code") AND (senior OR staff OR lead) NOT (recruiter OR intern). I include "k8s" because plenty of engineers abbreviate it in their headline but not their skills list. If I get over 2,000 results, I add a company list of 15 to 20 target employers running similar infrastructure. If I get under 30, I drop the seniority terms and read tenure and past titles myself instead of trusting the label.
6. What's an X-ray search, and when do you use one?
Why they ask: GitHub and Stack Overflow have no search tools built for recruiting. They want to see you work around that with a general search engine.
How to answer: Explain the technique, give an example string, and say which sites you X-ray most.
Sample answer: An X-ray search uses
site:and other operators in a search engine to pull public pages off a site that doesn't give recruiters good internal search. For GitHub I'd runsite:github.com "kubernetes-operator" location:berlinto find contributors to a specific type of project near a city. For Stack Overflow, which shut down its own recruiting tools years ago, I X-ray public profile and answer pages the same way:site:stackoverflow.com/users "kubernetes" "terraform". I use this most on GitHub and Stack Overflow, and less on LinkedIn since LinkedIn Recruiter's own search covers most of what I'd X-ray for.
7. How do you source on GitHub?
Why they ask: GitHub shows work instead of a resume. They want to know whether you can read that work and find the right people from it.
How to answer: Describe your search approach and how you judge a profile beyond star counts.
Sample answer: I start from the repositories, not the people. For a Rust backend req, I'd search for active repos using specific Rust web frameworks, then look at who's committing code, not just who starred the repo. I read a handful of recent commits and pull request comments to see whether someone writes clear reasoning, not just working code. GitHub profiles rarely list an email, so I use an enrichment tool to find a work email, and I only reach out once I can reference something specific: a commit, an issue they closed, or a design decision in a PR thread.
8. How do you write an outreach sequence, and what's your reply rate?
Why they ask: A sourcer's list is worthless if nobody replies. They want structure, personalization, and a number.
How to answer: Describe your sequence length, timing, and personalization, and give a real reply rate.
Sample answer: My sequence is 3 messages over 10 days. The first names something specific to that person, states the role in one line, and asks for 15 minutes with no pressure. If there's no reply after 4 days, the second message adds one new detail, like a recent product launch tied to the role. The third, at day 10, is 2 sentences and closes the loop either way. My reply rate across the last 6 months is 26%, and messages with a specific reference to the person's work reply at almost double the rate of ones that don't.
9. How do you build a diverse candidate pipeline?
Why they ask: Sourcing only on LinkedIn tends to return the same networks every time. They want specific channels, not a general statement about caring.
How to answer: Name channels beyond your default ones and how you check whether your pipeline is actually broader.
Sample answer: I pull speaker and organizer lists from groups like Women Who Code, /dev/color, and Out in Tech events relevant to the role, and I search GitHub for contributors to projects run by those communities. I also widen my company target list past the usual 10 names, since sourcing only from the same well-known employers narrows things by default. Every month I check my own submitted-candidate list against my sourced list to see whether one channel is doing all the work, and if it is, I go find a second one.
10. How do you use AI or automated matching tools in sourcing?
Why they ask: Sourcing platforms increasingly rank or auto-suggest candidates. They want to know where you trust the tool and where you don't.
How to answer: Say what you use automation for, and where you still read every profile yourself.
Sample answer: I use my sourcing platform's match score to sort a long list so I look at the most likely fits first, and I use AI to draft the first pass of an outreach message, which I then rewrite so it doesn't read like a template. I don't let a tool decide who gets contacted. Match scores miss context, like a candidate who switched from data engineering to backend last year and now reads as a weak keyword match despite being exactly right. I read every profile before sending anything.
11. How do you keep a pipeline warm for a role that might reopen in 3 months?
Why they ask: Some searches pause instead of closing. They want to see whether you track people or start from zero every time.
How to answer: Describe how you log and follow up with strong candidates who aren't hired now.
Sample answer: Anyone who replied and seemed strong goes into a talent pool in our ATS, tagged by skill and level, with a note on where they stood and why the search paused. I set a reminder for 10 to 12 weeks out and send a short personal check-in, not a form email, referencing what we talked about last time. When our data platform team reopened a senior req 4 months after a hiring freeze, 2 of the 5 people I re-contacted were still interested, and one became the hire.
12. How do you hand a candidate off to a recruiter?
Why they ask: A sourcer who dumps names in a spreadsheet slows the recruiter down. They want to see a clean handoff.
How to answer: Describe what information you pass along and how you keep the recruiter from re-asking the candidate things they already told you.
Sample answer: Every submission includes a short note: why I think they fit, what they said about their interest and timeline, and anything sensitive like a competing process or a notice period. I never leave a recruiter to ask "so why are you looking?" cold when the candidate already told me. In Greenhouse I tag the submission with the source channel too, since that's what our sourcing manager pulls for channel-level metrics.
Behavioral questions
13. Tell me about a search where your usual channels didn't work.
Why they ask: Every sourcer hits a search where LinkedIn and GitHub both come up thin. They want to see how you adapt.
How to answer: Name the role, what failed, and the channel that worked instead.
Sample answer: A search for a firmware engineer with automotive experience returned almost nothing on LinkedIn or GitHub, since that work often isn't public. I pulled the exhibitor and speaker list from an embedded systems conference, then searched patent filings for the specific sensor technology our team used, since patent applications list inventor names and employers. That list produced 6 qualified conversations and the eventual hire, who I found listed as a co-inventor on a patent from 2 years earlier.
14. Tell me about a time your sourced candidates weren't converting with the recruiter.
Why they ask: A gap between sourcing and screening wastes both people's time. They want to see you find the mismatch instead of just sending more names.
How to answer: Describe how you found the disconnect and what changed.
Sample answer: A recruiter was passing on almost everyone I sent for a data platform req, and I'd started to assume she was being too picky. I asked to sit in on 3 of her screens instead. She was probing for hands-on pipeline ownership, not just tool names on a resume, and my searches were matching on tool keywords alone. I rebuilt my screening questions in my outreach to ask directly what someone owned versus supported, which cut a few weak profiles before they ever reached her, and my submit-to-screen rate went from about 30% to 55% over the next 6 weeks.
15. Tell me about learning a technical domain you didn't know well.
Why they ask: Sourcers get pulled onto job families they've never searched before. They want to see how fast you get useful.
How to answer: Name the domain, what you did to learn it, and how you knew you'd learned enough.
Sample answer: I'd never sourced for hardware roles before 3 FPGA engineer reqs opened at once. I asked the hiring manager for 30 minutes to explain what the team built and what makes one FPGA engineer stronger than another. I wrote a one-page glossary of terms like Verilog and timing closure, and had one of the team's engineers review my first Boolean strings before I ran them. By my second week I was sourcing without help, and the team ended up interviewing 5 of my first 12 submissions.
Situational questions
16. LinkedIn returns almost nothing for a niche req. What do you do next?
Why they ask: LinkedIn is most sourcers' default. They want to see your next 3 moves, not just "I'd keep trying LinkedIn."
How to answer: Name specific alternate channels in order and why you'd try them in that sequence.
Sample answer: First I'd X-ray GitHub and Stack Overflow for the specific technology instead of relying on LinkedIn's own search. Next I'd look for niche Slack or Discord communities and conference speaker lists tied to that specialty, since specialists often skip building out a LinkedIn profile. If that still comes up short, I'd ask our own engineers who they'd recommend, since a referral from someone in the field beats a cold search for rare skill sets. I'd tell the hiring manager within the first week if none of that is working, rather than quietly grinding on LinkedIn alone.
17. A hiring manager only wants candidates from 5 well-known companies. How do you respond?
Why they ask: Narrow company lists shrink the pool and often reflect bias more than a real requirement. They want to see you push back with reasoning, not just comply.
How to answer: Ask what specifically those companies represent to the manager, then offer a broader list that meets the same bar.
Sample answer: I'd ask what those 5 companies have in common in the manager's mind, whether it's scale, a specific technology, or how the teams there operate. Usually it's one of those things, not the logo itself. I'd bring a list of 15 to 20 companies that share that trait, including some the manager hasn't heard of, along with 2 or 3 sourced profiles from outside the original 5 to make the case concrete. If the manager still insists on only those 5 after that conversation, I'd flag to my sourcing manager that the search is likely to run long.
18. You have 8 open reqs and 2 just got marked urgent. How do you reprioritize?
Why they ask: Req loads shift fast. They want to see you set priorities out loud instead of just working faster on everything.
How to answer: Explain your ranking method and who you tell about the change.
Sample answer: I'd rank all 8 by business urgency and how exhausted each search already is. The 2 new urgent reqs get my first 2 hours each morning until I've built a strong initial list, since a cold start is where sourcing takes longest. Reqs with an active pipeline that just needs following up stay on a lighter daily touch instead of new searching. I'd message the recruiters on my lower-priority reqs the same day so nobody's waiting without knowing why, and ask my sourcing manager whether one req can move to a teammate for 2 weeks.
Questions to ask the interviewer
- How many reqs does each sourcer carry, and how is that split between sourcer and recruiter?
- Which sourcing and enrichment tools does the team use, and who owns the budget for new ones?
- How do sourcers and recruiters divide the handoff, and what does a strong submission look like here?
- How is a sourcer's performance measured: submissions, reply rate, or hires?
- What's the hardest search open right now, and what's already been tried?
- Is there a path from this role into full-cycle recruiting or a sourcing lead role?
How to prepare
- Know your numbers. Reply rate, sourced-to-submit ratio, and submit-to-screen ratio for the last 6 to 12 months.
- Build a sourcing sample. Pick a real open engineering role at the company, write a Boolean string and an X-ray search, and draft a 3-message outreach sequence.
- Read the company's engineering blog and job posts. Note the stack and team structure so your example searches sound specific.
- Prepare 4 stories. A search where your usual channels failed, a mismatch with a recruiter you fixed, a domain you learned fast, and a pipeline you kept warm.
- Review basic engineering concepts. Know roughly what separates backend, infrastructure, and data roles so your questions sound informed.
- Consider a certification. The AIRS CIR program covers Boolean and X-ray sourcing directly and stays valid for 2 years.
If you're also open to full-cycle roles, compare this with technical recruiter interview questions. For related HR paths, see the HR generalist cover letter guide and these employee relations specialist interview questions. To see what the technical side of a search covers, read our security engineer interview questions.
by