ChatGPT in Job Interviews: What Employers Need to Know

ChatGPT and its competitors have changed the economics of interview fraud. What once required a well-placed contact willing to whisper answers now requires a second device, a free account, and thirty seconds. Employers who do not have a clear policy and detection strategy are flying blind.

This article does not argue that all AI use is cheating — that debate is worth having separately. It focuses on the narrower problem: candidates using AI tools covertly during live interviews in ways that misrepresent their ability to do the job, creating risk for both the employer and for other candidates competing honestly.

How candidates use ChatGPT during interviews

The most common pattern is simple: a phone or tablet sits off-camera, running a ChatGPT conversation alongside the video call. The candidate reads the interviewer's question, types or voice-transcribes it, and reads back the response. On coding questions this produces answers that arrive as a single fluent block after a short pause — a pattern that differs measurably from real-time thinking.

More sophisticated setups run a native desktop application that captures screen content and audio, generates responses, and displays them in a window configured to be invisible to screen-capture APIs. These are not hobbyist tools — several have active subscriber counts in the tens of thousands.

Why traditional countermeasures fail

Asking candidates to close other applications does nothing against a phone. Watching for "signs of reading" is too slow and too subjective to be consistent across interviewers. Blocking AI domains at the network level fails because the candidate controls their own internet connection. Detecting the specific application rather than the behaviour is a cat-and-mouse game that tool developers win by releasing a new version.

A durable detection approach watches signals that do not change when the tool rebrands: focus events, window presence, clipboard behaviour, and input timing. None of these require knowing which AI product the candidate is using. We cover the full signal set in How to Detect AI Assistance in Remote Interviews.

Setting a clear policy before the interview

Detection and policy are two separate problems. Detection without a stated policy creates legal and reputational risk — you cannot disqualify a candidate for something they were not told was prohibited. A well-structured pre-interview disclosure does three things: it states which tools are and are not permitted, explains what monitoring will run, and obtains explicit consent. Candidates who object can withdraw before any monitoring data is collected.

1. Pre-interview disclosure sent with calendar invite
2. Candidate consent collected before session begins
3. Integrity agent runs — metadata only, no content capture
4. Signals correlated into a score at session end
5. Signed report shared with hiring team for review
6. Any disqualification decision made by a human reviewer

Distinguishing AI assistance from legitimate AI fluency

Not all AI use during an interview is deceptive. Some roles explicitly test a candidate's ability to use AI tools effectively. The key distinction is disclosure: a candidate who says "I'd normally use Copilot here, may I?" is demonstrating honest judgment. A candidate who runs a covert assistant while presenting its output as their own thinking is misrepresenting their ability.

Your policy should draw this line clearly. In most cases: disclosed tool use is permitted or evaluated on its merits; undisclosed tool use in a session where monitoring is running is a disqualifying integrity signal.