Should I Interview a Candidate Who Is Missing One Requirement?

One applicant looks strong. They have handled the main work, but their resume misses one item from your job description. Interviewing them may waste time. Rejecting them may mean losing a capable person over something you could teach.

Should you interview them? First decide what kind of requirement is missing. A necessary licence is not the same as experience with your preferred software. “Five years” is not the same as evidence that someone can handle the work.

Put the missing item into one of three boxes

Use the actual job, not the importance implied by a long bullet list.

1. Required before the person can start: a lawful licence, clearance, language capability or technical skill that the job genuinely cannot be done without.
2. Needed soon but reasonably trainable: a system, process or product knowledge you can teach within a real amount of time.
3. Preferred rather than necessary: a familiar title, exact industry, particular software brand or extra years that would be convenient but is not essential.

If you cannot place the item, the job description needs work before the candidate can be judged fairly.

Ask whether it is missing or merely unstated

A resume is a short document. The candidate may lack the requirement, may have described the same work differently, or may simply have left the detail out.

Write down:

• the exact sentence in the job description;
• the evidence you expected to see;
• what the resume actually says;
• whether a short factual question could settle it.

Do not upgrade “not stated” to “does not have.” Do not downgrade a confirmed absence to “probably fine” because you like the rest of the resume.

A worked example: the software name is not the work

This is a hypothetical example, not a product test or a real applicant.

A small landscaping company needs a dispatcher. Its advertisement asks for two years using FieldPulse. Amari’s resume does not mention FieldPulse, but it says she scheduled twelve technicians, rearranged urgent visits, updated customers and checked that completed jobs reached invoicing.

The owner should ask why FieldPulse matters:

• If the company can teach its setup in the first week, the missing brand name is trainable.
• If the role starts tomorrow with no one available to train, prior use may carry more practical weight.
• If the real need is independent dispatch judgment, Amari’s examples may be more useful than the software label—but they still need checking.

An interview is reasonable if the underlying work is relevant and the business has an honest training plan. That does not guarantee Amari the job. It means the missing software name should not silently decide it.

Now change the fact: the job involves work that legally requires a current licence, and Amari confirms she does not hold it. That is not a preference the owner can casually waive.

Use the day-one test

The U.S. Office of Personnel Management’s job-analysis guidance distinguishes competencies needed on the first day from those employees are expected to learn through training. It says skills intended to be learned on the job should not become selection requirements in that federal context.

Your small business is not a federal hiring system, but the practical question travels well:

What goes wrong if the person starts without this item, and what would it take to close the gap?

Answer with specifics:

• Who would teach it?
• How many hours or weeks would learning take?
• What work would need supervision in the meantime?
• Is there a safety, legal or customer risk?
• Have you trained other employees in it?

“They are a fast learner” is not a training plan. “Nobody here has time to teach it” is useful information.

Apply the same answer to the whole pool

If you decide that the requirement is trainable, revise the criteria for every applicant—not only the person you already prefer. If it truly is a day-one requirement, record why and apply it consistently.

Do not invent a percentage rule such as “80% qualified.” One missing legal credential can matter more than five minor preferences. One missing software brand can matter less than clear evidence of the underlying work.

If everyone is failing the list, use the empty-shortlist diagnosis. If you need a fuller way to separate essential and preferred evidence, use the resume-screening rubric.

If an AI review rejects the candidate

Check the instruction and the source resume. Did the system treat every bullet in the job description as mandatory? Did it confuse an absent keyword with absent experience? Did it ignore comparable tools or transferable work?

Resume Ranker can help compare a batch using corrected criteria and cite the resume evidence behind each review. It cannot decide whether your business can realistically train someone. Make that choice first, rerun the whole affected pool consistently, then check the evidence yourself.

The interview decision becomes simpler once the requirement is honest: reject a confirmed, necessary gap; clarify missing evidence; or interview for the underlying work when the missing item can genuinely be taught.