Inside a Placement Story: How Passive Candidate Sourcing Fills Roles Everyone Else Gives Up On

Passive candidate sourcing means recruiting people who are not applying to anything, not browsing job boards, and not on the market at all, by reaching them through a relationship a recruiter has already built with them. It works because trust does the job that a job posting cannot: it gets someone to seriously consider a move they were never planning to make.

I want to walk through one placement in particular, because it is the cleanest example I have of why this matters, and because it is real, not a hypothetical built to sell you something.

The role that sat open for almost two years

A nearshoring company came to me with a Solutions Engineer opening. On paper it sounds like a normal req. In practice it was a strange, narrow blend: deep technical fluency, the interpersonal skill to sit in a room with a client and actually connect, and the polish to operate in front of high-end clients in an executive capacity. Not an engineer who could be coached into client-facing work eventually. Someone who already had all three. It is the same kind of rare, multi-dimensional profile I see in searches for a founding engineer: the skills matter, but so does the judgment and presence that no interview loop can manufacture in someone who does not already have it.

They had been trying to fill it for almost two years before they found me. Two years of postings, probably multiple agencies, probably a stream of candidates who were strong on one axis and missing the other two. I bring up the nearshoring detail only because it is true and I do not want to sanitize the story, but the industry the client was in is not really the point of this post. The point is what it takes to fill a role like that at all, in any industry.

The relationship that filled it

I did not find this candidate on LinkedIn the week the req landed. I had known him for years, from a previous placement I had made. We had stayed in touch the ordinary way a good recruiting relationship stays alive: check-ins, catching up on where his career was heading, no agenda beyond genuinely caring how things were going for him.

He was not job hunting. He was not “passively open” in the vague way people use that phrase to describe anyone who would theoretically answer a recruiter’s message. He was settled. But because I understood what he actually wanted out of his career, not just his title and comp range, I knew this role fit him before I ever mentioned it to him. When I did, he was open to it purely because it was me asking. That is not me being sentimental about it. That is the mechanism. The trust built over years is what let one conversation do what two years of job postings could not.

flowchart LR
  A[Prior placement<br/>relationship begins] --> B[Years of check-ins<br/>no agenda, real trust]
  B --> C[Candidate stays employed<br/>not job hunting]
  D[Client opens search<br/>Solutions Engineer role] --> E[~2 years unfilled<br/>via postings and other agencies]
  E --> F[I already know<br/>who fits and why]
  C --> F
  F --> G[One conversation<br/>grounded in years of trust]
  G --> H[Placement made]
  classDef base fill:#ECFDF5,stroke:#10B981,stroke-width:1.5px,color:#065F46
  classDef high fill:#D1FAE5,stroke:#059669,stroke-width:1.5px,color:#0A2E22
  class A,B,C,D,E base
  class F,G,H high

The years-long relationship that made a two-year-old req fillable in one conversation.

Why passive candidates are so often the right fit

There is a structural reason this keeps working, and it is not specific to this one candidate. Most of the workforce is not looking.

LinkedIn’s Talent Trends research, drawn from 18,000 professionals across 26 countries, found that 75 percent of the global workforce is not actively job hunting. Of that group, roughly 45 percentage points are still open to hearing about the right opportunity if a recruiter reaches them the right way. Add that to the 25 percent who are actively searching, and you get a workforce where the large majority is theoretically reachable, but only a quarter of it will ever show up as a resume in your applicant tracking system.

pie showData
  title Active vs. passive candidates (global workforce)
  "Passive (not actively job hunting)" : 75
  "Active (applying now)" : 25

Source: LinkedIn Talent Solutions, Active vs. Passive Candidates (18,000 professionals, 26 countries)

That gap is the whole game for a hard-to-fill role. If your search strategy is limited to people who apply, you are drawing from a quarter of the available talent, and you are competing with every other company doing the exact same thing for the exact same slice. The other three quarters are not unavailable. They are just unreachable through a job posting.

Passive candidates also tend to perform better once hired, and the data on relationship-sourced hires backs this up specifically. An analysis of more than 90,000 employees across 50 companies, cited by iCIMS, found that half of all referral-sourced hires had a median tenure of 38 months, compared to a median of 22 months for hires sourced through other channels. SHRM has separately reported that referral hires convert from interview to offer at meaningfully higher rates and tend to stay longer, which tracks with what I see: someone who comes in through a trusted relationship has already been informally vetted for fit, not just skills, before I ever submit them.

None of this means active candidates are worse. Plenty of excellent people are between roles or actively looking for good reasons. It means that for a role like this Solutions Engineer search, where the requirement is a rare combination rather than a common skill, the pool you need probably is not applying anywhere, and you have to go find it.

How a long-term relationship gets someone “off the sidelines”

Passive candidate recruiting is often described like a sourcing technique, a set of Boolean strings and cold InMails. That is the mechanical layer. The part that actually moves someone is trust, and trust is not something you can build in the two weeks between a client signing a contract and a deadline.

A few things had to be true for this placement to work, and they generalize to almost every passive placement I have made:

I had to actually know him, not just have his contact information. Years of conversations meant I understood his career goals, what had frustrated him in past roles, and what he valued beyond salary. That is different information than a resume gives you.

He had to trust that I would not waste his time. If I had a track record of pitching him roles that were not real fits, this conversation would have gone nowhere. The relationship only pays off if you have been disciplined about not spending it on mediocre opportunities.

The timing and the fit both had to be right, and I had to be watching for both. I was not shopping this candidate around. I was holding a specific understanding of what he wanted, and when a role matched it, I made exactly one call.

This is also, structurally, what executive search recruiters do at senior levels, even when the client-facing language sounds different. A retained executive search is built on the recruiter’s existing network of people who are not actively looking, not on inbound applications. The Association of Executive Search and Leadership Consultants holds its member firms to standards built around exactly this kind of relationship-driven, confidential search, because at the senior end of the market, the people worth hiring are almost never the people applying.

