How to Use Claude for AI Candidate Sourcing (2026 Guide)
AI candidate sourcing with Claude means a people database finds candidates and Claude ranks them against your rules.
Published
Written by
Chris Pisarski
Reviewed by
Manmohit Grewal
Read time
12
minutes

AI candidate sourcing with Claude means a people database finds candidates and Claude ranks them against your rules.
The database filters on location, years, title, employer and off-limits companies. Claude reads each work history and judges what no field holds, such as a career spent mostly at big companies, with a one-line reason per person. Firm and client rules live in files Claude reads at every session start, so you set them once.
Recruiters keep asking our team for exactly that, like this independent talent advisor in October: "is there a way for me to, like, just, like, to insert the rule, the hard rules that will carry across all searches at once so that it's already there?"
In our test on a senior payments role in New York, filters cut the pool to 333, and Claude gave 11 of the first 25 a 1 for careers spent at very large companies, which no filter could judge.
At a glance | |
|---|---|
What you need | Claude Code, a people database over MCP (this guide uses Crustdata), one open role |
Where rules live | Three CLAUDE.md files: firm, client, role |
What Claude judges | Career path and experience no title shows, with a reason |
How a search goes | Batches of 25, scored before the next pull, up to three rounds |
Cost | 0.03 credits per search result plus premium fields (pricing docs), at $0.30 to $0.01 per credit, lower depending on plan |
Contact data | Emails and phones, enterprise plans only |
The loop this guide builds starts from three rule files and ends with two checks:

