AI Prompts for Candidate Sourcing Strategy

Sourcing is a market problem before it is a messaging problem: where does the capability exist, in what volume, and through which channels can it be reached at what cost? Posting and waiting works for some roles and fails silently for others. A sourcing strategy maps the pools, chooses channels on evidence, sets the pipeline arithmetic (how many conversations produce one hire), and runs as a sprint with metrics rather than as an open-ended search.

These prompts map the market, build the searches and targets, and plan the sprint. Outreach messages have their own page; this is where the search decides who receives them.

Before you use these

Have these ready to replace the highlighted [variables]:

• Candidate profile and must-haves
• Historical funnel data: sourced → replied → screened → interviewed → offered → hired, by channel if available
• Channels available: job boards, referrals, internal mobility, agencies, communities, events, direct sourcing
• Time to fill target and recruiter capacity

The prompts

• 1. Map talent pools and channels
• 2. Build searches and pipeline targets
• 3. Plan the sourcing sprint and metrics

1. Map talent pools and channels

Act as a talent sourcing strategist mapping the market for [role] at [company].

Candidate profile: [likely situations, capabilities, motivators]
Channel history: [past hires for similar roles by source; reply and conversion rates by channel if known]
Channels available: [list, with cost and recruiter time each requires]
Constraints: [location/remote, level, timeline]

1. Talent pools: 4–6 distinct pools (by current situation, sector, adjacent function, internal), with estimated size (with basis), fit to the profile, and competition for them.
2. For each pool: the channels that reach it (direct sourcing, referrals from specific teams, communities, events, boards, agencies, internal mobility), expected yield per unit of effort, cost, lead time, and any diversity-of-pipeline consideration (widening pools, not screening on characteristics).
3. Prioritize pools by fit × reachability; explain what is deprioritized and why.
4. Channels to stop using for this role, with the evidence.
5. Referral plan: which employees are connected to which pool and the specific ask.
6. Risks: pools where our positioning is weak, and what would need to change.

Base estimates on the history given; mark market-size figures as estimates.

2. Build searches and pipeline targets

You are building the search plan and pipeline targets for [role].

Must-haves and equivalents: [list]
Pools prioritized: [from the map]
Funnel rates: [sourced → reply, reply → screen, screen → interview, interview → offer, offer → accept — measured or assumed, say which]
Timeline and capacity: [target fill date; recruiter hours per week for sourcing]

1. Search strings per pool: capability and outcome terms, title variants, exclusion terms; what each string will miss and the complementary search to cover it. Avoid terms that narrow to pedigree, age or location proxies.
2. Funnel math: from 1 hire (or [n] hires) backward to sourced contacts, by stage, using the rates; the weekly sourcing volume implied and whether it fits capacity.
3. Sensitivity: the stage rate with the most leverage and the effect of a ±10-point change.
4. Weekly targets by stage for the sprint duration.
5. Quality guardrail: the screen-stage criteria that keep volume from being pursued at the expense of fit.
6. Assumptions list.

Show the arithmetic. If the volume exceeds capacity, say which pool or channel to add rather than stretching the recruiter.

3. Plan the sourcing sprint and metrics

Act as a recruiting lead planning a sourcing sprint for [role], [n] weeks, target [hires].

Pool map and search plan: [summary] Targets by stage: [from the funnel]
Team: [recruiter(s), sourcer, coordinator, hiring manager availability]

1. Rhythm: daily sourcing blocks by pool, outreach send windows, screen slots, a weekly pipeline review with the hiring manager.
2. Metrics with thresholds: contacts sourced, reply rate by pool and message, screen pass rate, interview conversion, time in stage — and the level at which each triggers a change (new pool, new message hypothesis, requirement revisit).
3. Decision rules: when to add a pool, when to escalate to referrals or agency, when to reopen the requirements with the manager.
4. Hiring-manager touchpoints: what they see weekly, what decisions they must make quickly (feedback SLA), and the calibration on the first three candidates.
5. Candidate experience: response SLAs and the update cadence for everyone in process.
6. Retrospective at sprint end: what to measure and what to change for the next sprint.

Keep the plan proportionate. A sprint with fifteen metrics reviews none.

Related prompts

• Role Intake and Success Profiles
• Candidate Outreach Messages
• Recruitment Marketing and Employer Brand
• Resume Screening Rubrics
• Phone Screen Guides
• Workforce Planning

Logical next step

After this, most HR teams move on to Role Intake and Success Profiles.

All Human Resources prompts · Search the full library