An undetectable interview screen — explained, not just claimed

The mechanism, not just the claim

"Undetectable" gets used loosely across this whole product category. We'd rather name the actual mechanism: Windows lets an application exclude one of its own windows from every screen-capture surface the operating system services, via an API called SetWindowDisplayAffinity with the flag WDA_EXCLUDEFROMCAPTURE. Set it, and the window renders normally on your own monitor while disappearing from Zoom shares, Teams recordings, Google Meet, Webex, and tools like OBS Studio — all of which read from the same OS-managed capture surface. We've written a full technical breakdown of how this actually works, with the exact API signature.

Why this is verifiable, not just a promise

This is a real, Microsoft-documented API — you can go read the reference yourself, rather than trusting a vendor's word for it. That's the whole point of explaining the mechanism instead of just asserting the outcome: a claim you can verify is worth more than one you have to take on faith.

What it doesn't cover — stated plainly

• It doesn't hide the running process from Task Manager — the process is visible under its own name, though InterviewPilot runs under a neutral process name rather than announcing itself.
• It has no effect on audio — whatever your microphone picks up is transmitted normally.
• It doesn't defend against a physical camera pointed at your monitor — this is a software compositor feature, not a hardware one.
• It's Windows-only — there's no equivalent API on macOS or Linux.

None of this changes whether you can explain your own answer if asked a follow-up question — see our post on how interview cheating detection actually works for why that's the part that matters most, independent of any screen-capture mechanism.