In our test, the first batch's lesson, a 10,000-employee cap on the current employer, went into the filter before the second pull.
What does AI candidate sourcing with Claude do?
It turns a role brief into a ranked, checked shortlist inside Claude Code. The database supplies names, titles and employers, Claude judges and keeps the books, and you decide on the rubric and scores.
This guide is for agency, search firm and in-house recruiters working many roles for several clients. It covers sourcing only, not outreach, screening or scheduling.
Claude.ai and Claude Code can both connect to a people database (MCP docs). Pick Claude Code if you source similar roles often: it reads rule files every session, writes shortlists to files and runs many roles from one script, needing only a terminal and a text editor. For other recruiting tasks, see our guide to recruiting workflows with Claude.
Can't I just ask Claude for a list of candidates?
You can, but Claude alone can't reliably name who holds a job today. It answers from training data with a cutoff date (models overview).
An executive search partner told our team in May that Claude's position spec only needed to "adjust by 5%", but its list of IT leaders at target companies was another story: "It barely can give me any names, and just looking at it, I'm like, that guy died four years ago, that guy retired two years ago, she's not been in that job for eight, like, it was horrible."
Keep Claude for judging, and give it a database for facts.
Step 1: How do I connect Claude to a people database?
Install the Crustdata plugin, which bundles the MCP server with a ready-made /crustdata:candidate-sourcing skill:
Then run /crustdata:login in Claude Code and sign in once in your browser (plugin docs).
For the MCP server alone, run this, then sign in through /mcp:
claude mcp add --scope user --transport
claude mcp add --scope user --transport
claude mcp add --scope user --transport
--scope user makes it available in every folder; the default local scope loads it only where you added it, which breaks a folder-per-role setup (MCP scopes).
Ask Claude "How many credits do I have?" A number means you're connected (MCP docs). Any people database with an MCP server works, and only the filter names change. To build on the API, see people search for agency workflows.
Step 2: How do I set firm and client rules once?
Put each rule in a CLAUDE.md file at the level where it belongs, from firm down to role:
Claude Code loads every CLAUDE.md from the folder you start in up to the top, and subfolder files only when it works there (memory docs). Open Claude Code in the role's folder, and it reads all three files before you type.
The firm file holds off-limits lists and career-path rules. An agency recruiter described the problem to our team in July: "We have a client list that we can't touch. We have other clients that aren't on the list that we can't touch." The firm file from our running example:
Which rules go in the search, and which does Claude judge?
Rules a field can check go in the filter, so you pay only for people who pass. Rules that need reading go to Claude:
Rule | Where it goes | How |
|---|---|---|
Off-limits companies | Search filter |
|
Titles you never want (manager, intern, contract) | Search filter | Exclude titles containing those words |
People already reviewed or in your ATS | Search filter |
|
Employer size cap | Search filter | Headcount on the person's primary current role ( |
Career leans enterprise | Claude | Reads every past employer and its size |
Payments work that no title mentions | Claude | Reads titles, headlines and companies together |
not_in matches the whole stored company name, so near misses exclude nobody (Person Search reference). Get stored spellings from free autocomplete first. For a staged version, see multi-layer candidate filtering with Claude.
A CLAUDE.md rule can still slip, because Claude reads it as context and nothing enforces it (memory docs). So put hard rules in the filter too, and re-check at export. In our test, the re-check found no off-limits employer among the 50 people pulled.
How do I keep a client's rules for the whole team?
Write them into the client's CLAUDE.md, in a shared folder. A search firm founder told our team why in October: "If I've spent time, my 45 minutes, teaching it, hey, this client, [client], wants this." The next search should start from those 45 minutes. Our client file:
# Client: Series B payments startup, New York ## What they care about, and why - Engineers who built money movement (ledgers, payouts, card flows), because the hire takes over payouts from a third-party processor - Startup pace: shipped at a company under 1,000 people ## Off-limits for this client (on top of the firm list) - Their banking partners and card processor: [company names] ## Rejected, and why - [profile URL]
# Client: Series B payments startup, New York ## What they care about, and why - Engineers who built money movement (ledgers, payouts, card flows), because the hire takes over payouts from a third-party processor - Startup pace: shipped at a company under 1,000 people ## Off-limits for this client (on top of the firm list) - Their banking partners and card processor: [company names] ## Rejected, and why - [profile URL]
# Client: Series B payments startup, New York ## What they care about, and why - Engineers who built money movement (ledgers, payouts, card flows), because the hire takes over payouts from a third-party processor - Startup pace: shipped at a company under 1,000 people ## Off-limits for this client (on top of the firm list) - Their banking partners and card processor: [company names] ## Rejected, and why - [profile URL]
Claude's auto memory stays on one machine, so teammates never see it (memory docs). An executive search firm asked our team exactly this in September: "Is that saved for me alone? Or is that a learning that will go across the platform for all of us?" So after each round, have Claude write the lesson into the shared file:
Keep sourcing/ in a shared git repository or synced drive. With git, every change shows who made it and when.
Step 3: How do I write the role rubric?
A rubric tells Claude what makes someone a 4, a 2 or a 1 for one role. Write it as you'd brief a sourcer, because a job description alone is a weak brief. Our role file:
# Role: Senior Backend Engineer, Payments
Hybrid, three days a week in New York.
Owns the payouts service as the client moves card payouts onto its own ledger.
## Must-haves in the search filter
- Within 30 miles of New York, 6+ years, 12+ months in the current role
- Current title backend or software engineer, not a manager or contractor
- "Payments" in the headline, current title or current role description
## Must-haves you judge (score 1 if missing)
- Built or operated a payments system: ledger, card processing, payouts
- Mainly backend work, not front-end, mobile or machine learning
## Weighted signals (total 100)
- Payments systems built or operated: 35
- Backend depth in production: 25
- Time at a company under about 1,000 people: 20
- Led a service, a migration or a team: 10
- Stayed 2+ years in at least one role: 10
## Recall list (10 people who should match)
- [name, company]
# Role: Senior Backend Engineer, Payments
Hybrid, three days a week in New York.
Owns the payouts service as the client moves card payouts onto its own ledger.
## Must-haves in the search filter
- Within 30 miles of New York, 6+ years, 12+ months in the current role
- Current title backend or software engineer, not a manager or contractor
- "Payments" in the headline, current title or current role description
## Must-haves you judge (score 1 if missing)
- Built or operated a payments system: ledger, card processing, payouts
- Mainly backend work, not front-end, mobile or machine learning
## Weighted signals (total 100)
- Payments systems built or operated: 35
- Backend depth in production: 25
- Time at a company under about 1,000 people: 20
- Led a service, a migration or a team: 10
- Stayed 2+ years in at least one role: 10
## Recall list (10 people who should match)
- [name, company]
# Role: Senior Backend Engineer, Payments
Hybrid, three days a week in New York.
Owns the payouts service as the client moves card payouts onto its own ledger.
## Must-haves in the search filter
- Within 30 miles of New York, 6+ years, 12+ months in the current role
- Current title backend or software engineer, not a manager or contractor
- "Payments" in the headline, current title or current role description
## Must-haves you judge (score 1 if missing)
- Built or operated a payments system: ledger, card processing, payouts
- Mainly backend work, not front-end, mobile or machine learning
## Weighted signals (total 100)
- Payments systems built or operated: 35
- Backend depth in production: 25
- Time at a company under about 1,000 people: 20
- Led a service, a migration or a team: 10
- Stayed 2+ years in at least one role: 10
## Recall list (10 people who should match)
- [name, company]
Make anything the client would reject outright a must-have, and give the top three remaining signals about 80 of 100 points. For more, see our candidate evaluation framework.
The recall list is 10 people who should match, such as past placements or strong interviewees, for the Step 4 check.
Score only on the rubric's job criteria. Leave out age, gender, ethnicity and their proxies, and keep a person making the final call.
Step 4: How do I size the pool, score batches and search again?
Get the count before pulling anyone, then score 25 at a time:
The count moved like this in our test:
Filters | People who match |
|---|---|
US backend or software engineers with 6+ years | 690,180 |
Plus a finance industry or "payments", within 30 miles of New York | 13,911 |
Swap the industry for "payments" in the headline, title or role description | 393 |
Plus the off-limits list, title exclusions and 12 months in the role | 333 |
An industry filter counts everyone at a finance company, whatever they work on. Swapping it for "payments" in what people write about their own work took the pool from 13,911 to 393. Aim for 100 to 1,500. Over that, tighten a filter. Under about 50, search from a different angle.
What should I check in the first 25?
Check what kind of person comes back, because batch 1 tests the rubric. Have Claude pull and score 25, add your score next to Claude's in shortlist.csv, and send one message about the pattern:
That filter took the pool from 333 to 183, and batch 2 scored better:
Score | Batch 1 | Batch 2 |
|---|---|---|
4 | 2 | 4 |
3 | 3 | 5 |
2 | 5 | 11 |
1 | 15 | 5 |
In batch 1, eleven of the 1s failed the career-path rule, including two with years of real payments work at very large companies. Claude gave a 3 to a founding engineer at a fintech startup and noted their newly added interim VP of Engineering role. The second pull passed the first 25 as post_processing.exclude_profiles, and none came back.
Read the first 10 closely: the wrong kind of person means an unclear rubric. An in-house recruiter told our team in June about a Kotlin search that returned mobile developers. The fix was requiring Kotlin plus a backend signal, "at least two of those considerations".
A 4 means call first, a 3 is a maybe, and 1s and 2s drop. Stop after three rounds, or when two in a row add no new 3s or 4s.
What do I do when the search stops finding new people?
Change what the search starts from, because more adjectives return the same people. An agency founder described the dead end to our team in September as the tool saying that "the universe is already spent when in reality I know it's not spent."
Start instead from target companies, real title variants or a timeframe. For the payments role, ask for "20 companies that operate their own payouts or ledger", check the draft list yourself, then search each one. A timeframe search, such as 2+ years there in the last three, finds alumni.
Does my search find the people I already know?
Test it against your recall list before export. An engineering recruiter on r/recruiting wrote that AI sourcing tools "miss a lot of candidates that I found in fairly basic searches." Ask Claude:
The check sorts your 10 names into three groups:

