You can consider hiring a candidate who failed a skills test, but a strong interview alone is not a reason to disregard the result. First establish what the test measured, whether the failed skill is essential to the job, and whether the attempt produced usable evidence. Then apply the same decision standard to comparable candidates.
Identify the skill behind the score
A total score can hide very different problems. A developer who missed a syntax question is not necessarily in the same position as one who could not explain or debug the code the role requires. Review the actual tasks and mistakes rather than treating every below-cutoff score as interchangeable.
Separate requirements into two groups:
- Needed on day one: capabilities the person must demonstrate before taking responsibility for the work.
- Trainable after joining: gaps the team can realistically address with supervision, time, and a defined training plan.
If the assessment demonstrates a gap in an essential skill, an appealing interview does not establish that the candidate can perform the work. Consider another suitable role or end the process according to your criteria.
Check whether the attempt was interpretable
Confirm that the instructions, time limit, tools, and assessment format matched what you intended to measure. A platform outage or an unresolved access issue calls for a different response from a completed attempt that showed an inability to perform a core task.
When an attempt was materially disrupted, follow a consistent retest process. Do not keep offering attempts only until a preferred candidate gets a passing score. Also distinguish a skills result from an integrity concern: a low score is not evidence of cheating.
Get follow-up evidence using the same rubric
For an ambiguous result, a short, job-relevant work sample or structured follow-up can help. Ask the candidate to explain their approach, identify an error, or complete a representative task. Score the evidence against criteria established for the role, rather than changing the standard to justify your first impression.
TestDome's discussion of failed skills assessments recommends reviewing which questions were missed and following up on the mistakes. TestGenius discusses the same hiring dilemma, emphasizing consistent standards when employers reconsider a cutoff.
Make and document the decision
Record the requirement, what the test showed, any follow-up evidence, and the reason for proceeding or declining. If a gap is trainable, name who will provide support and what successful progress will look like. If the test itself needs revision, make that a process change for comparable applicants, not a private exception.
For hiring teams comparing these signals at scale, AI candidate evaluation supports role-specific assessments, structured interviews, transparent scoring, and ranked shortlists. The team's job is still to define the requirements and review the evidence.
Bottom line: hire when the combined evidence demonstrates the required capability or a realistic, supported path to a trainable skill. Do not substitute interview likability for evidence of an essential skill.