Screen-share captures, eye tracking, behavioral cues, Whisper Mode explained, and the honest caveats — a technical breakdown.
TL;DR
The copilot software is not technically detectable during standard video interviews. Whisper Mode (Document Picture-in-Picture API) renders outside the screen-share boundary. What interviewers can observe are behavioral cues — reading eye patterns, response latency, and phrasing shifts. Proctored assessment platforms have behavioral AI that flags these cues. The risk is behavioral, not technical.
Technical Explanation
Whisper Mode is built on the Document Picture-in-Picture API — a W3C web standard (documented at developer.chrome.com/docs/web-platform/document-picture-in-picture) that renders a floating window in a separate document context at the OS compositor layer.
When you share a browser tab, a window, or your entire screen in Zoom, Teams, or Google Meet, the capture happens at the application or tab layer — below the compositor. The Picture-in-Picture overlay lives above this layer. Screen share does not see it.
This is not a bug or an exploit — it is the intended behavior of the API. The same mechanism is how Netflix's PiP player continues to show over your video call when you minimize the browser. The interviewer is shown exactly what you choose to share, and nothing more.
Technical summary:
Detection Analysis
Screen-share capture
Not detectableWhisper Mode uses Document Picture-in-Picture API — the overlay renders outside the shared window boundary and is not captured by screen share on Zoom, Teams, or Meet.
Process / software scanning
Not detectableInterviewers on video calls have no access to your device processes, installed software, or browser tabs. They see only what you share.
Proctoring platform behavior AI
Partially detectablePlatforms like HireVue flag unusual eye movement patterns and tab switching. They do not detect the copilot — they detect behavioral anomalies that correlate with off-screen reading.
Eye movement / gaze tracking
Partially detectableHuman interviewers can notice if eyes track left-right in a reading pattern. More sophisticated proctoring platforms use gaze-tracking AI. Whisper Mode on a second screen minimizes this risk.
Response latency patterns
Partially detectableUnusually long pauses before answering can be noticed by experienced interviewers. The copilot generates suggestions quickly enough (1–3 seconds) that pausing to read feels like natural thinking time.
Phrasing / vocabulary shifts
Partially detectableA sudden shift from casual speech to formal, structured prose can be noticed. The mitigation is to speak the answer in your own voice, using the copilot suggestions as a scaffold rather than reading verbatim.
AI text detection tools
Not detectableGPTZero and similar tools are trained for written text. They are not applied to spoken interview responses in real time. No mainstream hiring platform uses real-time audio AI detection.
Behavioral Cues
The copilot is invisible. The candidate's behavior while using it may not be. Experienced interviewers notice the following patterns:
Eye tracking pattern
Eyes moving left-right in a reading scan rather than natural upward or side-glance thinking patterns. Reading pattern is distinctive.
Response latency
Pauses that are longer than normal thinking time, especially for simple behavioral questions where a candidate "should" have a ready answer.
Reading cadence
Even, flat speaking pace without natural hedges, filler words, or the self-corrections of unscripted speech.
Vocabulary discontinuity
Earlier in the call the candidate uses colloquial language; answers to key questions suddenly shift to formal, structured prose.
Exact question mirroring
Responses that start by re-stating the question verbatim — a common AI output pattern — rather than naturally beginning an answer.
Loss of eye contact
Looking away from camera during the exact moment of answering, rather than during the thinking phase before answering.
Best Practices
The candidates who use AI copilots most effectively treat them as a memory aid, not a script. The goal is to glance at the structure and speak in your own voice — not to read word-for-word.
Use a second monitor
Position the Whisper overlay on a second screen that is not in camera view. Eye movement to the side looks like natural thinking — not reading.
Practice before the real interview
Run practice sessions with the copilot active. Learn where to glance, how long suggestions take to appear, and how to absorb bullet points in a single look.
Use bullet point mode, not paragraphs
Configure the overlay to show 3–5 bullet points rather than full sentences. Bullets are absorbed in one glance; paragraphs require reading that shows.
Speak, don't read
Treat the suggestions as a memory cue, not a script. The copilot gives you the structure; your voice fills in the natural language. This makes delivery sound authentic.
Keep listening actively
The most common mistake is losing track of the actual question because you're reading the overlay. Stay present in the conversation first.
Pre-load context carefully
The better your resume and JD are indexed, the more specific and accurate the suggestions — and the less time you spend reading them.
Honest Caveats
The job gap problem
The copilot is invisible, but its downstream consequence is not. If you land a role you are not qualified for, the gap between your interview performance and actual capability shows up quickly. The ethical use case is using AI to communicate genuine experience — if you don't have the experience, the copilot cannot save you in the role.
Active listening failure
Some candidates get so focused on reading the overlay that they stop listening to the interviewer. They miss nuances in the question, answer the wrong thing, and look distracted. The copilot should be peripheral, not primary.
Proctored assessments are a real risk
For timed, proctored coding assessments and structured psychometric tests, behavioral AI on the platform can flag anomalies. If the platform explicitly prohibits outside aids and you use one anyway, you risk disqualification. Read the instructions.
Detection will get better
Gaze tracking AI is improving. Future high-stakes assessments may include hardware-enforced gaze monitoring. The window where AI copilots are fully invisible is probably not permanent.
FAQ
The copilot software itself is not technically detectable during a standard Zoom, Teams, or Google Meet interview. Screen sharing does not expose the Whisper Mode overlay (it uses the Document Picture-in-Picture API which exists outside the shared window boundary). Interviewers cannot see what software is running on your device. What they can observe are behavioral cues — eye movement, response latency patterns, and phrasing consistency — but these are circumstantial, not conclusive.
OphyAI's Whisper Mode uses the Document Picture-in-Picture API so the overlay never appears in screen shares. Try it free.