Eight or more found means the search covers the pool. A name dropped by a rule means a filter is too strict: fix it in CLAUDE.md and rescore. Source anyone not in the database by hand.
Step 5: How do I check my ATS and get contact details?
Check the ATS twice: before each pull and before export. A search firm partner told our team in June what they wanted: "Of these 25 that we found, it should be able to say 15 of them are already in your system."
Before the pull, save an ATS export of the client's candidates, with profile URLs, in the client folder, and add to its CLAUDE.md:
The second line covers teammates' shortlists. An agency recruiter told our team in July what skipping it costs: "We're all trying to reach out to the same people. We don't want to spam people at the same time."
Before export, match the final list and get contacts only for people you'll call:
Check your ATS import template before the first export. Before outreach, check data-protection rules where candidates live, and honor opt-outs.
How do I work many roles at once?
Give every role its own folder and rubric, then run them in one claude -p batch. A recruiting lead at a talent marketplace told our team in July that "each of the recruiters usually handles anything between 15 to 25, 30 positions, opens at the same time."
claude -p runs Claude Code without the interactive screen and loads CLAUDE.md files like a normal session, unless you add --bare (headless docs). Anthropic plans to make --bare the -p default, so confirm rules still load after updates. Save one prompt as sourcing/batch-run.md:
Then loop over the role folders:
cd ~/sourcing for role in clients/*/roles/*/; do (cd "$role" && claude -p "$(cat ~/sourcing/batch-run.md)" \ --allowedTools "Read,Write,Edit,mcp__crustdata__*" > run-log.txt) done
cd ~/sourcing for role in clients/*/roles/*/; do (cd "$role" && claude -p "$(cat ~/sourcing/batch-run.md)" \ --allowedTools "Read,Write,Edit,mcp__crustdata__*" > run-log.txt) done
cd ~/sourcing for role in clients/*/roles/*/; do (cd "$role" && claude -p "$(cat ~/sourcing/batch-run.md)" \ --allowedTools "Read,Write,Edit,mcp__crustdata__*" > run-log.txt) done
Each pass starts in a role folder, so it reads that rubric plus the client and firm rules. --allowedTools approves file edits and every crustdata server tool, since claude -p can't stop to ask (headless docs, permissions docs). Plugin tools are named mcp__plugin_crustdata_<server>__*, so check the exact name in /mcp.
Then read each role's 4s, skim the 3s and check notes.md for roles that stopped. Each stop rule caps credits. For a small firm's version, see a two-person firm with 30 active roles.
How much does one role cost in credits?
About 31.5 credits, applying list rates to our test's counts:
Item | List rate | Credits |
|---|---|---|
Two batches of 25, filtering on and getting back work history | 0.23 per result | 11.5 |
Full profiles for the 14 people scored 3 or 4 | 1 per person | 14 |
Business emails for the 6 people scored 4 (enterprise plans) | 1 per matched person | Up to 6 |
Total | About 31.5 |
The 0.23 is a 0.03 base plus 0.1 each to filter on and receive work history (pricing docs). Personal emails and phone numbers cost 2 credits each per matched person, also on enterprise plans, and no match costs nothing (Contact Enrichment docs).
To keep a list current, a discovery watcher reruns the search on a schedule for 0.5 credits per new person at the 30-day refresh (pricing docs). Credits cost $0.30 to $0.01 per credit, lower depending on plan.
When is a sourcing platform a better fit than Claude?
A platform fits better when you want outreach and ATS sync ready-made. Claude with a people database fits better when per-client rules, such as off-limits lists, decide the shortlist.
Option | What it does well, from its own pages | Verdict |
|---|---|---|
AI search, email outreach on paid plans, ATS or CRM integration on Business, and add-on agents that can auto-shortlist. From $99 per seat a month billed yearly | Better fit for search, outreach and background agents in one place | |
Sourcing, applicant review, AI screening and scheduling on top of your ATS, with 40+ native ATS integrations. Solo from $494 a month | Better fit for one platform across the funnel | |
Search across its profiles and your ATS, with past-candidate rediscovery, on integration plans, plus an MCP server for Claude and other assistants. Sourcing Core is $149 a month paid annually | Better fit if ATS rediscovery matters most | |
Finds candidates, writes to them, follows up and books interviews, with multi-client workspaces and 120+ ATS integrations on higher plans. Solo is $100 a month per user, billed annually | Better fit for agencies wanting outreach and booking done for them | |
Claude with a people database | Firm, client and role rules in your own files, soft rules judged per person with a reason, many roles per batch, credits per result. You set up the ATS check and outreach | Better fit when off-limits lists and career-path rules decide the list |
Test both on your hardest open role, and compare how many of your 10 known names each finds.
Where do I start this week?
Start with your hardest role and one client:
Connect Claude to a people database (Step 1).
Write the firm file and that client's file (Step 2).
Write the role rubric and your 10 known names (Step 3).
Check the count, then score the first 25 (Step 4).
The first role takes longest, since the rule files start empty. Start on a Crustdata account at crustdata.com, or book a demo for help with your first role.
Frequently asked questions
How can AI be used in candidate sourcing?
AI searches a people database against your filters, ranks each person with a reason, builds target company lists and checks the shortlist against your ATS. The recruiter still decides who gets contacted.
What is the best AI for candidate sourcing?
Pin and Juicebox suit teams that want outreach done for them, hireEZ adds screening and scheduling, SeekOut pairs search with ATS rediscovery, and Claude with a people database holds your own firm and client rules.
Can Claude remember my sourcing rules across searches?
Yes, when they're in CLAUDE.md, which loads in full at every session start. Auto memory also carries notes forward, but only the first 200 lines or 25KB of its index load at start (memory docs), so hard rules belong in CLAUDE.md.
Can my whole team share the same client rules?
Yes, keep each client's CLAUDE.md in a shared folder so every session reads the same file, and put personal notes in a CLAUDE.local.md beside it. In a git repository, add CLAUDE.local.md to .gitignore so it isn't committed (memory docs).
Can Claude check candidates against my ATS?
Yes, against an ATS export file, since this setup has no direct ATS connection. Claude skips everyone in the export on each search, then matches the final list by profile URL and by name plus company. Re-export before each new search for a client.
How many roles can one recruiter handle with Claude?
Every open role can go through one claude -p batch, each with its own folder and rubric. Start with five and check each one's counts and 4s, since review time and credits set the limit.
What's the difference between a sourcing tool and an ATS?
A sourcing tool finds people who haven't applied, and an ATS tracks candidates through hiring. Some platforms search both, which SeekOut calls ATS rediscovery.
What is the difference between sourcing and recruiting?
Sourcing is finding and qualifying people, usually before they apply. Recruiting covers the rest, from screening to offers and closing.
