Before 2020, identity verification in hiring was largely handled by physical presence. You showed your passport or driver's license on your first day. An I-9 officer looked at the document, looked at your face, and checked the box. The verification was imperfect — experienced document fraud is difficult to detect under a two-second visual inspection — but it was at least synchronous with the person being evaluated.
Remote hiring eliminated that touchpoint entirely. A company can now extend an offer to a candidate they have interacted with exclusively through video calls, digital assessments, and email — and have no mechanism for confirming that the person who accepted the offer is the same person who will show up in their system on day one. This is not a hypothetical edge case. Credential fraud, identity substitution, and proxy interviews — where someone other than the candidate completes technical assessments — are documented patterns in remote hiring pipelines, particularly for high-demand engineering roles.
Identity verification for remote hiring is the practice of filling the gap that physical presence used to fill. Here is how the technology works and what the operational realities look like in practice.
The Two Layers of Remote IDV
Modern identity verification in hiring contexts typically involves two distinct processes: document verification and liveness detection. These two layers serve different purposes and address different fraud vectors, and a complete IDV solution requires both.
Document verification confirms that the identity document a candidate presents is genuine and consistent with the information they provided. At the technical level, this involves optical character recognition (OCR) to extract data from the document — name, date of birth, document number, expiration date — and comparison of that extracted data against the information the candidate submitted in their application. For machine-readable travel documents like passports, this includes parsing the Machine-Readable Zone (MRZ) — the two lines of standardized text at the bottom of the photo page — and checking for internal consistency between the MRZ data and the visual inspection zone. A document where the MRZ-encoded name does not match the visually printed name is an immediate flag. Driver's license verification includes similar OCR and format validation against the expected layout and security features for the issuing jurisdiction.
Document verification catches presented documents that are malformed, expired, or internally inconsistent. It does not, on its own, confirm that the person presenting the document is the person depicted in it. That is where liveness detection comes in.
Liveness detection confirms that the candidate completing the verification is a live person physically present at the verification moment, and that their biometric data (typically a facial image) matches the document photo. Passive liveness detection analyzes the video stream or photo sequence for characteristics that distinguish a live person from a photograph, a mask, or a deepfake injection — depth cues, micro-expression patterns, texture inconsistencies. Active liveness detection asks the candidate to perform a specific action (turn head, blink, look up) and confirms the response in real time. Enterprise-grade solutions typically layer both passive and active mechanisms.
The combination — document verification confirming the document is legitimate, liveness detection confirming the person presenting is the document holder — produces a meaningful identity assurance level that is substantially stronger than what most visual I-9 checks provide.
When in the Hiring Loop to Run IDV
Timing matters operationally and from a candidate experience standpoint. Running a full IDV check at the initial application stage creates unnecessary friction and raises privacy concerns for candidates who have not yet progressed through a competitive process. Running it only at onboarding closes the loop too late — by that point, an offer has been extended, a start date is set, and a background check vendor has been engaged.
The typical pattern for early-stage hiring teams that have thought through this carefully is to run IDV at the offer stage, after a verbal offer is accepted but before the written offer letter is executed. At this point the candidate has already cleared the full interview loop, so the friction of the check is landing on a population that is already committed and motivated to complete it. The result of the IDV check feeds the background screening workflow — verifying that the individual being offered the position matches the employment verification (VOE) documents and reference check targets from earlier in the process.
For roles where proxy interview risk is elevated — typically senior engineering, security, or finance roles with high compensation — some teams are running liveness detection earlier, at the final technical round, by requiring candidates to complete a brief biometric confirmation before their interview session begins. This approach requires careful communication to candidates and clear documentation of what data is captured, how it is stored, and when it is deleted.
A Scenario: Remote Engineering Hiring at a Growing Healthcare Technology Company
Consider a remote-first healthcare technology company with 90 employees that opened five senior engineer positions in mid-2024 after closing a growth round. Their interview loop was entirely asynchronous for the first two stages — a technical assessment and a system design submission — followed by three live video rounds. They had received a growing number of applications from candidates whose technical assessment performance was significantly higher than their live interview performance: articulate, specific answers on the assessment, vague and uncertain in real-time technical discussion.
The pattern was consistent enough that their head of engineering flagged it. They could not confirm whether these were cases of assessment proxy use, but the discrepancy was unexplained. After implementing a liveness check tied to their technical assessment platform — requiring candidates to confirm their identity before the timed assessment window opened — the pattern attenuated noticeably in subsequent loops. Whether because the check deterred proxy use or simply because the added friction changed the candidate pool, the correlation between assessment performance and live interview performance improved measurably.
This is a plausible, realistic scenario — not a guaranteed outcome. IDV does not eliminate fraud. It raises the cost of fraud and creates an evidentiary trail that supports downstream review.
The Privacy and Data Handling Dimension
We are not suggesting that IDV checks are friction-free or without legitimate privacy concerns. Biometric data — facial images, liveness video — is sensitive data. Candidates in many jurisdictions have specific rights regarding biometric collection, and organizations collecting this data incur corresponding obligations. States like Illinois, Texas, and Washington have biometric privacy statutes (BIPA and its counterparts) that impose notice, consent, and retention limitations on biometric data collection.
A responsible IDV program documents exactly what data is collected, stores it with appropriate access controls, applies defined retention and deletion schedules, and obtains informed consent from candidates before the check begins. The consent language should be specific: it should describe what biometric data is collected, how it is processed, whether it is shared with third-party processing services, and how long it is retained. "We may collect personal information" is not adequate notice for biometric collection.
A well-designed IDV integration deletes biometric match data — the facial comparison result — after the verification window closes and retains only the decision outcome (verified / not verified) and a de-identified audit record for compliance purposes. The underlying facial image should not be retained as a searchable asset.
IDV and the I-9 Requirement
Remote IDV for hiring screening is separate from the Form I-9 Employment Eligibility Verification process, which has its own authorized document list and authorized verification procedures. Organizations conducting remote I-9 verification as part of onboarding must follow the current USCIS remote examination procedures, which as of 2024 include authorized alternative procedures for enrolled E-Verify employers.
The IDV check at offer/pre-offer stage is not a substitute for I-9 compliance. It addresses a different question — is this the person who interviewed? — not the work authorization question that I-9 addresses. Hiring teams should ensure their IDV workflow is clearly positioned as a hiring security measure and does not create confusion with or substitute for the I-9 process.
The practical integration is that a successful IDV check at offer stage reduces the friction at I-9 completion, because the identity document you collected during IDV may align with documents the candidate presents for I-9 purposes — but the I-9 still requires its own list A or list B+C document inspection, and no pre-onboarding IDV check satisfies that requirement on its own.
