CoderPad cannot see a screenshot you take on your own machine. Nothing in CoderPad Interview or CoderPad Screen captures your desktop or reads your operating system's screenshot activity, and the company's documentation lists no such feature. What it records is activity inside the pad: edits, runs, pastes and the moments your browser stops focusing on the editor.
What Interview records
CoderPad's Interview documentation says the platform keeps track of every keystroke of every participant within a pad. After the interviewer clicks End Interview, playback opens with a separate track per participant showing edits and runs.
Pasting content from outside the editor puts a yellow dot on the playback bar labelled "Code pasted", and the docs note that even copying from CoderPad's own AI Assist tab triggers it. Leaving the editor puts an orange dot where the candidate's browser is no longer focused on the IDE.
CoderPad alerts interviewers while the session runs too: an external paste or a departure from the IDE, tab switching included, shows up live.
What Screen adds
Screen is the asynchronous test product and carries more instrumentation. Its docs list automatic detection for plagiarism against earlier submissions, difficult questions finished in a fraction of the usual time, leaving the test environment, copy and paste, and geolocation changes.
Copy and paste blocking can stop text from outside the IDE entirely. Full-screen mode can require candidates to enter full screen before starting; exiting it or switching to another monitor triggers an alert after a 10-second grace period.
Webcam proctoring is a separate Enterprise option. It takes periodic snapshots, and CoderPad's AI analysis flags no face, multiple faces or a different face in the frame.
Why a screenshot stays outside CoderPad's reach
Browser screen capture requires an explicit user prompt even when a site is allowed to request it, as MDN documents, and CoderPad's candidate flow does not ask for that access. A screenshot shortcut handled by Windows or macOS never passes through the tab, so there is no event to log.
CoderPad does not publish any screenshot detection capability. Interviewers on Reddit describe the same boundary. One who runs CoderPad screens wrote that the platform uses "window loses focus" as its cheat detection mechanism.
CoderPad knows you left and when you came back. It does not know what you looked at.
What candidates should assume
Assume the timeline gets reviewed. A pasted block from another window leaves a marked event, and a long gap with no edits followed by a complete solution reads badly.
Type in the pad where you can. If you draft elsewhere first, expect a paste event and be ready to explain it. Do not switch monitors during a Screen test with full-screen mode on. Treat the webcam as live if the employer enabled it.
For employers reading the flags
A flag is a prompt to ask, not a verdict. CoderPad recommends treating alerts as prompts for clarification rather than immediate disqualification.
Candidates report that accessibility tools and notification popups register as leaving the environment, so one focus loss means little. Look at the pattern: pastes clustered around a single question, time away that lines up with a suddenly finished solution, or a candidate who cannot explain the code they submitted.
For the scoring that sits alongside that playback, see AI Candidate Evaluation. For other platforms, see whether Proctorio detects cheating, whether HireVue can detect cheating, and how HackerEarth's proctoring layers differ from CoderPad's in-tab signals.