How to Evaluate Job Candidates Who Don’t Check Every Box

Share it

Most hiring teams start a search with an idea of their perfect candidate.

They outline the experience they should have, the skills they need, the technologies they should know, and the background that would make them a strong fit.

Then they start meeting candidates, and the reality is rarely that simple. Rather than being a perfect fit, they might meet 70% or 80% of what the team originally asked for.

This doesn’t necessarily make them underqualified and shouldn’t rule them out of consideration for the role. In many cases, knowing how to evaluate job candidates effectively means looking beyond how closely a resume matches the original job description and understanding what someone actually needs to succeed in the role.

Very few candidates will match every detail of a job description. What matters more is understanding which requirements are essential to doing the job well and which skills or experiences can be learned along the way.

The difference can be easy to overlook, especially when you’re comparing candidates against a long list of requirements.

Here’s how to tell the difference.

Start With the Capabilities the Role Needs

Before you focus on what a candidate is missing, go back to what exactly you need them to do in the day-to-day of the job.

Job descriptions often use qualifications as shorthand for capability. You might ask for 10 years of project management experience when what you really need is someone who can lead a complex program, manage executive stakeholders, navigate competing priorities, and keep work organized through uncertain situations.

The capabilities are what you’re really hiring for. A candidate with seven years of experience may have already done all of them. Another candidate could have 12 years of experience without operating at the same level of complexity.

Look at the work this person will need to own in their first six to 12 months.

What problems will they need to solve? What decisions will they make? What level of responsibility will they have? What would they need to be able to do from day one?

Use those answers to identify the capabilities that are truly non-negotiable.

Decide What Can Be Learned

Once you’ve identified your must-haves, look at what’s left.

Some gaps are relatively easy to close, such as a new reporting tool, internal process, company terminology, or unfamiliar software platform. These are all things a strong candidate can typically pick up fairly quickly.

Other capabilities take much longer to develop. For example, if you’re hiring someone to lead a large technical team, years of experience managing people, priorities, and difficult decisions can’t necessarily be replaced by a few months of training.

Consider both the importance of the missing skill and how long it would realistically take to learn. Ask yourself:

How quickly could this person become proficient, and how soon do we need them to be?

A skill that you’ll need them to develop over their first three months is not as high a priority as a skill they’ll need during their first week.

Look for Transferable Experience

Candidates don’t always need to have done the exact job before to have relevant experience.

Someone coming from another highly regulated industry may already understand how to work within strict compliance requirements. Someone who has led a different type of transformation may have experience managing the same level of complexity, change, and stakeholder involvement your project requires.

Instead of only asking whether they’ve worked in your industry, used your technology, or held the same title before, look at their concrete experience and background.

What kinds of problems have they solved? How complex was the environment? Who did they work with? What were they responsible for delivering?

The details may look different, but the underlying experience is very similar.

Industry knowledge and specific technical experience still matter, but it’s important to understand why it matters for this particular role before making it a make-or-break requirement.

Separate Requirements From Preferences

Job descriptions tend to collect requirements over time, such as a particular degree, experience at a certain type of company, or even knowledge of a specific platform.

Some of those may be essential, but others may simply be “nice-to-haves”.

Before treating a missing qualification as a reason to pass, ask:

If an otherwise strong candidate didn’t have this, would we still consider hiring them?

If the answer is yes, it probably isn’t a true requirement.

It can help to divide your criteria into three groups:

Must-haves: Capabilities someone genuinely needs to succeed in the role.

Strong preferences: Experience that would be valuable or shorten the learning curve, but isn’t essential.

Nice-to-haves: Qualifications that could add value but shouldn’t determine whether someone moves forward.

Do this before you start interviewing. It’s much easier to evaluate candidates consistently when everyone agrees on which requirements are your top priority.

Know Which Gaps Create Real Risk

There are also times when the missing 30% should give you pause.

The candidate may need a particular technical skill immediately and doesn’t have an adjacent background to build from, or the role could require regulatory knowledge that would take significant time to develop.

Whatever the gap may be, take a moment to consider:

How important is this to the person’s day-to-day responsibilities?

How quickly could they realistically learn it?

Does the team have the capacity to help them develop?

What happens if they don’t become proficient as quickly as expected?

This helps identify the risks specific gaps can create, so you can make an informed decision. If those risks seem substantial, it may be time to move on to a new candidate.