Screen share is not the same as screen truth.
Overlay tools use the same display-affinity APIs that legitimate apps use to protect DRM content. Point it at an interview and the candidate reads generated answers the interviewer will never see in the shared feed.
A normal code editor, browser, or video call. Nothing unusual.
An overlay with generated answers, hints, or talking points.
Omits protected or capture-excluded windows by design.
Flags windows configured to be excluded from capture, or tied to known overlay tooling.
Read the window flags, not the pixels.
On the fast 2-second loop, the overlay detector inspects the display-affinity of on-screen windows. A window marked to be excluded from capture is exactly what an interview overlay needs, and exactly what InterviewWatch reports.
The capture API hides the overlay from screen share on purpose. The agent reads the window's display-affinity flag directly, so it can't.
Capture exclusion
Detects windows configured to avoid screen capture, a defining trait of overlay-based assistance tools.
Known overlay processes
Cross-references windows and processes against a remotely updateable catalog of interview overlay tools.
Contextual severity
An overlay active during a live answer is treated as critical; a harmless background app is scored differently.
Overlay detection questions, answered.
What is a hidden interview overlay?
How does InterviewWatch find overlays screen share cannot see?
Is an overlay always cheating?
See the windows screen share is built to hide.
Add capture-exclusion detection to your live interviews and close the biggest blind spot in remote hiring.
Try nowSee AI tool detection