Passive candidate sourcing: a practical method for recruiters
By Drippay, Inc.Published 7 min read
Passive candidate sourcing is finding and engaging people who are not looking for a job. They are employed, not on job boards, and will not apply; a recruiter has to locate them, earn a reply, and often wait. It is slower than working applicants and it is how hard reqs and senior searches actually get filled.
This guide covers what makes a candidate passive, where to look, how to turn a req into a target list, first messages that respect the person’s situation, and how to keep a pool warm between roles.
What passive really means
Passive is a spectrum, not a switch. At one end are people who would move for the right role but have not looked; at the other are people who are content and will only talk to someone they trust. Senior and specialist candidates can sit anywhere on that spectrum, so confirm interest instead of inferring it from a profile. A passive candidate does not owe you a reply, and the tone that works with an applicant fails here.
Where passive candidates are found
Start where the person does their work, not where job seekers gather.
- Professional profiles and company pages: who holds the equivalent role at the companies your client competes with or hires from.
- Your own database: past applicants and sourced profiles who were not looking then and may be now. Rediscovery searches existing records, which can include both active and passive candidates.
- Professional communities: conference speaker lists, association directories, open-source contributors, licensing boards, published authors in the field.
- Referrals from placed candidates and from people who declined: a no with a name attached is a sourcing result.
- Sourcing platforms: tools such as Loxo describe searching external market data alongside internal records, and Juicebox describes conversational search with profile assessment. They speed the finding; the message is still yours.
Related: Candidate rediscovery: sourcing the records you already haveAI sourcing tools compared by use case
From req to target list
A req describes a job; a target list describes the people likely to be doing it now. Translate one into the other before you search.
| Req element | Ask | Search input |
|---|---|---|
| Title and level | What titles do people with this job actually hold at other companies? | Three to five title variants, seniority markers |
| Must-have skills | Which two or three are rare enough to narrow the pool? | Skill or certification terms, not the whole list |
| Company context | Which companies produce people who succeed in this environment? | Named competitors, suppliers, customers, or alumni pools |
| Location and mode | Where can the person live, and would relocation ever be considered? | Metro radius or remote eligibility |
| Motivation to move | What would make someone in this seat listen? | The one sentence your message leads with |
A worked example: a client wants a plant controller for a food manufacturer. The title variants are controller, plant controller, and site finance manager; the narrowing skill is standard-cost accounting in a manufacturing environment; the source companies are other food and beverage plants within commuting distance; and the motivation is a plant that is expanding rather than consolidating. That list is a few dozen people, which is the right size for personal messages.
First messages to people who are not looking
Lead with why them, name the role plainly, and ask for permission rather than a call. Keep it short; the reply you want is a question.
Hi Priya, your work on the cold-chain rollout at Meridian came up when I was mapping controllers in the region. I am working a plant controller search for a food manufacturer in the north metro that is adding a second line next year. You may be entirely settled; if so, ignore this. If you are curious what the role and range look like, I can send a one-paragraph summary.
Specific reason for the contact, honest about the person’s likely position, a low-commitment next step.
Priya, one follow-up and then I will leave it. The range on the controller role came back higher than I expected, and the plant manager is someone who was a controller herself. If either changes anything, I am easy to reach. Either way, good luck with the rollout.
Adds one new fact, names the close, and leaves the door open without pressure.
Related: Candidate outreach: tools, automation, and templates
Keeping a passive pool warm
Most passive candidates say not now. Record why and when to ask again, and give them a reason to hear from you before the next role: a relevant market note, a compensation observation, an introduction. A pool of people who know your name and your niche is the asset that makes the next hard search shorter.
Discuss this workflow with dreach
dreach is a managed service for staffing firms, run by hand in the pilot. It watches the employers your firm knows and the ones it can reach through a warm path, such as a current or past client, a person your firm placed who now works at the hiring company, or a contact your team authorizes. It flags new openings with the source and date, confirms the hiring manager to contact, and shows the warmest way in. For a live role, it ranks people your firm already knows from its own ATS, past placements, and network your firm authorizes, and shows why. Your team makes every contact; dreach contacts no one. Scope, data access, integration requirements, and availability are confirmed before starting.
Bring a hard-to-fill req and we will look at whether an intro path through your own network beats a cold approach.
Discuss your candidate workflowPassive candidate sourcing is a target list built from the req, a short personal message that says why this person, one honest follow-up, and a record of every not-now so the pool stays warm. Tools speed the finding; the message and the patience are the recruiter’s.