Articles
HackerRank Identity Verification Guide: Candidate ID, Webcam Checks, and Privacy
Separate HackerRank webcam Photo Identification from document requests, check camera setup, and understand manual review and test-specific privacy details.
A HackerRank webcam identity check does not automatically mean a government-ID scan or continuous video proctoring. HackerRank's Photo Identification feature takes a candidate photo before the test for the hiring team to review manually. It is disabled by default, and enabling it does not add automatic identity validation or photo-based flagging.
Check the exact prompt on your invitation and pre-start screen.
Three prompts that need different responses
| What the prompt asks for | Appropriate response | Do not infer |
|---|---|---|
| A candidate or application identifier | Use the reference requested by that invitation; ask recruiting if the field is unclear | That an ID number means a passport scan |
| Photo Identification | Complete the displayed webcam-photo step | That the photo is automatically matched against a government database |
| Additional identity documents or monitoring consent | Read that specific flow and its privacy notice; clarify accepted documents with the owner | A universal HackerRank document list or retention period |
“Candidate ID” is ambiguous without the actual form. This guide does not claim that every HackerRank test has a field with that name. A request to identify an application and a request to photograph a person are different tasks.
Set up the camera before the timer starts
Open the legitimate invitation on the device you will use. Check the camera preview, allow camera access for the assessment site, and close another app if it is already using the camera. If the preview stays black, inspect both the browser's site permission and the operating system's camera permission. Make these changes before starting the timed attempt whenever possible.
Use clear lighting and follow the framing instructions. Photo Identification alone does not justify holding a passport up to the camera. If another step explicitly requests a document, use that official step and its accepted-document instructions; do not send an unsolicited copy through email.
The HackerRank integrity overview describes different test modes and configurable controls. A browser that works for a basic test may not satisfy a particular desktop-app or secure-mode requirement. Use your invitation's setup check rather than a blanket “all browsers work” list.
Who can review the photo?
For Photo Identification, the official documentation places the candidate photo in the summary report for manual hiring-team review. This differs from CodeSignal's separately documented handling of its proctoring data; do not transfer another provider's privacy promises to HackerRank.
The Photo Identification page does not establish one retention period for every customer's assessment. To resolve a privacy concern, ask about the named feature, who receives its data, how long it is retained, and the appropriate deletion or access-request channel. The HackerRank privacy policy is a starting point, alongside the notice shown by the hiring company.
If the check blocks you
Contact recruiting before the deadline if the camera is unavailable, the invitation name needs correcting, or you need an accommodation. Describe the problem without attaching identity documents in the first message:
The HackerRank pre-start screen requests [exact feature]. I cannot complete it because [camera/access/name issue]. The deadline is [time and timezone], and the test timer [has / has not] started. Which approved setup or accommodation should I use?
For a technical problem, keep the exact error, browser/OS version, time, and whether the timer started. Use HackerRank's candidate support route for platform troubleshooting and recruiting for deadline or accommodation decisions.
After the check succeeds, follow the test's displayed monitoring rules.
Sources and Further Reading
Documentation checked: September 6, 2026.