Interview fraud and proxy candidates: what actually works

What does interview fraud actually look like?

Four patterns cover almost all of it: a proxy sitting the interview in place of the candidate, a second person feeding answers off-camera, an AI assistant generating answers in real time, and pre-obtained assessment questions. They differ in how detectable they are, and conflating them is why so many responses miss.

Proxy candidates — someone else taking the interview entirely — are the most damaging and the most detectable, because the mismatch shows up later at onboarding. Coaching and AI assistance are far more common and much subtler: the candidate is who they say they are, but the answers are not theirs.

Question leakage is a different problem again and is the one most often ignored, because it implicates the employer's own process rather than the candidate. An assessment whose items have circulated for two years is not measuring what anyone thinks it is.

Why is "detection" the wrong frame?

Because every available signal is probabilistic and every one has an innocent explanation. A candidate looking off-camera may be reading a second monitor or may have a window. A pause before answering may be retrieval or may be thought. Treating any of these as proof produces false accusations against real candidates, which is a worse outcome than the fraud.

This is why OpusHire surfaces integrity signals as timestamped moments a human reviewer can check against the recording, rather than as a trust score. The reviewer sees what happened and decides. A number that silently gates candidates concentrates every false positive into a decision nobody ever reviews.

The asymmetry matters. Missing a fraudulent candidate costs you one bad hire, caught at probation. Falsely flagging an honest one costs that person a job they earned, and you will never know you did it.

What actually reduces interview fraud?

Structural changes, not detection features: rotating item banks so questions cannot be memorised, scoring on the server so answer keys never reach the browser, asking follow-up questions that require reasoning about the candidate’s own prior answer, and keeping recordings so a suspicion can be checked later rather than resolved in the moment.

• Rotate and retire items. Leakage is inevitable over time; the question is whether you can respond to it without rebuilding the assessment.
• Score on the server. If the browser knows the answers, the result is unverifiable regardless of what else you do.
• Ask follow-ups grounded in the answer just given. Generic questions are easy to feed; "why did you choose that over the alternative you mentioned" is much harder.
• Keep the recording and transcript. The value is not surveillance, it is that a concern raised at offer stage can be checked against what was actually said.
• Verify identity at the point it matters. Onboarding, not the screening interview.

What should you tell candidates?

Exactly what is recorded, what is checked and why, before anything is captured. Beyond being a legal requirement in most jurisdictions, disclosure is a deterrent: candidates who know a session is recorded and reviewed behave differently, which does more work than any detection model.

Burying it in the terms of service is not disclosure. An interview is a recording of a person and their agreement to it should be a distinct, informed step — which is how OpusHire treats it.

Frequently asked questions