True technical signal. Zero surveillance invasion. with people in the loop.
No webcam, no biometrics — just consistent timed conditions and an event log a human reviewer reads before anyone makes a call.
Candidate session · integrity log
Session started
Tab focus lost
12s
Tab focus regained
Copy attempt blocked
Session submitted
Recorded automatically · visible to the candidate when it happens · included in the audit trail, not used to auto-fail.
The integrity log recorded during a candidate's session. Sample content shown.
Fair conditions, honestly recorded
Same conditions for everyone
Every candidate runs on the same timer, so a score reflects the work — not who had more time.
Quietly recorded
Session integrity signals — copy-paste and tab-focus events — are logged in the background, visible to the candidate as they happen.
A person decides
Irregularities are flagged for a reviewer. Nothing about a candidate is decided automatically.
Assessment · in progress
This session is timed and monitored for integrity.
System Design · Q2 of 4
18:05Your service's read latency degrades under peak load. What data-modeling changes would you consider, and what would you trade off?
Your answer
Saved as you go · graded against your rubric after you submit
Nothing secret, nothing invasive
Integrity here is about consistent conditions, not surveillance. There's no webcam and no biometric check — just a timer, a secure session, and a plain record of copy-paste and tab-focus events that the candidate can see as they happen.
What runs in the background
Three integrity signals run on every assessment. They keep conditions consistent and the record honest — and that's all they do.
Timed sessions
A per-assessment timer runs the same way for every candidate, so results are produced under the same clock.
Secure session token
Each attempt is tied to a session token, so the run is scoped to the candidate it was issued to.
Copy-paste & tab-focus guards
Copy attempts and tab-focus changes are guarded and logged as events — not to punish, but to keep the record honest.
How it works
The session opens
The candidate starts the assessment. A secure session token and the timer are set for this attempt.
Events are logged as they happen
Copy-paste attempts and tab-focus changes are recorded to a chronological integrity log — and shown to the candidate.
A reviewer reads the context
The log is context for a human reviewer alongside the result. It informs a decision; it never makes one.
One number, for a reviewer to weigh — not to decide
The event log rolls up into a single integrity signal a reviewer can scan alongside the result. It's context for their judgment, not a verdict on the candidate.
Session summary · reviewer view
Integrity signal
for reviewer context — not a pass or fail result
Derived from this session's log
A person reviews this signal alongside the candidate's result — it informs their judgment, it doesn't replace it.
A person always makes the call
Assessment Integrity flags irregularities for review — it doesn't auto-fail or auto-disqualify a candidate. A person always makes the call.
No webcam, no biometrics
Integrity is a timer, a secure session token, and copy-paste / tab-focus event logging — nothing watches the candidate through a camera.
Visible and auditable
Events are shown to the candidate when they happen and kept in the audit trail — not used to auto-fail anyone.
Context, not a verdict
The log is input to a human reviewer's judgment. The decision about a candidate stays with your team.
Ready to verify genuine engineering craft without violating candidate trust?
See how Assessment Integrity keeps conditions fair and consistent for every candidate — no webcam, no biometrics — and leaves a human reviewer the record to make the call.