In many recruitment processes, everyone believes they are aligned at the beginning.

The job description is approved. The requirements are written down. The recruiter understands the role. The hiring manager confirms the profile. The process starts.

And yet, a few days or weeks later, the same sentence appears:

“This candidate is good, but not quite what we’re looking for.”

This is one of the most common sources of frustration in recruitment. Not because anyone is acting in bad faith, and not because recruiters are sending random profiles. More often, the problem is simpler and harder to fix: the recruiter and the hiring manager are using the same words, but attaching different meanings to them.

“Good” often means different things to different people

A recruiter may look at a candidate and see relevant experience, matching skills, a clear career path, and a realistic salary range. From that perspective, the candidate is strong enough to move forward.

A hiring manager may look at the same profile and focus on something else entirely: the specific type of projects the candidate has worked on, the maturity of previous environments, the scale of responsibility, or whether the person would fit the way the team actually operates.

Both perspectives can be valid. The issue is that they are not always made explicit early enough.

This is why “good candidate” is such a dangerous phrase. It sounds clear, but it often hides a lot of assumptions. Good on paper? Good technically? Good for the team? Good for this moment in the company? Good enough to interview, or good enough to hire?

Unless those differences are discussed, they usually show up later - when candidates have already been sourced, contacted, screened, and submitted.

The job description is not the same as the real need

One of the biggest reasons for misalignment is the gap between the job description and the actual hiring need.

Job descriptions often describe a role in broad, polished language. They list required skills, responsibilities, qualifications, and experience levels. They are useful, but they are rarely enough to fully explain what the hiring manager truly needs.

The real need is often more contextual.

Maybe the team does not simply need a “senior developer.” It needs someone who can work independently because the manager has limited time for onboarding. Maybe the company does not simply need a “marketing manager.” It needs someone who has already built demand generation in a low-budget environment. Maybe the role is not just about knowledge of a tool, but about having worked in a specific level of chaos, growth, structure, or ambiguity.

These details rarely fit neatly into a job description, but they often decide whether a candidate is considered right or wrong.

Misalignment creates hidden delays

When the definition of a good candidate is unclear, the process slows down in ways that are easy to misdiagnose.

The recruiter sends candidates who appear to match the brief. The hiring manager rejects them with feedback that feels vague. The recruiter adjusts the search based on that feedback, but the target keeps shifting. More candidates are reviewed. More calls are made. More time passes.

From the outside, this may look like a sourcing problem.

In reality, it is often an alignment problem.

The team is not struggling because there are no candidates. It is struggling because the definition of relevance is still being negotiated during the process.

That is expensive. It costs time, candidate attention, and recruiter energy. It also creates frustration on both sides. Recruiters feel that the hiring manager “doesn’t know what they want.” Hiring managers feel that the recruiter “doesn’t understand the role.”

Often, both are partly right.

Calibration should happen before sourcing

One of the simplest ways to reduce this friction is to treat calibration as a real stage of the recruitment process, not a quick conversation before the search begins.

A good intake meeting should go beyond reviewing the job description. It should explore what success in the role looks like, what trade-offs are acceptable, which requirements are truly non-negotiable, and which are only desirable. It should also include examples.

Instead of asking only, “What skills are required?”, it is more useful to ask:

“What would make you excited to interview someone?” “What would make you reject a candidate despite matching the formal requirements?” “What kind of previous environment would prepare someone well for this role?” “What trade-offs are we willing to make if the perfect candidate does not exist?”

These questions reveal the hidden criteria that often drive decisions later.

Feedback needs to be specific enough to improve the search

Even with good calibration, some adjustment during the process is normal. Hiring is rarely perfect from the first shortlist. But feedback determines whether the search improves or simply repeats itself.

“There was no fit” is not feedback. “Too junior” is only partly useful. “Not strategic enough” may be true, but it needs explanation.

Useful feedback explains what was missing and why it matters.

For example: “The candidate has marketing experience, but most of it is executional. We need someone who has owned campaign strategy and budget decisions, because this person will work without a senior marketing lead above them.”

That kind of feedback changes the next search.

It gives the recruiter a sharper lens. It reduces guesswork. It turns a rejection into learning.

A good candidate is not universal

Another source of friction is the assumption that a strong candidate is strong in every context.

They are not.

A candidate can be excellent in a structured corporate environment and struggle in an early-stage company where processes are still being built. Someone can be very strong technically but not ready for a client-facing role. Another person can have the right skills but not the right level of independence for a team with limited managerial support.

That is why recruitment is not just about matching skills to requirements. It is about matching people to context.

This is also why hiring managers often notice things that do not appear in the CV. They imagine the candidate inside the team, inside the workflow, inside the pressure of the role. Recruiters can do this too, but only when they have enough context.

The role of the recruiter is changing

In this environment, recruiters are not only talent finders. They are translators.

They translate business needs into search criteria. They translate candidate experience into relevance. They translate hiring manager feedback into better decisions. And increasingly, they help prevent vague expectations from turning into slow processes.

This requires more than sourcing ability. It requires structured communication, strong intake discipline, and the confidence to challenge unclear requirements early.

Sometimes the most valuable thing a recruiter can say is not “I’ll find more candidates.”

It is: “Before we continue, we need to define what ‘good’ really means.”

Better alignment creates better speed

Many hiring teams try to improve recruitment speed by reducing stages or increasing sourcing activity. Both can help, but neither solves the problem if the team is not aligned on what it is looking for.

When the definition of a good candidate is clear, the process moves faster. Shortlists are more relevant. Feedback is sharper. Hiring managers trust recommendations more. Candidates receive clearer communication. Recruiters spend less time chasing a moving target.

The process does not become faster because people rush.

It becomes faster because fewer decisions need to be corrected later.

The real question

The next time a hiring manager says, “This candidate is good, but not quite right,” it is worth pausing.

Not to assign blame, but to ask a better question:

What did we fail to define earlier?

Because in recruitment, “good candidate” is not a fixed category. It is a shared definition that needs to be built before the search begins.

And the teams that do this well will not only hire faster.

They will hire with far less friction.