A candidate answers a sourcer’s message, agrees to a call, and two weeks later a recruiter opens the first screen by asking why they’re thinking of leaving. The candidate already told the sourcer, but the recruiter never saw it written down. When the same candidate drops out after the hiring manager interview, the sourcer never hears why.
That gap is where the sourcing versus recruiting question gets settled in most teams. Sourcing finds people who could do a role and gets them talking. Recruiting carries them from the first screen to a signed offer, and teams lose candidates at the point where one job hands over to the other.
I’d draw the line between the two jobs at the first recruiter screen, and give the handoff at the screen an owner. The sourcer passes forward why each person was approached and what they said. The recruiter sends back where each one stopped and why. Most of what makes the split succeed happens in those two handoffs.
Sourcing versus recruiting: where one job ends and the next begins.
Each job answers its own question. Sourcing asks who could do this role and whether they’ll talk to you, and recruiting asks whether this person should get the offer and whether they’ll take it:
| Sourcing | Recruiting | |
|---|---|---|
| The question it answers | Who could do this role, and will they talk to you? | Should this person get the offer, and will they accept it? |
| Where it sits | Before the first recruiter screen | From the first screen to a signed offer |
| The daily work | Searching and writing first messages, then following up and checking early profiles with the hiring manager | Running screens and debriefs, then the offer conversation and the close |
| The skill it leans on | Reading a talent market and writing a message a stranger answers | Running a process for several people at once and negotiating an offer |
| What it’s measured on | Replies, and how many sourced candidates the hiring manager agrees to meet | How fast candidates move from first screen to offer, and how many accept |
| Who usually owns it | A dedicated sourcer, or a full-cycle recruiter between screens | The recruiter, working with the hiring manager |
I put the line at the first recruiter screen because it’s the first conversation where someone assesses the candidate against the role. Before that call the work is persuading a stranger to talk. From that call on, the team is deciding about a candidate and then trying to close them, so the skills and the measures change at the same point.
Both jobs sit on the same recruitment funnel, which is why a weak stage on one side so often gets blamed on the other. A recruiter with an empty week of screens blames the sourcer, and a sourcer whose candidates stall in the final round blames the interviews.
For the sourcing half on its own, start with the sourcing strategies teams use to build pipelines they can repeat.
Who owns each side as the team grows.
Most teams start with one person doing both jobs, so the first decision is when to split them.
A full-cycle recruiter sources in whatever time the screens and debriefs leave. That works while most roles are ones people apply for. Sourcing slips first when the calendar fills, because a screen with a candidate waiting usually wins over a search with no deadline, and the pipeline for next month thins out without anyone deciding it should.
If one person holds both jobs for now, the harder part of full-cycle recruiting is keeping the context of a role in one head. Some of the signs that sourcing is slipping call for a sourcer, and some call for something cheaper:
| What you see | What I’d do |
|---|---|
| Recruiters keep pushing their searches to the end of the week | Give one person the searches for the hardest roles, and keep everyone else full-cycle |
| Few people apply for the roles you’re hiring, such as senior or specialist ones | Add a dedicated sourcer for those roles, because waiting for applicants will not fill them |
| Most of the first profiles come back rejected by the hiring manager | Fix the brief before adding anyone, since a sourcer working from a vague brief finds more of the wrong people |
| One team’s hiring push will end in a quarter or two | Bring in contract or agency sourcing for the push instead of a permanent seat |
A dedicated sourcer’s week is mostly active sourcing: outbound search and first messages to people who never applied. Chris Adams, Uber’s first sourcer, talks through how that seat is changing in his 10x Recruiting episode.
Once the role is split, write down who owns the first conversation. I’d give the sourcer the reply and any short call about the candidate’s interest and timing, and give the recruiter everything from the screen onward. Leave it undecided, and the candidate ends up with two first calls.
Hand each candidate over with the reason they were approached.
The first of the two handoffs runs from sourcing to recruiting, and it decides how the candidate’s first screen opens. Write the note when the candidate agrees to a screen, while the sourcer still remembers the thread, and keep it to what a recruiter can take in during the minute before the call:
- What on their profile made you reach out, and how it ties to the role.
- What they said in reply, in their own words where you have them.
- What would make them move, and what would keep them where they are.
- Anything that worries you, such as a long notice period or a gap between their pay and the role’s range.
The recruiter’s screen then starts from that note. Ask the candidate nothing twice, because a candidate who repeats their story to a second person learns that the team doesn’t share what it hears.
Put the note where the recruiter already looks, on the candidate’s profile in the team’s applicant tracking system (ATS), so it survives the sourcer’s vacation. The brief the sourcer searched from belongs on the role’s record too, and it is only as sharp as the intake call behind it. The handoffs after the screen, to the hiring manager and on to the offer, are where mapping the candidate journey takes over.
Send the reasons back to sourcing every week.
The second handoff runs the other way, from recruiting back to sourcing. Most teams skip it, and without it each search starts from the same brief as the last.
When a sourced candidate leaves the process, the sourcer should hear at which stage and why, in the words the interviewers or the candidate used. Without that, a sourcer learns months later that the final round kept turning down a certain kind of profile, and has kept finding more of them in the meantime.
I’d run it as a weekly 20-minute review. The recruiter brings every sourced candidate who left the process that week, with the stage and the reason taken from the scorecards or the debrief, and the sourcer brings the searches they’re about to run. Put any reason that changes a search into the brief the same day. Over a few months, those edits turn into a talent sourcing strategy written from what your own interviews said.
Keep the candidate’s own reasons in the review as well. A candidate who withdrew over pay tells the sourcer something different from one the panel turned down, and the fix for each sits in a different place. One who stepped back only for timing belongs in your hiring pool for the next opening.
Some reasons trace back to something the hiring manager never said at the intake call. Take those to the hiring manager directly, as part of the recruiter and hiring manager alignment you already work on.
Measure each job on its own side of the line.
Each job needs numbers it can move by itself, plus one number that shows whether the handoff works. This is the set I’d track:
| The number | Who owns it | What it tells you |
|---|---|---|
| Replies to first messages | Sourcing | Whether the targeting and the message reach the right people |
| Sourced candidates the hiring manager agrees to meet | Sourcing | Whether the search and the hiring manager want the same person |
| Sourced candidates who pass the first recruiter screen | Both | Whether the handoff carries the right people, with what the recruiter needs to know |
| Time from first screen to offer | Recruiting | Whether feedback arrives and the debriefs happen on time |
| Offers accepted | Recruiting | Whether the close works |
I’d keep message volume off the page. A count of messages sent shows how busy the sourcer was, and a team measured on volume sends more messages to the same wrong people.
Where Metaview fits in sourcing and recruiting.
Both handoffs depend on what people said: the candidate’s reply to the sourcer at one end, and the interviewers’ reasons at the other. AI Sourcing works on the sourcing side of that line, and the Notetaker and Reports work on the recruiting side.
AI Sourcing starts the sourcing side from one prompt in plain language. From that prompt the agent looks across the web, the ATS you’ve connected and the conversations your team has already had in Metaview, then hands back candidates, each with the reasoning behind it. That reasoning can give the sourcer the note’s first line, the part about why this person, once they have checked it against the brief. Everything else in the note comes from the candidate’s reply, and the outreach and every judgment about fit stay with your team.
Inside a candidate search, AI Filters set criteria the sourcing agent applies to the candidates the manual filters have already narrowed, and the sourcer chooses which ones to apply. The illustration below lists the filters for one search.
- 1Six filters for the search, from “Seniority” down to “Avg tenure,” each one ticked.
- 2The “Apply filters” button, which the sourcer presses once the list looks right.
Whatever the filters leave, the sourcer still reads each result and its reasoning before a first message goes out.
On the recruiting side, if the candidate and the interviewer both consent, the Metaview Notetaker joins the screen as a visible participant and records and transcribes the conversation, which it then turns into structured notes. Candidates can decline, and your team sets how they’re asked.
With the Notetaker on a screen or an interview, Metaview captures every spoken word, so the reason a candidate gave for stepping back is on the record when the recruiter brings it to the weekly review, and the sourcer reads it in the candidate’s own words.
In Reports, your team can ask about its own interview data from inside Metaview, or from an outside AI client such as Claude that you connect to it. A report over submitted scorecards can split the interviewers’ recommendations by department, as in this illustration:
- 1The report’s scope: submitted scorecards, grouped by department.
- 2The date range the report covers, set here to “All time.”
The recruiter closes on what the candidate told the sourcer they wanted, so the close starts at the first conversation. I’d want that conversation on the record while it is still in the candidate’s own words.
Good interviewers know that failing to close an excellent candidate is a silent company killer.”
Follow one sourced candidate across the line.
Here is the whole method on one person, as an example. A sourcer finds a backend engineer whose profile shows payments work at a company on the hiring manager’s list. She replies that she likes the product and wants a remote role.
The handoff note carries both lines, so the recruiter opens the screen on the remote question instead of asking why she’s looking. She clears the recruiter screen and meets the hiring manager, then the panel turns her down after the final round because she has never been on call for a live system.
At the weekly review the recruiter brings that reason in the panel’s words. The sourcer adds on-call experience to the brief that afternoon and checks the next batch of profiles for it before writing to anyone.
Every sourced candidate should cross the line like that, with a note going forward and a reason coming back. When both travel every week, each side keeps its own owner, and each search starts better informed than the one before it.
Run sourcing and recruiting as one handoff.
Bring one open role to the demo, and see a sourcing agent return candidates with the reasoning for each before anyone writes a handoff note.
Frequently asked.
Is a sourcer the same as a recruiting coordinator?
They’re different jobs. A coordinator schedules interviews and keeps candidates informed about the logistics of each stage. A sourcer finds candidates and gets them to a first conversation. In a small team one person may do both, but the skills differ, so I’d hire for them separately once you can.
Should a sourcer run the first screening call?
Only if your team has agreed the sourcer owns that call and given them a scorecard for it. Otherwise I’d keep the sourcer’s call to interest and timing, and leave the assessment against the role to the recruiter, so the candidate is judged once by the person who will run their process.
Who gets credit when a sourced candidate is hired?
Both of them. I’d count the hire in the sourcer’s numbers and in the recruiter’s, and use the first-screen pass rate of sourced candidates to see how well they work together. Splitting the credit tends to start arguments about who found a candidate first.
Can an agency do the sourcing side for an in-house team?
Yes, for a hiring push with an end date or a market your team rarely hires in. Give the agency the same brief and ask for a handoff note with every candidate. Then bring them into the weekly review of why candidates left, or they will keep sending the profiles your panel already turned down.
What does a sourcer do once AI tools find the names?
They check each result against what the hiring manager said, and they write first messages people answer. The handoff note and the weekly review stay with people too, because both depend on what candidates and interviewers said.