Passive vs. active candidate sourcing: what you’re actually choosing between

Neither approach is universally right. The table below is how I think about which one a given search actually needs.

Dimension	Active candidates (applying, on job boards)	Passive candidates (sourced via relationships)
Job search status	Actively applying, often to several companies at once	Not looking; typically employed and reasonably content
Where you find them	Postings, inbound applications, job boards	A recruiter’s existing network and long-term relationships
Competition for them	High. The same person is in several other pipelines right now	Low to none. They are not in anyone else’s pipeline
What moves them	Compensation, timing pressure, need for a change	Trust in the person reaching out, and a role that is genuinely a better fit
Vetting you’re doing blind	High. You are often forming your first real opinion of them from an interview loop	Lower. A recruiter with history already has a read on their work and character
Best suited for	Roles with a broad, well-defined pool of qualified applicants	Senior, hybrid, or highly specific roles where the right person is not searching

The Solutions Engineer role belonged firmly in that last row. A blend of deep technical skill, client-facing polish, and executive presence is not a common combination, and the people who have it are rarely unemployed or restless enough to be actively applying anywhere.

What this means for your search strategy

If a role has been open for months and the usual channels have not produced anyone, that is not always a sign you need a better job posting. Sometimes it is a sign the person you need has never seen a job posting, because they are not looking at any.

A few things follow from that, and they are the same things I would tell any founder or hiring manager sitting on a role like this:

Stop measuring the search by resume volume. A pile of applicants tells you the posting reached a lot of active candidates. It tells you nothing about whether it reached the one passive person who actually fits. I have written before about why strong engineers do not apply to your roles, and the short version is that your best-fit hire is disproportionately likely to be someone who was not looking.

Ask whoever you are working with what their actual network looks like. A recruiter’s value in a passive search is almost entirely the depth and relevance of relationships they have already built, not the size of a database they can query. If a recruiter’s answer to “how would you find this person” is “we will post it and see who applies,” that is a job board, not a passive search.

Expect a longer runway to build the relationships that eventually pay off, but not necessarily a longer runway to fill this specific role. Ironically, once the right relationship exists, the placement itself can move fast, sometimes faster than a role that is drawing from an active, oversaturated pool. The slow part already happened, years before the req existed.

Recognize when passive candidates aren’t actively unhappy where they are; they simply haven’t been given a reason to think about a change. That is a different conversation than recruiting someone who is desperate to leave, and it needs a different kind of pitch: specific, honest about what the role actually offers, and delivered by someone they have a reason to believe. I have written about the signals that tell someone it might be time for a new role even when they are not actively looking, and a good passive pitch speaks directly to those signals rather than a generic “we’re hiring” message.

This is where I will make the one plug I think is fair here: this is a meaningful part of what I do at Kruger Recruiting. My placements average a 21-day fill time and a 2 percent attrition rate in the first year, and a chunk of that comes from being able to reach candidates who were never going to apply anywhere, because I already know them. It is also part of why the fee structure for this kind of search looks the way it does, which I cover in more detail in how tech recruiter fees actually work: you are paying for access to a pool that does not show up in an ATS, not for volume.

The bottom line

The Solutions Engineer search did not get solved because I ran a smarter Boolean query or wrote a better job description. It got solved because I had spent years being someone a specific person trusted, and because I understood what he actually wanted clearly enough to recognize the fit the moment it existed. Two years of job postings could not do that. One phone call, backed by years of relationship, could.

If you have a role that has been open for a while and the usual channels are not producing anyone, that is worth a real conversation before you post it for the third time. Book a free strategy call and I will tell you honestly whether this is a search that needs a wider net or a deeper relationship, because they are not the same problem, and they do not have the same solution.

Sources and further reading

Frequently Asked Questions

What is passive candidate sourcing?

Passive candidate sourcing is the practice of recruiting people who are not actively applying for jobs or browsing job boards, typically by reaching them through an existing relationship or network rather than an inbound posting. It relies on the recruiter, not the job posting, to do the work of surfacing and vetting the person.

How do you find passive candidates who aren’t on the job market?

The most reliable way is through relationships built over time, often from previous placements, industry contacts, or ongoing conversations that have nothing to do with an open req. Tools like LinkedIn can help identify who exists in a given niche, but the actual movement usually comes from a recruiter the candidate already trusts, not a cold message from a stranger.

Are passive candidates better hires than active applicants?

Not automatically, but for narrow or hybrid roles they often are, because they were selected for fit rather than self-selected by who happened to apply. Data on referral-sourced hires, which follow a similar trust-based path, shows meaningfully longer tenure than hires sourced through open channels, according to research cited by iCIMS.

What’s the difference between passive candidate recruiting and executive search?

They overlap heavily. Executive search is typically passive candidate recruiting applied to senior and leadership roles, run on a retained basis because the pool of qualified, relevant people is small and rarely actively job hunting. The mechanics, relationship-based sourcing over a posting-based one, are largely the same.

How long does it take to fill a role through relationship-based sourcing?

It depends entirely on whether the relationships already exist. If they do, a passive search can move faster than an active one, sometimes in a single well-placed conversation, because the vetting and trust-building already happened. If a recruiter has to build the relevant network from scratch, it takes longer, which is why the depth of an existing network matters more than the size of a database when you are evaluating who to work with.

Should I still post the job if I’m using a recruiter for passive sourcing?

There is no harm in posting it, since it can still catch strong active candidates or people at the edge of “tiptoeing” toward a move. Just do not expect the posting to solve a search that has already failed to fill through postings. If a role has been open for months, the fix is usually a different sourcing approach, not a better-written listing.