AI cheating in interviews: what recruiters can actually see

AI cheating in interviews usually means a candidate gets help from a tool or a person while answering: a chatbot in another window, an overlay app that listens and suggests answers, or someone off camera feeding lines. Recruiters can't reliably tell from the answer itself whether it came from AI. What you can see is the behavior around the answer, such as switching tabs, pasting text, looking away at a fixed spot, or a second person in the room. Build your screen around those observable events and have a person review them.

Managers already suspect it is common. In Checkr's survey of 3,000 US managers (September 2025), 59% said they had suspected a candidate of using AI tools to misrepresent themselves, and 62% agreed that job seekers are now better at faking their identities with AI than hiring teams are at detecting them.

What does AI cheating in interviews look like?

Assisted interviews tend to fall into a handful of patterns, and they differ in how much they leave behind.

The last row is identity fraud more than cheating, but the two overlap. The FBI warned in January 2025 that North Korean IT workers "have been observed using artificial intelligence and face-swapping technology during video job interviews to obfuscate their true identities." If you screen remote technical roles, read our pieces on deepfake job candidates and the North Korean IT worker scheme too.

Can you tell from the answer whether a candidate used AI?

Not with any confidence. People want a detector that reads an answer and says "that came from ChatGPT." We don't think one exists that you should trust with someone's job. A strong candidate who prepared well can sound polished and structured. A nervous candidate reading from notes can sound robotic. An AI-assisted answer can sound perfectly human once the candidate says it out loud in their own words.

So treat answer content as a signal about skill, and treat behavior as the signal about integrity. Keep them separate in your notes. When a recruiter writes "sounded like ChatGPT" in a submission note, the client has no way to check it, and the candidate has no way to answer it.

A few answer patterns are still worth a follow-up question (not a verdict):

• A long, well-organized answer that follows a delay of several seconds, repeated across questions.
• Textbook definitions with no example from the candidate's own work.
• A confident answer to the first question and a vague one when you ask "what happened next on that project?"
• Answers that address a slightly different question than the one asked, as if a tool misheard it.

What can recruiters actually see during a remote screen?

On a normal video call, very little: a face, a voice and whatever is behind the candidate. You can't see other windows, a phone on the desk, or anything running on the machine.

A browser-based screening tool can record more, because the candidate takes the interview inside a controlled page. Here is what is realistic to observe, and what isn't.

How do you set up a screen that discourages AI cheating?

Telling candidates up front what is recorded sets the rules before anyone is tempted to bend them. This checklist is what we'd set up for any remote first screen.

1. Tell candidates in the invite what is monitored and why, so nobody is surprised later.
2. Run the screen in a controlled page with full-screen enforced and paste restricted.
3. For higher-risk roles, require a second camera angle that shows the desk and the laptop, not just the face.
4. Ask follow-up questions that build on the candidate's last answer. A tool can produce a first answer quickly; a chain of "why did you choose that" and "what went wrong" is harder to fake live.
5. Ask for specifics from the candidate's own experience: project names, team size, the bug they remember.
6. Keep a timestamped log so a reviewer can match each event to the question being asked at that moment.
7. Decide in advance what a flag means. One tab switch during a long answer is different from five tab switches, each right after a technical question.
8. Put every flag in front of a person before it affects a decision.

How should a recruiter review an integrity flag?

Context first. Open the timeline, find the question that was on screen when the event happened, and listen to the answer that followed. Then ask:

• Did the event happen right after a hard question, or during small talk?
• Is it a single event or a pattern across several questions?
• Did answer quality jump after the event?
• Is there an innocent explanation the candidate could offer (a notification, a pet, a dropped connection)?

If you can't decide, move the candidate forward with a note to probe that topic live in the next round. A clear pattern is worth raising with the candidate directly before rejecting. Gartner reported, as covered by HR Dive, that in a survey of 3,000 job candidates 6% said they had participated in interview fraud. That is a real minority, which is exactly why a single ambiguous flag shouldn't sink someone.

How Simplehire handles integrity in an AI voice screen

Simplehire runs the screen as an AI voice interview in the browser. It does not try to judge whether an answer came from AI. It records integrity events and puts them in the screening report for a person to review.

Every tier (Basic, Adaptive and Advanced) includes:

• Enforced full-screen mode, with any exit recorded in the report.
• Copy, cut and paste restricted or flagged.
• Tab switches, window changes and focus loss monitored and included in the integrity summary.
• Common shortcuts for copying, searching or switching blocked or flagged.
• A timestamp on every integrity event, recorded interview audio, and screenshots attached to alerts.

For higher-risk roles, recruiters can add more:

• Simplehire Proctor for supported Windows interviews. Candidates close risky applications, for example remote-desktop tools, and re-check before the interview starts. During the interview, desktop checks run in the background and record high-severity findings without interrupting. The checks cover supported system facts and do not capture screen content, keystrokes, files, URLs or audio.
• A required second device. The candidate pairs their own phone from the browser by scanning a code, with nothing to install and no account. The phone gives a side-camera view of the candidate, their laptop and the surrounding desk, which is where a second person or a reading device shows up.
• An ID check set to Off, Optional or Required. When required, the candidate passes a government ID check and a live face match before the interview begins.

Candidates are informed before monitoring begins. Alerts carry a severity of Low, Medium, High or Critical concern, and the recruiter decides what they mean. The report's Screen verdict (Advance, Maybe or Reject) is a recommendation; a person makes the hiring decision.

The proctoring page has the details. Screens cost $2, $3 or $5 depending on the tier, and you can start with 25 free Basic screens a month with no credit card.