Keystroke Event Capture That Spot the Swap

Q: Does keystroke event capture log what candidates type?

The event capture model needs timing data — dwell, flight, and key-pair transitions — not content. Content and timing are handled with separate retention policies; analysis can work on timing metadata alone.

Q: How long does it take to establish a baseline?

About 60 seconds of natural typing. Shorter for simple short-form questions; longer for extensive code editing. Analysis is disabled until a reliable baseline is established.

Q: What if the candidate is a slow typist or types unusually?

The baseline is personalized — the analysis models that specific candidate's pattern, not an average typist. Slow, fast, one-finger, or unusual rhythm all work as long as the session is consistent.

Q: Can keystroke event capture catch AI-generated typing?

Kind of — paste events are a separate signal, and LLM-assisted candidates often paste large chunks, triggering the paste detector. Direct AI-driven typing (simulating a human) is harder but shows up as unusual timing patterns.

Q: Is keystroke event capture compliant with privacy laws?

ClarityHire captures keystroke events, not biometric identifiers. Clear consent, configurable retention, and deletion workflows are built in to align with GDPR and similar privacy regulations.

ClarityHire captures keystroke timing and detects sudden style changes and paste events in the first minutes — then flags when a different person may take over the keyboard. Invisible, continuous, and transparent.

Start Free Trial See Pricing

Event capture

Keystroke analysis method

< 60s

To establish baseline

Continuous

Monitoring throughout

Invisible

To the candidate

Typing patterns and paste events reveal cheating

ClarityHire captures keystroke events for replay and paste/burst detection, not biometric fingerprinting.

Keystroke timing capture

Records keystroke timing features — dwell times, flight times, and pauses — for analysis and replay.

Dwell and flight timing

Millisecond-accurate measurements of key-down, key-up, and inter-key transitions.

Baseline profiling

First 60 seconds establish a typing-pattern baseline — used to detect sudden style changes.

Continuous event capture

Every subsequent keystroke's timing is recorded. Abrupt changes in pattern trigger alerts.

Paste event detection

Distinguishes typed content from clipboard pastes — paste events are separate signals.

Per-signal integrity score

Keystroke confidence folds into the unified authenticity score with timestamps and replay.

Event-based storage

Keystroke timing events stored for replay; actual content is separated and retention-controlled.

Browser-native

Works via keyboard events in any modern browser. Zero install, zero extension.

Audit trail

Every timing anomaly timestamped with confidence score — exportable for review.

Built for how modern teams hire

The science

Everyone types differently

Dwell times (how long you hold a key) and flight times (how quickly you move between keys) are as distinctive as handwriting. After 60 seconds of typing, ClarityHire has a signature — and it does not match anyone else's.

Dwell time distributions per key
Flight time distributions per transition
N-gram pattern analysis

Catch the swap

When someone else takes over, typing rhythm changes

Proxy test-takers and mid-session swaps change typing rhythm noticeably. The classifier catches the shift and timestamps the event for review.

Continuous scoring against baseline
Alert threshold configurable per role
Timeline shows the exact moment of change

Privacy-aware

Timing events, not content logging

Keystroke event capture records timing, not content. Metadata (dwell, flight, transitions) is stored for integrity scoring — actual typed content is stored separately with its own retention policy.

Timing metadata separated from typed content
Configurable retention per data type
Candidate consent and audit log included

How it works

Candidate starts typing

First 60 seconds capture the pattern baseline — dwell, flight, and pause distributions.

Pattern analysis begins

Baseline loaded. Every keystroke now analyzed against the established pattern.

Style changes flagged live

Sudden timing anomalies detected. Alerts fire to the interviewer dashboard immediately.

Review with evidence

Integrity report shows exact timestamps of pattern changes with confidence scoring.

Frequently asked questions

Does keystroke event capture log what candidates type?+

The event capture model needs timing data — dwell, flight, and key-pair transitions — not content. Content and timing are handled with separate retention policies; analysis can work on timing metadata alone.

How long does it take to establish a baseline?+

About 60 seconds of natural typing. Shorter for simple short-form questions; longer for extensive code editing. Analysis is disabled until a reliable baseline is established.

What if the candidate is a slow typist or types unusually?+

The baseline is personalized — the analysis models that specific candidate's pattern, not an average typist. Slow, fast, one-finger, or unusual rhythm all work as long as the session is consistent.

Can keystroke event capture catch AI-generated typing?+

Kind of — paste events are a separate signal, and LLM-assisted candidates often paste large chunks, triggering the paste detector. Direct AI-driven typing (simulating a human) is harder but shows up as unusual timing patterns.

Is keystroke event capture compliant with privacy laws?+