Every Failed Hiring Search Has an Origin Story

The quest begins before anyone leaves the village

Before Talent Acquisition starts looking for candidates, there is usually a conversation with the hiring manager to define the role, clarify what is needed, and agree on what the search should look like.

Recruiters often call this the intake meeting or job qualification.

It sounds like a fairly ordinary first step, but this is where assumptions turn into requirements, preferences become selection criteria, and vague ideas somehow make their way into job descriptions without anyone necessarily noticing.

A surprising number of recruitment problems that appear much later can be traced back to this conversation.

“We’re not seeing the right people.”

“The candidates are too junior.”

“They don’t have enough industry experience.”

“I liked them, but something is missing.”

“Can we see a few more?”

Sometimes the search is difficult, sometimes the market is tight, sometimes the recruiter has missed the mark, and sometimes nobody defined the mark properly in the first place.

Someone has to read the map

Talent Acquisition should never treat this conversation like an order-taking counter. The hiring manager owns the hiring decision, absolutely, but Talent Acquisition should drive the conversation that helps them get there.

Most hiring managers are experts in their own field, not in recruitment, because hiring may only take up a small part of their year, yet when a vacancy appears, we suddenly expect them to define the role, understand the talent market, separate requirements from personal preferences, assess future potential, decide what can be learned on the job, and predict what kind of person will work well with the team, often while another meeting is starting in 8 minutes.

The purpose of this first conversation is not only to collect information, but to help the manager think through what they are asking for: why the role exists, why it is needed now, what problem this person is expected to solve, what needs to be there on Day 1, what can be learned after joining, and what success should look like twelve months from now.

And perhaps one of the most useful questions of all is this:

What would make you reject someone who otherwise looked strong?

If nobody can explain what would make them say no, there is a fair chance they have not agreed on what would make them say yes either.

Every quest gets a little more impossible

Requirements tend to expand when nobody challenges them. 5 years becomes 7, industry experience suddenly becomes mandatory, a qualification nobody has mentioned for years appears on the list, and someone remembers that the previous employee knew a particular piece of software, so now every candidate apparently needs that too.

The list gets longer, but very few people stop to ask whether the job itself has become more demanding, or whether everyone is simply trying to remove as much risk as possible from the decision.

Hiring managers also tend to fall back on what they know: their own career path, the person who previously held the role, the strongest employee on the team, or someone they worked with 10 years ago who was brilliant, and before long, one real person has become the blueprint for an imaginary candidate who may not exist.

Then comes the fear of dragons

That usually comes from pressure rather than bad intent. A vacancy may already be causing problems for the team, a previous hire may have gone badly, work may be piling up, and the manager may be very aware that if they get this wrong, they will be the one living with the consequences.

Hiring carries risk, and when people become nervous about risk, they start looking for certainty through more experience, more interviews, more references, more people involved in the decision, and more evidence.

Recruitment cannot give anyone complete certainty.

We are trying to predict how a human being will perform in a future environment using CVs, conversations, assessments, references and judgement, and while some methods are more useful than others, none of them can tell us exactly what will happen after someone joins.

This is where the guide earns their keep

Talent Acquisition should bring some distance and perspective, not by telling the hiring manager they are wrong, but by asking whether 12 years of experience are necessary, whether industry experience matters because the person needs immediate pattern recognition or because it feels safer, whether one of the technical requirements could be learned in 3 months, whether the salary matches the person being described, and whether the timeline matches the amount of time the manager is prepared to dedicate to the process.

There also needs to be a conversation about compromise, because most hiring decisions involve some kind of trade-off and the perfect candidate described at the beginning of the process often does no