Best Practices for Detecting Candidate Fraud in Remote Hiring: a 12-Step Checklist (2026)
By Sparsh Goyal, Founder at The Cognitive. Published ยท Last updated
- Detect candidate fraud in remote hiring with 12 checks run the same way for everyone, from profile continuity at sourcing to ID verification before the offer and identity checks after day one.
- One red flag rarely proves fraud: when several details conflict, pause the offer, write down exact observations and run the same verification step you use for everyone.
- In Checkr's 2026 survey of 3,000 US managers involved in hiring, 40% had interviewed a candidate later found to use a fake identity, so pair an ID check such as Greenhouse Real Talent or Alex with an interview that probes the work.
- The Cognitive's live AI interview flags integrity events, checks the recording for signs of a swapped video or a second voice and probes up to 5 resume claims, but it does not check a government ID.
Best practices for detecting candidate fraud in remote hiring come down to checking identity, work history and interview evidence the same way for every candidate, at every stage from sourcing to day one. Confirm identity before the final round and again on the first day. Ask ownership questions that need dates and tradeoffs. Log interview signals without auto-rejecting anyone, and pause any offer you can't document.
Candidate fraud is a person misrepresenting who they are or what they did in order to get hired, through a proxy interview, a deepfake, a fake or borrowed profile, an AI-inflated resume, a fake reference or an identity swap after the offer.
The problem is now measurable. In Checkr's 2026 survey of 3,000 US managers involved in hiring, 40% said they had personally interviewed a candidate later revealed to be using a fake identity, up from 31% in 2025, and 67% had confirmed or strongly suspected an interview proxy.
In a Gartner survey of 3,000 job candidates, 6% admitted to interview fraud, either posing as someone else or having someone else pose as them. Gartner also predicts that by 2028, 1 in 4 candidate profiles worldwide could be fake.
In practice, fraud detection is a set of calm verification steps: confirm identity, ask specific ownership questions, test real work, log interview signals, and slow down before an offer.
A remote interview can feel slightly off for reasons that have nothing to do with fraud. A candidate joins 2 minutes late. They glance below the camera. Their answer starts slowly because the call lagged or because they are nervous. It is easy to dismiss all of that as noise, especially when the team is behind on sprint planning and needed the hire yesterday.
The trouble starts when the small things stack. A candidate can explain an impressive system in broad terms, then cannot name the tradeoff they made. They describe owning a migration, then the dates do not match the resume. They sound fluent until you ask them to change one constraint and reason through what would break.
That is where a consistent structure helps more than suspicion.
What is candidate fraud in remote hiring?
Candidate fraud in remote hiring is any attempt to win a job by misrepresenting identity, experience or work. It ranges from one person inflating a resume with AI to organized schemes in which someone else interviews, someone else starts, or an overseas worker logs in to a company laptop kept at a host's home.
The common thread is distance. Remote hiring splits one person into a resume, a profile, a video call and a laptop shipment, and no single check sees all of them. That is why the checks below follow the funnel instead of piling up in one interview.
Why is remote hiring fraud rising?
Remote hiring fraud is rising because the hiring process now has more distance, more AI-written resumes, more outsourced interview prep, and fewer natural identity checks than office-based hiring had. The same shift that made global hiring easier also made impersonation and rehearsed answers easier to hide.
That does not mean most candidates are dishonest. Most are not. The practical point is narrower: remote hiring removes some of the incidental trust signals teams used to rely on without thinking about them.
In an office interview, someone checks in at reception. They meet several people in a room. Their body language, laptop, ID, and conversation all form one continuous picture. Remote hiring breaks that picture into fragments: a resume, a video call, a code test, a LinkedIn profile, maybe a recruiter note.
Fraud finds the gaps between fragments.
3 changes have made the problem sharper:
- Resume fiction is cheaper. AI can rewrite an average resume into something that sounds senior, polished, and painfully plausible. In the same Gartner survey, 4 in 10 candidates said they use AI when applying.
- Interview coaching is more available. Candidates can rehearse common answers for system design, behavioral prompts, and remote work scenarios.
- Identity signals are weaker. A remote interviewer may never meet the person who actually wrote the code sample, took the assessment, or will show up on day one.
In iProspectCheck's 2026 survey of 1,500 US managers and owners, 22.9% said they had interviewed a proxy or suspected deepfake candidate, and 29.3% had hired someone who later didn't seem to be the same person.
The 2026 numbers from Checkr point the same way. Beyond the 40% who met a fake identity, 38% of the managers reported AI-generated or deepfake interview content. Only 23% were extremely confident their process would catch a fraudulent candidate. That last figure is the real gap: most teams suspect the problem and few trust their process to find it.
The uncomfortable part is that speed makes teams easier to fool. When a role has been open for 38 days and the team is losing engineering hours every week, people want the candidate to be real. They want the explanation to be nerves. They want the process to move.
The best countermeasure is not paranoia. It is a repeatable process that catches weak signal before it becomes a bad offer.
The Cognitive covers the middle stretch of hiring: it sources, interviews, and shortlists. It finds candidates across ~900M public profiles. It reaches out by email from the recruiter's own mailbox on every Sourcing plan, the free trial included. Candidates then book a live, two-way AI video interview whose report holds scores, written feedback, a transcript and a recording.
That matters because fraud detection needs evidence, not a manager's vague feeling after a long afternoon.
If you are comparing remote interview formats, the difference between live conversation and a one-way recording is not small. A live interview can push on the answer the candidate just gave. A one-way video cannot. The guide to async video interviews versus live AI interviews breaks that difference down in more detail.
What types of candidate fraud show up in remote hiring?
Candidate fraud in remote hiring falls into 6 types, each with its own check. In a June 2022 alert, the FBI reported deepfakes and stolen personal data used to apply for remote IT jobs. By January 2025 it was warning that organized worker schemes used face-swapping during video interviews.
| Type | What happens | Where it shows | Check that catches it |
|---|---|---|---|
| Proxy interview | Someone else interviews for the applicant | A new face or voice between rounds | ID check before the final round |
| Deepfake | Face or voice altered live | Lips out of sync with the audio | ID check with a liveness step |
| AI-written answers | A tool off screen writes the answers | Generic answers that thin out on follow-up | Follow-ups built on the last answer |
| Fake profile | An invented work history | Dates and employers that don't line up | Profile continuity check at sourcing |
| Identity swap | Stolen details, or a different person starts | Day-one person doesn't match the finalist | ID check before offer; day-one match |
| Facilitated remote worker (laptop farm) | A host in the US keeps the company laptop at home and a worker overseas logs in to it remotely | Remote desktop or KVM hardware, address and payment changes | Ship to a verified address, watch remote access tools, re-verify identity |
How do North Korean IT worker schemes get through remote hiring?
North Korean IT worker schemes get through remote hiring by using other people's identities, face-swapping in video interviews, and paying people in the US to host the company laptop. They are the clearest example of organized candidate fraud, and the US government has documented them in detail. This is a known scheme, not a reason to distrust any nationality or accent. The checks below apply to every candidate.
The scale is no longer theoretical. In June 2025 the US Department of Justice announced searches of 29 known or suspected laptop farms across 16 states, and said North Korean actors had obtained jobs with more than 100 US companies.
In October 2026 it announced Operation Lonestar Roundup. Agents searched more than 40 residences in Texas and seized about 187 laptops and KVM devices. 14 people were charged, in schemes affecting more than 70 US company employers.
The FBI has described how the schemes work. Its January 2025 alert said the workers were "observed using artificial intelligence and face-swapping technology during video job interviews to obfuscate their true identities."
Its October 2026 alert added that they "are increasingly using facilitators to counter improved private sector detections." Facilitators are asked to keep work devices online from their own homes. The workers use external hardware such as TinyPilot, PiKVM and GL.iNet devices to control those laptops, and "tend to rotate through bank accounts, street addresses, social media accounts."
The FBI's recommendations translate into hiring steps:
- Cross-check applicants. Look for other applicants with the same resume content or contact information. That is row 2 of the checklist below.
- Verify identity more than once. The FBI recommends identity checks "during interviewing, onboarding, and throughout the employment of any remote worker," and, in October 2026, E-Verify, a US passport or multiple forms of identification.
- Check your staffing vendors. Confirm that third-party staffing firms run robust hiring practices, since a contractor placed by an agency skips your own funnel.
- Meet in person where you can. The FBI suggests completing as much of hiring and onboarding in person as possible.
- Layer the controls. The October 2026 alert warns that relying only on ban lists can be unreliable and calls for layered access controls and detections across the employment lifecycle.
The FBI alerts center on remote IT, programming and database roles, so teams hiring remote engineers carry the most exposure. The guide on how to hire remote developers covers the rest of that process.
What are the best practices for detecting candidate fraud in remote hiring?
The best practices are 12 checks across the hiring funnel, because each type of fraud shows up at a different stage. A fake profile is cheapest to catch before outreach. An identity swap only shows on day one.
| # | Stage | What to check | Signal it catches |
|---|---|---|---|
| 1 | Sourcing | Name, employers and dates match across resume, LinkedIn and portfolio | Fake profiles, borrowed histories |
| 2 | Sourcing | Email, phone country and stated location fit together; no other applicant shares the same resume text, email or phone | Synthetic identities, duplicate applicants |
| 3 | Application | Pick 3 to 5 resume claims the role depends on and plan a follow-up for each | AI-inflated resumes |
| 4 | Application | Invitation states the rules on notes, AI help, camera and ID checks | Gray-area help; makes later flags fair |
| 5 | Interview | Camera on, one visible face, lips matching the audio | Proxies, deepfakes |
| 6 | Interview | A change request on a project they claim to own | Rehearsed or AI-written answers |
| 7 | Interview | Tab switches, copy and paste, camera off, extra faces, a second voice, logged for review; a flag alone is not a verdict | Outside help, as context |
| 8 | References | At least 1 reference you found yourself, not only the number given | Friends posing as managers |
| 9 | References | Ask what the candidate personally did on the project they described | Borrowed project stories |
| 10 | Offer | ID and work authorization through HR; background check with Fair Credit Reporting Act consent in the US | Stolen identities |
| 11 | Onboarding | Day-one video call matches the interview recording; equipment ships to a verified address; late changes to address, payroll or bank details get a second check | Identity swaps after the offer, laptop farms |
| 12 | Onboarding | First 30 days of work match the skill shown in interviews; remote desktop tools and KVM hardware are watched; identity is re-verified during employment | A proxy that got through, facilitated remote workers |
How do you spot fake references?
A fake reference is a friend, a paid stand-in or the candidate themselves posing as a former manager. The fix is to choose at least one referee yourself. Find the manager through the company's main switchboard or a public profile, not only through the number the candidate supplied.
Then ask about work, not character. What did the candidate personally own on the project they described? What would the referee have done differently? Real managers recall dates, team names and one thing that went wrong. A stand-in tends to praise in general terms and goes vague on the details. A fixed set of reference check questions keeps the calls comparable, and the guide to reference check software covers tools that run them at scale.
How do you spot AI-written resumes?
Using AI to write a resume is not fraud on its own. In the Gartner survey, 4 in 10 candidates said they use AI when applying. The problem starts when AI invents experience the candidate does not have. In iProspectCheck's 2026 survey, AI-generated resumes were the most common fraud type employers reported, at 14.0%.
The tells are polish without specifics: every bullet ends in a percentage, the tools list matches the job post word for word, and no project has a date, a team size or a failure. The check is the same as for any claim. Pick 3 to 5 resume lines the role depends on and ask for the decision behind each one.
The AI-generated resumes resource lists the patterns to look for, and the guide on how to spot a fake resume covers diploma mills and employment verification.
Red flags during a remote interview
Remote interview red flags are behaviors or answer patterns that suggest the candidate may not be the person, owner, or skill level represented in the application. The useful red flags are specific and observable: mismatched identity details, inconsistent project facts, generic answers after follow-up, unusual assistance signals, and contradictions between the resume and live explanation.
Do not overreact to one awkward moment. A candidate looking down may be reading notes, checking the prompt, calming themselves, or dealing with a second monitor. Remote interviews are strange. Good candidates get nervous too.
Look for clusters.
| Signal | What you might observe | What it could mean | Fair follow-up |
|---|---|---|---|
| Identity mismatch | Name, face, voice, or profile details do not line up | Possible impersonation or shared account | Ask for a standard identity verification step used for all finalists |
| Generic project ownership | Candidate describes architecture but not decisions they made | They may have studied the project but not owned it | Ask for one tradeoff, one failure, and one change they personally handled |
| Date inconsistency | Timeline differs from resume, LinkedIn, or prior answer | Inflated tenure or borrowed experience | Ask them to walk through the project timeline in sequence |
| Delayed patterned answers | Long pauses before every technical answer, then polished phrasing | Possible live assistance, though not proof | Ask a practical, role-specific follow-up that depends on their last answer |
| Tool behavior | Repeated tab switches, camera off, face not visible, another voice | Possible outside help or AI-assisted answer generation | Log the event and continue with a consistent integrity check |
| Audio and video out of sync | Lips don't match the words; a cough with no matching movement | Possible deepfake, the pattern the FBI described in 2022 | Note the timestamp and move ID verification ahead of the next round |
| Different person between rounds | Face, voice or accent changes between the screen and the final | Possible proxy interview | Run the standard ID check and compare the recordings side by side |
The strongest red flag is not a behavior. It is a loss of specificity.
A candidate says they led a database rollback. Broadly, they sound fine: customer impact, incident channel, hotfix, postmortem. Then you ask what metric told you the rollback worked. They answer, "we monitored the system." You ask which metric. They say "latency and errors." You ask where the threshold came from. They pause and move back to generalities.
That is not proof of fraud. It is a reason to keep digging.
The same pattern shows up in non-technical roles. A remote customer support candidate claims they reduced escalations. Ask which tickets were escalated before the change, what macro they edited, how QA measured the change, and what tradeoff got worse. Fraudulent or inflated experience often collapses when the story has to survive ordinary detail.
Modern interview cheating detection and anti-fraud monitoring should log behaviors like tab switches, camera-off moments, and face tracking events, but those signals should feed human review. They should not become an automatic rejection by themselves.
A fair red flag is something you can write down without guessing motive.
"Candidate looked down" is weak. "Candidate looked below the camera before 7 technical answers, then contradicted the resume date for the payments migration" is stronger. "Candidate used AI" is an accusation unless you have evidence. "Candidate switched tabs 11 times during the coding question and could not explain the submitted code" is an observation.
What is an identity verification checklist?
An identity verification checklist is a standard set of steps used to confirm that the person interviewing is the same person represented in the application and, later, the same person who joins the company. In remote hiring, the checklist should be consistent, documented, and applied at the same stage for every comparable candidate.
The word standard matters. If you only verify candidates who "feel suspicious," you create fairness risk. You also train interviewers to rely on vibes, which is exactly what structured hiring is supposed to reduce.
A practical identity checklist does not need to be dramatic. Most teams need 5 checks:
- Application consistency. Compare name, email, location, work history, portfolio links, and public profile details before the live interview.
- Video presence. Require camera on for identity-sensitive roles, with exceptions handled through a documented accommodation path.
- Profile continuity. Check whether the resume, LinkedIn profile, GitHub or portfolio, and recruiter notes tell the same timeline.
- Finalist verification. Before offer, confirm government ID or work authorization through your normal HR process, not ad hoc interviewer judgment. Calls to former managers, using a fixed set of reference check questions, add a second source on the work history.
- Day-one continuity. Make sure the person who starts work matches the finalist who completed the interview process.
For remote technical roles, add one more: ask the candidate to explain a past project as if onboarding a new teammate. Then make a small change request. Nothing theatrical. Just something like, "Assume traffic doubles next month and the database cost has to stay flat. What changes first?"
If they owned the work, they will usually know where the bodies are buried. The slow query. The weird stakeholder constraint. The test they skipped and regretted. If they only studied the resume story, their answer tends to float above the ground.
The Cognitive's live two-way AI interviewer is useful here because it does not run a static script. It decides the next question live from the job description, rubric, resume, and the candidate's previous answers. The rubric stays fixed for the role. The follow-up adapts. That is the combination you want when the problem is vague claims: a consistent evaluation bar, sharper probing.
Set the identity policy before the interview loop starts. Decide what you verify at application, what you verify before final rounds, and what you verify before offer. Then tell candidates clearly. Hidden traps damage candidate experience and invite inconsistent decisions.
Before the interview
Before the interview, fraud detection starts with reducing ambiguity. Write a specific job description, build a role rubric, verify basic contact data, and decide which identity checks happen at which stage. Most fraud prevention gets harder once the interview is already live.
The prep stage is boring. It is also where the process gets safer.
Start with the job description. A vague role invites vague stories. If the JD says "build scalable systems," every candidate can claim they did. If it says "own the billing service, debug production incidents, reduce queue latency, and work across US and UK time zones," the interview has real edges.
If your job post is full of soft phrases, use the free AI JD Grader to spot unclear requirements, cliches, and vague expectations before candidates ever see it. A sharper JD makes it harder for a dishonest candidate to hide behind broad language.
Next, build the rubric. A fraud-aware rubric does not say "technical skill" and leave the interviewer to improvise. It names the behaviors that prove the skill:
- Can explain a system they personally changed, including constraints and tradeoffs.
- Can name a failure, the signal that exposed it, and what changed afterward.
- Can reason through a new scenario without relying on memorized phrasing.
- Can describe how they work remotely: documentation, async handoffs, timezone overlap, and escalation habits.
You can build this manually, or start with the free AI Interview Rubric Generator. The point is not the tool. The point is that interviewers should know what proof sounds like before they enter the call.
Sourcing also matters. The Cognitive's AI sourcing tool reads a plain-English brief into editable filters, opens each result card with a "Why this match" line traced to the profile, and reveals personal emails and phone numbers. Sourced candidates can be invited to the AI interview in one go. That one-pipeline model helps because candidate identity, outreach, interview evidence, and shortlist decisions are not scattered across 5 disconnected tools.
Before the interview, send clear instructions:
- Camera expectations and what to do if there is a technical issue.
- Whether notes are allowed.
- Whether outside help or AI assistance is allowed.
- What identity verification will happen and when.
- How recordings and transcripts are used for review.
Clarity is underrated. A candidate who knows the rules is less likely to stumble into a gray area, and your team has cleaner ground if something looks wrong. Gartner's own advice points the same way: set clear expectations about acceptable AI use and tell candidates how fraud is detected.
Remote interview questions that are harder to fake
Remote interview questions are harder to fake when they force the candidate to connect claims to decisions, constraints, dates, and live reasoning. The best questions make a polished story interact with reality.
Most fraudulent or inflated answers survive the first question. They fail on the second or third.
Here is the simple pattern:
- Ask for the project. "Walk me through a project you owned that is closest to this role."
- Ask for ownership. "Which decision was yours, and which parts did other people own?"
- Ask for a tradeoff. "What got worse because of the choice you made?"
- Ask for a change request. "Now assume the constraint changes. What would you do differently?"
- Ask for evidence. "What metric, customer signal, or incident told you it worked?"
The change request is the turn. Someone who memorized a project summary can often sound good for 5 minutes. Ask them to modify the system and the answer starts to reveal whether they understand the work.
For a backend developer, that might sound like:
- "You said you added caching to reduce latency. What data could not be cached, and why?"
- "If writes doubled next month, what breaks first?"
- "What did you measure before and after the change?"
- "Which part of the design did you disagree with at the time?"
For a remote customer success manager:
- "You said you improved onboarding. Which step caused the most drop-off before the change?"
- "What did you document so another teammate could run the same process?"
- "Tell me about one customer where your first recommendation was wrong."
For a remote finance or operations role:
- "Which reconciliation issue took longest to diagnose?"
- "What control did you add, and what extra work did it create?"
- "If the close window moved from 5 days to 3, what would you change first?"
If you need a starting set, the free AI Interview Question Generator can turn a role, competency list, and interview duration into structured questions with follow-ups and red flags. Do not use any generated list blindly. Edit it until the questions sound like your actual work. For honesty-focused prompts, the ethics and integrity interview questions give you a tested starting set.
The scorecard matters as much as the question. A good interviewer should not leave the call with "seemed strong." They should leave with timestamped evidence: the candidate explained the rollback clearly at 12:40, contradicted the resume at 18:05, and could not reason through the changed constraint at 16:10.
That is why evidence matters more than a number. In The Cognitive, each criterion gets a 1 to 5 score with written feedback, and the full transcript and recording sit in the same report, so a hiring manager can go back to the exact answer behind a concern. The AI organizes the evidence. People decide.
During evaluation
During evaluation, separate behavior logs from skill scores, compare answers against the rubric, and require evidence before escalating a concern. This keeps the process fair when interviewers feel uneasy but cannot yet prove why.
Remote fraud detection gets messy when every signal goes into one bucket called "concerns." Do not do that. Split the evidence into 3 lanes:
| Lane | What belongs there | Who reviews it | Decision use |
|---|---|---|---|
| Identity | Name mismatch, profile mismatch, finalist verification issue | Recruiter or HR owner | May require verification before moving forward |
| Integrity | Tab switches, camera-off events, possible outside voice, unusual answer timing | Recruiter plus hiring manager | Context for follow-up, not automatic rejection |
| Competency | Weak reasoning, contradictions, inability to explain claimed work | Hiring manager and interview panel | Scored against the same rubric as every candidate |
This split protects candidates too. A poor technical answer is not fraud. A nervous communication style is not fraud. A tab switch might be a mistake. But if identity, integrity, and competency concerns all point in the same direction, you have a serious reason to pause.
The other discipline is consistency. If one candidate gets 3 follow-ups on ownership and another gets none, your process is not measuring the same thing. This is where structured interviews help. The exact questions can adapt, but the rubric and scoring standard should remain stable.
If you are unsure where to start, fix the scorecard before buying another tool. A clear scorecard forces the panel to write what happened, not what they felt. The free AI Interview Scorecard Generator is a useful way to turn role requirements into scoring anchors before the loop begins.
The Cognitive is built around that same idea. Its report carries a 1 to 5 score per criterion plus overall written feedback, a weighted score out of 100, a suggested verdict, the transcript, the recording and the integrity flags. A flag alone never lowers a score, and nothing is rejected automatically.
There is a limitation worth saying plainly. Fraud detection methods can create false positives if you treat every odd behavior as intent. Remote candidates have bad Wi-Fi, shared apartments, noisy children, second monitors, anxiety, and accessibility needs. A fair process leaves room for ordinary mess.
Suspicion is cheap. Documentation is work.
What can an AI interview detect, and what can't it?
An AI interview can raise integrity signals for a reviewer and probe resume claims live, but it can't confirm who someone is. It produces evidence for a person to weigh, not a verdict. Here is the split for The Cognitive's live AI interview, in which a video avatar interviews the candidate over their camera for 10 or 20 minutes, in any of 9 languages.
What The Cognitive's AI interview flags during the call
- Browser and screen events. Tab switches, the window losing focus, copy and paste, leaving full screen, screenshot keys, and a second monitor where the browser reports one.
- Camera events. Camera off, no face in view, extra faces, and a virtual camera, meaning video software feeding the call instead of a real webcam.
- Answer events. Answers typed into the session, and attempts to get the interviewer to reveal the rubric, the score or its instructions.
What it checks after the call
- A video and voice check on the recording. It looks for a played-back clip, signs of a generated or swapped face, a screen or photo held up to the camera, a change of person partway through, someone else on camera, and a second voice besides the interviewer and the candidate. Any finding appears in the report as a "Video or Voice Check" flag.
- Resume claim checks. The AI plans up to 5 claims or gaps from the candidate's resume and profile to probe, and each comes back marked verified, refuted or unclear, with evidence from the interview.
- Live follow-ups, judged on a fixed rubric. The rubric is fixed per role and the questions adapt to what the candidate just said.
How the flags are used
A flag alone never lowers a score, and nothing is rejected automatically. When the evidence shows an answer was not the candidate's own, for example typed in or supplied by someone else, the report says so plainly and that answer is not credited. Everything else is context for the reviewer, who decides what it means.
What it can't do
- It does not check a government ID. The face checks look for a face, extra faces and whether the same person stays on camera; they do not match anyone to an ID.
- It can't prove identity or prove a deepfake. The video and voice check is a signal for a reviewer, not proof, and a mismatch between lips and speech can come from a bad connection.
- It can't see a phone or a second device off camera, or tell a notification from a cheat sheet behind a tab switch.
- It can't judge motive. A refuted claim can be a fabrication or a memory slip.
So pair it with an ID check before the final round, and let the interview test whether the person can talk through the work they claim. The guide to AI interview cheating detection covers how candidates try to game AI interviews.
Five minutes from an interview for a go-to-market role. The AI asks about an outbound email campaign, then follows up on reply rates and lead qualification, each question built on the last answer.
Probe resume claims in a live AI interview Source candidates, invite them in one go, and review integrity flags and claim checks in one report. Start free
Which tools help with remote candidate fraud detection?
Remote candidate fraud detection tools fall into 3 groups: identity verification, interview proctoring and background checks. Most teams combine an ID check with an interview that probes the work. Here is what 4 of them say they check, in each vendor's own words:
| Tool | What it checks, in its own words | When it runs | Checks an ID document? | Price on website? |
|---|---|---|---|---|
| Greenhouse Real Talent | Phone number, email address, IP address and location signals; CLEAR identity verification | At points like before interviews or offers | Yes, through CLEAR | No |
| Alex | Email, phone, connection and LinkedIn profile, checked one by one; government ID matched to a selfie with a liveness check | Before an interview, from a workflow, or on demand | Yes | No |
| HireVue | Loss of focus, location signals, identity continuity, browser monitoring, disabling paste, candidate transparency, fraud dashboard | During HireVue interviews and assessments | Lists ID verification, without detail | No |
| The Cognitive | Tab switches, copy and paste, leaving full screen, a second screen, camera off, virtual camera, missing or extra faces, typed answers; a video and voice check on the recording; up to 5 probed resume claims | During and right after the live AI interview | No | Yes |
Greenhouse Real Talent returns 26 signals in 3 groups. Alex can hold an interview until verification passes and sends name mismatches to human review. HireVue calls its page "the integrity layer that flags cheating signals in the hiring process" and fits teams already running its interviews.
The full list of ID tools sits in the guide to candidate verification platforms. For the pre-offer step, see the guide to background check software, and the best tools for remote recruitment for the full stack.
What should you check after the offer and on day one?
After the offer, check that the person, the address and the bank account all stay the same as the ones you verified. Most hiring checklists stop at the signed offer, which is exactly where a facilitated worker scheme starts. In Checkr's 2026 survey, 44% of companies lacked a formal, written process for verifying identity after hire.
A short post-offer routine covers most of the risk:
- Ship equipment only to the verified address. Treat a request to send the laptop somewhere else, or a last-minute address change, as a reason for a second check rather than a logistics detail.
- Watch payroll and bank changes. The FBI notes that these workers rotate through bank accounts and street addresses. A new hire who changes payment details in the first weeks deserves a call over video.
- Look for remote access tools. Remote desktop software and KVM hardware on a company laptop are how an overseas worker controls a device kept in someone else's home. Your IT team can flag both.
- Grant least privilege. New hires get the access the first month of work needs, not the full production keys on day one.
- Re-verify identity during employment. The FBI recommends identity checks throughout employment, not only at the offer. A day-one video call compared against the interview recording is the cheapest first step.
Then compare the first 30 days of work with the skill shown in interviews. A proxy can pass an interview. It is much harder to fake a month of daily standups, code reviews and customer calls.
What laws apply to fraud checks in remote hiring?
Identity checks touch consent, biometric and background check laws, so involve your counsel before you add one. This is general information, not legal advice.
- Illinois BIPA. The Biometric Information Privacy Act counts a voiceprint or a scan of face geometry as a biometric identifier. Section 15 requires written notice, a stated purpose and retention period, and a written release before collection, and destruction within 3 years of the last interaction at the latest. Ask any selfie-match vendor who collects that consent.
- Background checks. In the US, the FTC's Fair Credit Reporting Act guidance requires a stand-alone written disclosure and written permission before a consumer reporting agency runs the check, and a copy of the report before you reject someone over it.
The Cognitive's face checks look for a face, extra faces and whether the same person stays on camera; they do not match anyone to an ID. The invitation tells candidates the interview is run by AI. Ask your counsel how your state treats any face analysis, The Cognitive's included.
What to do if you suspect fraud?
If you suspect fraud, pause the process, document exact observations, run the same verification step you would use for any similar concern, and avoid accusing the candidate without evidence. The goal is to protect the hire and the candidate experience at the same time.
A good response has 5 steps.
- Write down observations immediately. Use timestamps, quotes, and facts. "Contradicted resume dates for Acme project" is useful. "Something felt off" is not. A shared interview notes template keeps those records in one format.
- Separate fraud from poor performance. If the candidate cannot explain the project, they may simply be unqualified. That is a hiring decision, not a fraud case, and a plain note from these candidate rejection email templates closes it politely.
- Run a structured follow-up. Ask the same type of clarifying questions you would ask any candidate with unclear ownership.
- Verify identity through policy. Use your normal finalist or HR verification process. Do not improvise a harsher process for one person.
- Decide with humans. Tools can surface evidence. People should decide whether the concern is resolved, disqualifying, or just a weak signal.
Here is a follow-up script that keeps the temperature low:
"We want to clarify a few details from the interview so we can assess everyone consistently. Please walk us through the project timeline, your specific responsibilities, and one technical or operational decision you personally made. We may ask a few follow-ups based on your answer."
Notice what is missing. No accusation. No dramatic reveal. No "we caught you." Just a request for specifics.
If the candidate gives a clear explanation and the details line up, move on. If the contradictions deepen, document the result and close the process respectfully. You do not need to prove a courtroom case to decide not to hire someone. You do need enough evidence to show the decision was job-related, consistent, and fair.
This is also where velocity and caution have to be held together. The answer is not to skip verification. It is to make verification faster and more structured. The Cognitive helps by sourcing candidates, letting them book a live AI interview themselves, and handing you a report to decide who goes to the human round. AI Sourcing and AI Interview each start at $99/month.
If you are choosing tooling under pressure, the comparison of video interview software platforms is a useful checklist. The short version for fraud detection: pick the tool that preserves evidence, not the one that merely records a meeting.
How to make fraud detection fair instead of hostile
Fair fraud detection means every candidate gets the same rules, the same evaluation standard, and the same chance to clarify unclear evidence. The best process feels firm, not suspicious.
That starts with language. Tell candidates what is allowed. Tell them whether notes are fine. Tell them the interview is recorded for evaluation. Tell them identity may be verified at finalist stage. People handle rules better than traps.
Then train interviewers to ask better follow-ups. The weakest remote hiring processes rely on one senior person improvising under time pressure. On a good day, that person catches the inconsistency. On a bad day, they are tired, late for sprint planning, and too polite to push.
A structured process makes the good day repeatable.
There is also a candidate experience upside. Honest candidates usually like specific interviews more than vague ones. They get to show their actual work. They do not lose to someone with a polished resume and borrowed project language. For broader process risks, especially when roles are reopened or standards shift mid-search, read the piece on fair hiring practices when a role changes.
The final rule is simple: never let fraud detection become a shortcut around hiring discipline. You still need a clear role, a real rubric, good questions, and humans making the final decision.
If you want to test what this looks like on your own role, run a few finalists from an open role through The Cognitive's live AI interview and compare the reports to your usual notes. Look at the integrity flags, the resume claims it probed, and the follow-ups. Decide from the evidence, not from the pitch.
You can start free. The free trial includes 50 sourcing credits.
Run your next remote role through The Cognitive Find candidates across ~900M public profiles and interview them live with AI, with integrity flags and a video and voice check in the report. Start free
Sources
- HR Dive, "By 2028, 1 in 4 candidate profiles will be fake, Gartner predicts", 8 August 2025, reporting Gartner's survey of 3,000 candidates (Gartner press release, 31 July 2025).
- Checkr, "The hiring hoax 2026", published 15 October 2026, survey of 3,000 US managers involved in hiring, fielded 11 to 16 September 2026.
- iProspectCheck, 2026 State of Screening Report, published 29 July 2026, survey of 1,500 US business managers and owners.
- FBI Internet Crime Complaint Center, "North Korean IT Workers Expanding Use of Facilitators, Broadening Recruitment", public service announcement I-101326-PSA, 13 October 2026.
- FBI Internet Crime Complaint Center, "North Korean IT Workers Conducting Data Extortion", public service announcement I-012325-PSA, 23 January 2025.
- FBI Internet Crime Complaint Center, "Deepfakes and Stolen PII Utilized to Apply for Remote Work Positions", 28 June 2022.
- US Department of Justice, "Justice Department Announces Coordinated Actions to Combat North Korean Remote IT Worker Schemes Affecting More than 70 U.S. Companies", 13 October 2026.
- US Department of Justice, press release on coordinated nationwide actions against North Korean remote IT worker schemes, 30 June 2025.
- Greenhouse, Real Talent.
- Alex, Identity verification documentation and Alex Verify.
- HireVue, Cheating and fraud mitigation.
- Illinois Biometric Information Privacy Act, 740 ILCS 14/10 and 740 ILCS 14/15.
- FTC, "Using Consumer Reports: What Employers Need to Know".
Frequently Asked Questions
How do companies detect and prevent hiring fraud during remote interviews?
Companies detect and prevent remote interview fraud by verifying identity at set stages, keeping the camera on, asking follow-ups that depend on the last answer, and logging integrity events for human review. Prevention starts before the call: publish your rules on notes, AI help and ID checks in the invitation. During the call, a change request on a project the candidate claims to own exposes rehearsed answers. Before the offer, run ID and work authorization checks through HR, then match the person on day one to the finalist.
What tools help detect candidate fraud in remote hiring?
Tools for remote candidate fraud detection fall into ID verification, interview proctoring and background checks. Greenhouse Real Talent reads phone, email, IP and location signals and verifies identity with CLEAR. Alex matches a government ID to a selfie with a liveness check. HireVue lists loss of focus, identity continuity, browser monitoring and ID verification. The Cognitive flags integrity events in a live AI interview, runs a video and voice check on the recording and probes up to 5 resume claims, but it does not check IDs, so most teams pair it with an ID tool.
How common is candidate fraud in remote hiring?
In Checkr's 2026 survey of 3,000 US hiring managers, 40% had personally interviewed a candidate later revealed to be using a fake identity, up from 31% in 2025. In the same survey, 67% had confirmed or strongly suspected an interview proxy. In a Gartner survey of 3,000 job candidates reported in August 2025, 6% admitted to interview fraud, and Gartner predicts 1 in 4 candidate profiles worldwide could be fake by 2028. In iProspectCheck's 2026 survey of 1,500 US managers and owners, 22.9% said they had interviewed a proxy or suspected deepfake candidate.
Can an AI interview detect a proxy or deepfake candidate?
An AI interview can raise signals of a proxy or a swapped video for a reviewer, but it can't prove identity on its own. During the call, The Cognitive flags events such as tab switches, copy and paste, leaving full screen, a virtual camera, typed answers and missing or extra faces. After the call, it checks the recording for a played-back clip, signs of a generated or swapped face, a change of person and a second voice, and shows any finding as a flag. A flag alone never lowers a score and nothing is rejected automatically. It does not check a government ID, so pair it with an ID check before the final round and compare recordings across rounds.
What are the red flags of a fake candidate in a video interview?
The strongest red flag is a loss of specificity: broad answers that fall apart on the second or third follow-up. Other signals are audio that doesn't match lip movement, a different face or voice between rounds, dates that differ from the resume, long pauses followed by polished phrasing, and repeated tab switches. One signal is a reason to dig, not proof. Act on clusters, and document each one with a timestamp.
Is it legal to verify a candidate's identity with a selfie or face scan?
It can be, but biometric and background check laws set conditions, so ask your counsel first; this is not legal advice. The Illinois Biometric Information Privacy Act requires written notice, a stated purpose and retention period, and a written release before collecting a scan of face geometry, plus a public destruction policy. In the US, background checks through a consumer reporting agency need a stand-alone written disclosure and written permission under the Fair Credit Reporting Act.
What should you do if you suspect a candidate of fraud?
Pause the process, write down exact observations with timestamps, and run the same verification step you would use for any similar concern. Separate fraud from poor performance, since a weak answer is a hiring decision, not a fraud case. Send a neutral follow-up asking for the project timeline and one decision they personally made. Let people, not tools, decide whether the concern is resolved.
What interview questions for remote workers help detect fraud?
Interview questions for remote workers help detect fraud when they ask for ownership, tradeoffs, dates, and a change request to work the candidate claims to know. Ask them to explain a real project as if onboarding a teammate, then change one constraint and listen for specific reasoning.
Which remote job interview questions are hardest to fake?
Remote job interview questions are hardest to fake when they depend on the candidate's previous answer. Good examples include asking what broke first, what metric proved the fix worked, what got worse because of their decision, and what they would change if the constraint shifted.
Which remote work questions should candidates answer with specifics?
Remote candidates should give specifics on async handoffs, documentation habits, timezone overlap, escalation rules, and one time they handled a missed signal remotely. Generic answers like "I communicate well" are weak unless backed by a real example.
Which remote interview answers should you document?
Document every answer that bears on identity, integrity, ownership or a job-critical skill. Keep the exact question, the candidate's answer, timestamps, and any follow-up so the final decision rests on evidence rather than memory.
What are North Korean IT worker schemes in hiring?
North Korean IT worker schemes are organized efforts to get remote IT jobs at foreign companies under other people's identities. The FBI reported in January 2025 that the workers used AI and face-swapping during video interviews, and in October 2026 that they increasingly rely on US facilitators who keep company laptops online at home. The US Department of Justice announced searches of 29 suspected laptop farms in 16 states in June 2025 and, in October 2026, actions in schemes affecting more than 70 US companies. The FBI recommends identity checks during interviewing, onboarding and employment, cross-checking duplicate applicants, and checking the hiring practices of third-party staffing firms.
How do you spot fake references?
Spot fake references by choosing at least one referee yourself instead of relying only on the contacts a candidate supplies. Find the former manager through the company's main line or a public profile. Ask what the candidate personally owned on a specific project and what went wrong. Real managers recall dates, team names and setbacks, while a stand-in tends to stay general.
What should you verify after a remote hire starts?
After a remote hire starts, verify that the person, the address and the bank account match what you checked before the offer. Ship equipment only to the verified address, treat early changes to address or payroll details as a reason for a second check, watch for remote desktop tools and KVM hardware on company laptops, and re-verify identity during employment as the FBI recommends. In Checkr's 2026 survey, 44% of companies lacked a formal, written process for verifying identity after hire.
Related reading
- Interview Cheating Detection and Anti-Fraud Monitoring With AI: 11 Tactics, the Signals That Catch Them and the Gaps
- Async Video Interview vs Live AI Interview: Which Works Better for Remote Hiring?
- 25 Recruitment Strategies That Work in 2026, Sourcing First
- Sourcing Meaning: What the Word Means in Recruiting and in Business
- How to Find Professional Contact Information Ethically: A Recruiter's Guide (2026)
- PeopleGPT Alternatives: 9 Plain-English Candidate Search Tools Compared in 2026