You posted the role. You got applicants. And somehow, none of them are the people you actually wanted.
That gap is not a mystery. The strongest engineers, AI researchers, finance leaders and sellers are mostly employed and not applying. Job posts mostly reach people who are already looking. The people who would change your quarter are busy shipping, closing books or hitting quota — not refreshing your careers page.
Passive candidate recruiting is how you reach them anyway. Not with a louder job post. With a sharper story, better timing and outreach that respects that they are happy where they are — the approach our recruiters use across a 1.5M+ candidate network.
Active vs. passive: why job posts miss the people you want
Active candidates are already in the market. They applied, updated LinkedIn or told a friend they are open. They are valuable — and they are the group every other company is competing for through the same channels.
Passive candidates are not in the market. They are employed, often performing well, and not scanning job boards. The only way they enter your funnel is if someone finds them, makes a case and earns a conversation.
Job posts are built for the first group. They sit on a careers page or job board and wait. Passive candidates do not. If your pipeline is mostly applicants, you are mostly seeing people who raised their hand. The quiet ones — systems shipped, quotas crushed, audits led — never raise it.
That does not mean you abandon posting. It means you stop treating the apply button as your entire sourcing strategy. Passive sourcing is the other half: search, network and outreach aimed at people who would be great if they said yes.
Signals of a strong passive candidate, by function
You cannot cold-message everyone with the right title. You need signals that someone is worth the ask. Here is what we look for by function.
Engineering and AI
Look past the stack list. Look at what they shipped and how their scope grew.
Systems they shipped. Production systems, not side projects. Real users, real uptime, real tradeoffs.
Scope growth. Individual contributor to tech lead. Feature owner to platform owner. One team to cross-team influence.
Tenure on strong teams. Time spent where the bar is high tells you more than a flashy title at a weak shop.
Depth over buzzwords. For AI and ML roles especially, we care whether they can explain the work — data, model choices, failure modes — not whether they can name every framework.
A strong passive engineer is often the person who just finished a hard build and is not looking. That is exactly when a well-timed conversation lands.
Finance and operations
Titles in finance are noisy. Signals are clearer.
Audits they led or survived. Clean close under pressure. Controls that held. An auditor who trusted their work.
Raises or systems they owned. A fundraising process, a new ERP, a forecasting model the board actually uses.
Ownership of the messy middle. Month-end that used to take three weeks and now takes five days. A process someone else is still copying.
Passive finance leaders rarely apply because they are deep in the work. The signal is not "open to work" — it is evidence they have already done the hard version of your job somewhere else.
Go-to-market
Sellers and GTM leaders leave a trail if you know where to look.
Promotions that match performance. Not title inflation — real step-ups tied to results.
Quota history. Consistent attainment beats one lucky year. Look for pattern, not a spike.
President's Club and peer recognition. Awards are not everything, but repeated recognition usually means something.
Ramp and retention stories. People who built a book, kept it and helped others do the same.
A top seller crushing quota is not applying. They are closing. Your outreach has to sound like an opportunity, not a job blast.
Outreach that gets replies
Most passive outreach fails for the same reason: it is about you, not them. Long. Vague. Comp buried. Role unclear. It reads like a template that could have gone to anyone with that title in that city.
What gets replies is specific, short, role-first, with the comp range up front. You are asking for a conversation, not a career change on the spot.
Bad sample message:
Hi Jordan — I came across your profile and was really impressed by your background! We are a fast-growing company changing the industry, and we have an exciting opportunity on our team. Would love to connect and share more. Let me know if you are open to a chat!
Why it fails: no role, no reason they were picked, no comp, no specificity. "Impressed by your background" is what you say when you have not read it.
Good sample message:
Hi Jordan — noticed you led the payments platform rebuild at [Company] and moved from IC to tech lead while shipping it. We are hiring a Staff Engineer to own a similar rebuild for our billing stack (remote, US). Comp range is $210–250K base + equity. Worth a 20-minute chat this week, even if timing is not right?
Why it works: specific signal, clear role, scope they can picture, comp up front, low ask, room for "not now."
A few rules we stick to:
Lead with the role and the reason. Why them. Why this job.
Put compensation in the first note. Passive candidates will not chase you for a range. Missing it often means no reply.
Keep it short. If it needs a scroll, cut it.
Make the next step tiny. A short call, not a five-round commitment.
Use channels that fit. LinkedIn Recruiter, warm intros, referral and exec networks, and targeted outreach beat one more generic InMail blast. Our teams also use Loxo, AI sourcing and programmatic ads to find people — then a human writes the note that actually gets sent. AI helps with discovery and drafts; human screens still judge real depth.
What moves someone who's happy
Perks do not move happy people. Free snacks and a foosball table are not a reason to leave a job they like.
What does move them:
The problem. A harder, more interesting problem than the one they have now. Scope they can describe to a friend in one sentence.
The scope. Ownership. Mandate. Room to build, not just maintain.
The manager. Who they would work for matters as much as the company brand. Strong passive candidates ask about the manager early, and they should.
A realistic comp picture. Cash, equity, level and how the offer compares to where they sit today. Vague "competitive package" language loses trust fast.
You are not selling escape. You are selling a better next chapter. If you cannot name the problem, the scope, the manager and the money, fix the story before you hit send.
Don't lose them in the process
Passive candidates drop out of slow loops first. They already have a job. Every extra day of silence, every redundant interview round and every "we will circle back next week" is a reason to stay put.
If your process takes six weeks and four overlapping conversations to decide, you will lose the people who were never desperate to leave. Design the loop like you mean it: clear stages, fast feedback, a decision owner and a calendar that respects borrowed time.
We cover round count and calendar length — both create exit ramps — in How Many Interview Rounds (https://www.isgpartners.com/blog/how-many-interview-rounds). Compress the loop without cutting signal. Passive talent notices both.
Speed is not only kindness. For employed candidates, speed is the product. Our searches aim for 14 days to hire against a 52-day industry average, because waiting is how you lose people who had options the whole time.
"Not now" starts a relationship
A "not now" from a strong passive candidate is not a loss. It is the start of the relationship — if you treat it that way.
Say thank you. Ask what would make timing better. Note the signal that made you reach out. Stay useful without being a pest. When their company shifts, their manager leaves or they finish the project keeping them put, you want to be the name they remember.
Ghosting a "not interested" burns a network. Handling it well builds one. Every search produces one hire and a lot of conversations — and the conversations are the asset. Candidate Experience Is a Revenue Problem (https://www.isgpartners.com/blog/candidate-experience-revenue-problem) digs into why every touchpoint matters, including the ones that do not convert today.
When to bring in help
You can build passive sourcing in-house. Many talent teams do parts of it well. Bring in help when the gap is clear: you are getting applicants but not the right ones, your team is buried in reqs, or the roles you need live in a market you do not already know.
An embedded recruiter changes the math. They bring an existing passive network, work inside your process and culture, and carry about 5–7 open roles at a time — focused enough to do real sourcing, not spray-and-pray. At ISG, that is Talent as a Service: a dedicated recruiter on a flat monthly fee, month to month, so you can scale up or down as hiring changes.
What that looks like in practice:
Live in 3–5 days. Your embedded recruiter is active quickly, with first candidate profiles typically within 3 days of kickoff.
A bench that is already warm. 1.5M+ candidates across 50+ major markets, built through real relationships — including people who said "not now" last year.
Multi-channel sourcing. LinkedIn Recruiter, Loxo, AI sourcing, programmatic ads, and referral and exec networks — then human judgment on who is worth the note.
Cost that does not punish senior hires. Flat monthly fee instead of a percentage of salary. Clients typically save 50–80% on cost per hire versus traditional search.
If your job posts are full and your shortlist is empty, the problem is not posting louder. It is reaching the people who were never going to apply.
Ready to reach the candidates your job posts can't? Talk to ISG (https://calendly.com/meetings-isgpartners/30min) about embedding a recruiter who already knows how to find them.