What a candidate's response time on a test tells you

A candidate’s response time and latency are context signals, not verdicts. On their own they don’t tell you whether someone cheated or what their personality is like: they offer clues about how the test was taken, which may suggest looking at a case in more detail. Like every integrity signal, they support human review — they never disqualify automatically.

Response time and latency: what each one is

They’re two related but distinct signals, both part of the integrity checks during the test session:

• Response time: how long the candidate takes to answer each item on the test.
• Latency: the pattern or rhythm of those times across the evaluation — whether they’re even, whether there are jumps, whether they shift toward the end.

Together they describe how the test was taken, not who the person is. They don’t measure intelligence or traits: they give context about the answering process.

What this signal can suggest (and what it can’t)

A striking timing signal can be a good reason to look at a case in more detail. But it has important limits that need to be respected:

What it provides	What it does NOT do
Context about how the test was answered	Doesn’t prove cheating occurred
A clue for prioritizing reviews	Doesn’t determine anything on its own
A comparable signal across candidates	Doesn’t measure personality or ability
Input for human review	Doesn’t disqualify automatically

Why it’s never used in isolation

Making a decision based on response time alone would be a mistake. There are too many possible explanations for that signal to “speak” for itself. Its value appears when it’s combined with the rest of the picture: the test result, the other integrity signals, and above all the judgment of the person evaluating.

At Kokoro, response time and latency are recorded as part of the integrity controls and offered as additional context. They help organize which cases deserve a second look — but the decision always stays with the HR team.

How to use it well

The healthy way to use this signal is simple: treat it as a clue for prioritizing, not as a conclusion. If a candidate’s response time stands out, it’s worth reviewing that case alongside everything else before deciding. The technology provides the signal; the person provides the judgment.

In short

Response time and latency describe how a test was taken, not who the candidate is or whether they cheated. They’re context signals, useful for prioritizing which cases to review, but with no conclusive value on their own. Like every integrity control, they support human review and never disqualify automatically. See how it works or get to know the product.