top of page

Engaging Passive Candidates: Chasing People Who Aren’t Chasing You

Oct 27
6 min read

You have been in high school, right?

At some point, someone probably told you that if you liked somebody, you should not look too interested, because the more interested you looked, the less interesting you somehow became.

Questionable life advice, arguably. Surprisingly useful recruitment advice.

When recruiters approach passive candidates, we sometimes forget one fairly important fact: they were not looking for us.


We have a role to fill, we think it is interesting, we have looked at their background and decided they could be a good fit, so it is easy to assume that they should now be interested in hearing about it. But passive candidates are, generally speaking, people who are reasonably happy where they are. Their job is not perfect, because no job is, but nothing is pushing them hard enough to spend an evening updating a resume, browsing job boards and completing an application form asking them to manually re-enter everything already written on their CV.

You are entering their world, not the other way around, so the objective at the beginning is not to convince them to leave their employer or sell them on everything your organisation has to offer. It is simply to give them enough of a reason to have a conversation with you.

Start warmer than you think

When a difficult search starts, recruiters often head straight to LinkedIn while sitting on years of potentially useful candidates in their ATS.

Before looking for someone completely new, go back to the people who have already had some contact with your organisation. Look at who applied, who interviewed, who reached the final stages and, more importantly, why they were not hired.

There is a big difference between somebody who was rejected because they could not do the job and somebody who missed out because the role was put on hold, the budget disappeared, an internal candidate appeared, another candidate was marginally stronger, or the timing did not work.

Sometimes somebody was the second-best candidate in a process where only one person could get the job. Six months later, that same person may still be an excellent candidate, yet we often start again from scratch as though everybody we previously rejected has somehow become permanently unsuitable.

Your ATS should be a place you recruit from, not simply somewhere old applications go to die.

Make the outreach feel deliberate

Once you start approaching people you do not know, make it obvious that you looked at their profile and understood something about their background.

That does not require a long message explaining your company history, mission, values, growth plans, leadership team and how exciting the opportunity supposedly is. It requires enough specific information for the person receiving it to understand why you contacted them.

Mention the experience, project, industry, move or part of their background that caught your attention. If your message tells the candidate nothing about why you picked them, it will sound exactly like something you sent to another 50 people at the same time.

For difficult searches, I would rather contact 20 people, one by one, than 200 people badly.

A normal LinkedIn connection request can sometimes feel more natural than immediately sending an InMail, but the format matters less than the content. The purpose of that first message is not to convince somebody to change jobs before they have even spoken to you; it is to make them curious enough to reply.

Do not outsource the conversation to the job description

One of the most common replies to recruiter outreach is:

“Can you send me the job description?”

That is usually a good sign. They are interested enough to want more information.

The temptation is to reply with the document and leave it there, but you have then handed the next part of the conversation to a job description, which is rarely the most compelling ambassador for a role.

I would rather say something like:

Happy to send it over. Would you have 15 minutes first? I can give you some context around the role and you can decide from there whether it is worth exploring.

A job description can explain responsibilities and requirements, but it rarely explains why the role exists, what is happening in the team, what the manager is like, what could make the job interesting, what might change over the next year, or what could make the move worthwhile for this particular person.

That is the recruiter's job.

The first call is a conversation, not an interview

If you contacted someone who was not looking for a job, opening the conversation with “tell me about yourself” is slightly odd.

You already looked at their background. That is supposedly why you contacted them.

I prefer to start with something more natural, such as:

“Had you heard of us before I contacted you?”

If they have, ask what they know. If they have not, you have an easy opening to explain who the organisation is, what it does and why you thought their background might be relevant.

It also gives you a useful glimpse of your employer brand from the outside. You get to hear what people know about the organisation, what they associate with it, whether they have heard anything at all, and occasionally whether what they think they know is completely wrong.

From there, the conversation should be about understanding what could make a move interesting enough to consider, rather than forcing somebody who is not job hunting through the same script you would use with an applicant.

I am not a big fan of asking passive candidates:

“What are you looking for in your next opportunity?”

They may not be looking for one.

A much more useful question is:

“What would have to come along for you to consider making a move?”

The answer tends to tell you much more about the conditions under which they would move, which is what you need to understand.

Understand the objection before accepting it

Passive candidates will often tell you that they are happy where they are, and that may be the end of it. But before assuming it is, it is worth understanding what “happy” means.


Is it the manager, the flexibility, the salary, the work, the location, the progression, the team, or the fact that changing jobs sounds like unnecessary hassle right now?

Sometimes there is nothing your opportunity can offer that would make moving attractive, and there is no point trying to manufacture a reason. But sometimes the first objection is just the first thing that came to mind.

If salary comes up immediately, for example, I might ask:

“Let’s put salary aside for a minute. What else would have to be different for you to seriously consider moving?”

The purpose is not to talk somebody into leaving a job they like. It is to understand what matters to them well enough to know whether there is anything worth discussing.

If there is not, you can both move on.

One conversation can still lead somewhere

A conversation with a passive candidate does not have to end in an application to have been useful.

The timing may be wrong, the role may be wrong, or the person may simply have no interest in moving. But if the conversation was good and they leave with a positive impression of you and the organisation, ask whether they know somebody else who might be more open to it.

“Is there anybody you know who might be more interested in this than you are?”

Particularly in specialist industries, people know who is good, who might be open to a move and who has the experience you are struggling to find.

Cold outreach does not always lead directly to the candidate you hire. Sometimes it leads to someone who introduces you to them.

Passive does not mean interested

The mistake with passive candidates is treating them as though they are already candidates.

They are not, at least not yet.

They did not apply, they did not ask to hear about your company, and they do not owe you enthusiasm because you have decided the role is a good fit.

Your job at the beginning is much simpler: give them a good enough reason to talk to you, and find out whether there is anything worth continuing from there.

Comments


bottom of page