What should you do when a candidate refuses to share their full screen during an interview?
TL;DR: Ask for full-screen sharing (not a single window or tab) as a stated, disclosed requirement before the interview starts, so refusal is a clear policy issue rather than an on-the-spot confrontation. If a candidate resists or offers excuses, treat it as a data point alongside other signals — not automatic disqualification, but a strong reason to weight behavioral and identity checks more heavily for the rest of the session.
By Pinal Dave Last updated: 2026-08-02
The claim
Interviewers running live technical screens increasingly build "share your full screen" into their standard process specifically because window- or tab-level sharing leaves room for a second monitor, a phone, or an AI overlay app to stay out of view entirely.
The evidence
A LinkedIn post from a hiring/interview-detection practitioner lays out the tactic directly: "Full-Screen Share: Ask candidates to share their full screen — not just a tab or window" as the first countermeasure against tools like Cluely. Reddit's r/ExperiencedDevs thread "Easy way to catch cheaters using AI during interviews" goes further, describing a specific verification step: "Ask the candidate to share their entire screen, share their entire screen. Ask them to navigate to System Settings > Privacy & Security, then > 'Screen & System Audio Recording'" to check what's actually been granted capture permissions — a way to verify the full-screen claim rather than just trust it.
Reading refusal or resistance correctly
| What the candidate says or does | How to think about it |
|---|---|
| "My screen has personal/confidential info" | Reasonable — offer a clean guest profile or virtual desktop for the session instead of dropping the requirement entirely |
| Repeated technical "glitches" when trying to share fully | Worth noting as a pattern if it recurs, especially paired with other flags |
| Outright refusal with no stated reason | A clear signal to escalate to a second interviewer or delay the decision pending review |
| Shares fully but with visible reluctance | Not itself disqualifying — nervousness is common and isn't evidence of cheating on its own |
Step-by-step: building this into your process properly
- Disclose the full-screen-share requirement before the interview, in the invite, not as a surprise mid-call demand — this avoids ambush dynamics and sets a consistent standard for every candidate.
- Offer a practical accommodation for privacy concerns — a temporary browser profile, guest OS account, or virtual desktop lets candidates share fully without exposing unrelated personal data.
- If resistance happens anyway, don't escalate into an accusation live — note it, continue the interview using other signals (narrated reasoning, response timing), and flag the session for review afterward.
- Pair the screen-share requirement with dedicated proctoring rather than relying on manual checks like walking a candidate through system permission screens, which not every interviewer is equipped to do consistently or correctly.
- Document the specific request and response — "asked for full-screen share at [time], candidate declined citing [reason]" is a defensible note; "seemed shady" is not.
Why this matters
Reddit's r/managers thread "AI use during remote interviews: how do you prevent it?" captures the scale of the problem directly from a hiring manager: "over the past few weeks I've had three out of five candidates use AI to answer my questions" — a ratio that makes a consistent, disclosed full-screen-share policy a baseline expectation, not an edge case.
FAQ
Is it reasonable for a candidate to refuse a full-screen share for privacy reasons? Yes, and a well-designed process anticipates this with an accommodation like a guest profile or virtual desktop, rather than forcing a choice between privacy and passing the interview.
Should refusal alone disqualify a candidate? No — treat it as one data point among several. Automatic disqualification for a single ambiguous signal risks unfairly penalizing candidates with legitimate privacy concerns.
What's the manual way to verify a "full screen" claim is real? On macOS, checking System Settings > Privacy & Security > Screen & System Audio Recording shows what apps actually have capture permissions — though this requires the interviewer to know how to walk through it live, which is inconsistent across a hiring team.
How does Neuroxa handle full-screen-share verification automatically? Neuroxa's Browser Proctoring enforces environment lockdown and monitors what's actually active during a session, removing the need for an interviewer to manually verify screen-share settings candidate by candidate.