How to Engage Passive Candidates, Not Just Find Them
Photo by Claire

Most companies think they have a sourcing problem. They almost never do.

Ask a founder why hiring is slow and you will hear some version of the same answer. We can't find the right people. Not enough candidates in the pipeline. The market is tight.

Then watch what actually happens. They run a search. They get four hundred profiles. Fifty of them look genuinely good. They send messages to all fifty and get three replies, two of which are polite declines.

The pipeline was never empty. The replies were.

This distinction matters more than almost anything else in hiring, and it is the thing most teams get wrong. Finding candidates is a solved problem. It has been solved for years. Search tools are cheap, databases are enormous, and AI made the whole thing faster again. If your only advantage is that you can find people, you have no advantage. Everyone can find people now.

What nobody solved is the part after.

Why passive candidates ignore you

The people you want are not looking for a job. This is not a detail. It is the whole situation.

A senior engineer who is good at their job has a salary they are fine with, a team they mostly like, and a problem in front of them that is interesting enough to think about on the walk home. They are not browsing job boards. They are not updating their CV. They receive several recruiter messages a week and delete nearly all of them without finishing the first sentence.

To move that person you have to do something harder than finding them. You have to give them a reason to reconsider a life they are already content with.

Most outreach does not attempt this. It describes a role. It lists requirements. It mentions that the company is growing fast and the opportunity is exciting. None of that is a reason. It is a description of a job posting with the candidate's first name at the top.

What actually works

The messages that get replies do three things.

They prove someone looked. Not at a job title, at the actual work. Something specific enough that the candidate knows this was not sent to two hundred people.

They name the problem the person would own. Not responsibilities. A problem. Engineers who are good at their jobs are motivated by problems they cannot stop thinking about, and there is no way to know if yours qualifies unless you tell them what it is.

They show the team. Who they would work with, how those people think, what the company is trying to do and why it matters. Candidates are not evaluating a role. They are evaluating whether the next two years of their life will be worth it.

That is a lot of work per candidate. Doing it well for one person takes twenty minutes. Doing it for fifty takes a week you do not have. Which is exactly why most companies send the generic version and then conclude that passive candidates do not respond.

Where Vashly fits

We built Vashly around the second half of the problem, because the first half is already commoditized.

Search is table stakes for us. We do it across a very large professional pool, and we do it fast, but that is not the point of the product. The point is what happens once the right person is in front of you.

Vashly builds a team & product story around your company. The problem the hire would own, the people they would join, the technical challenges, why any of it matters. Then it writes outreach for each specific candidate, in email and on LinkedIn, in their language, drawing on their actual background rather than a template with a merge field.

The candidate does not get a job description. They get a case.

Then you see who is engaging. Who opened the pitch, who read the team section, who came back to it two days later. That tells you where to spend your time, which is a more useful signal than how many messages you sent.

The uncomfortable test

Think about your best hire. The one who changed how the company works.

Did they come through a job ad?

For most companies the answer is no. Someone found that person and made a real case to them. It worked, and then it never happened again at scale, because doing it by hand does not scale.

That is the gap. Not finding people. Convincing them.

blog-pic2
Photo by Carwan
More Interesting Topics