How to Verify Candidate Identity in an Online Interview Without Being Creepy
The actual threat model
Three failure modes happen at non-zero rates in remote hiring:
- Impersonation. A different person sits in the interview chair than the one who applied.
- Coaching. The candidate is real, but a second person off-camera is feeding them answers.
- Asynchronous fraud. Someone else completes a take-home or async assessment.
Identity verification addresses (1) and partially (3). Coaching needs different controls.
The minimum-invasive approach that works
At application
Government ID is overkill at this stage and creates real candidate friction. Skip.
Before the first technical round
Ask the candidate to confirm a few simple facts you can match against later: full name as it should appear on offer, current employer (if applicable), the email they used to apply. Capture, don't verify.
At the first video interview
Camera on. The interviewer sees the candidate and verbally confirms "you're [name], correct?" That's the human-eyeball check. Almost all impersonation fails here because the impersonator isn't going to fool a 30-minute live conversation.
Across rounds
Use the same video interview for visual continuity. If round 1's candidate looks substantively different from round 3's, the recruiter follows up. ClarityHire captures interview video with retention controls and surfaces a face-continuity signal across a candidate's interview rounds — flagging the 2% of cases where the across-round person doesn't match without performing intrusive biometric matching against external databases.
At offer stage
Now do the formal identity verification. Government ID, right-to-work documents, the works. The candidate has agreed to be hired, the friction is appropriate, and the verification is binding.
What "creepy" looks like (and why teams default to it)
- Live face-recognition scoring during interviews
- Continuous webcam recording with no clear retention or use policy
- Government ID required to apply
- Background checks before the first interview
- Browser lockdown or invasive proctoring software for short assessments
Teams reach for these because vendors sell them. They are appropriate for high-stakes certification exams. They are not appropriate for hiring funnels — they filter out candidates who object on principle, who have privacy regulations, or who simply have a less-photogenic camera setup.
The async assessment piece
For take-homes and async assessments, identity verification is partial:
- Capture metadata that correlates with identity continuity (keystroke timing patterns are remarkably individual; ClarityHire uses this as a signal across rounds).
- Pair every take-home with a live walk-through. A candidate who cannot explain their own submission did not write it. This catches almost all asynchronous fraud without any verification ceremony.
What to communicate to candidates
A short, clear paragraph in the application or interview invite: what verification you do, when, and why. Candidates appreciate transparency far more than they object to reasonable verification. The objection threshold is low when the rationale is honest and the friction is appropriate to the stage.
The summary
Light identity check upfront. Camera-on first interview. Visual continuity across rounds. Walk-through for async work. Formal ID at offer. That's the whole protocol — and it catches the actual threats without alienating real candidates.