The Control Journal
Assessment GuidesSeptember 10, 20264 min read

Does CoderPad Record Your Screen?

CoderPad records every keystroke in the pad, not your screen. What Interview playback and Screen code playback capture, and where video, audio, and webcam stop.

CControl Editorial Team

No. CoderPad does not record your screen. As of September 9, 2026, CoderPad's documentation describes keystroke recording inside the pad, a replay of the editor, markers for pastes and lost focus, saved AI prompts, and, in some Screen tests, still webcam snapshots. It does not document screen capture, screen sharing, or a stored video of you in either product. What it keeps is a complete record of the editor, which for most purposes is more revealing than a screenshot. This article covers what CoderPad Interview and CoderPad Screen each record, and what they do not.

What CoderPad Interview records

CoderPad's playback documentation is direct: "During an interview, the Interview platform keeps track of every keystroke of every participant within a pad." The cheating prevention page for Interview lists the timeline contents: "Every pad records a complete timeline of the session, including: Code edits, Runs, Cursor movements, Copy/paste events, IDE exit notifications."

Playback becomes available when the interviewer clicks End Interview, and later from the Pads List. In it, a yellow dot marks every paste from outside the pad and an orange dot marks every time "the candidate's browser is no longer focused on the IDE," labelled with a duration such as "Clicked away for 19 seconds." A separate alert fires when a candidate copies all code in a file.

Two limits are documented. "Only code changes on the left window will be shown in the playback. Any code run in the shell (like REPL commands or package installations) will not be displayed in playback mode." And the drawing whiteboard is kept only as its end state: "You will be able to see the final state of the drawing as part of the pad playback for review," per the Drawing Mode documentation.

If AI Assist is enabled, the AI Assist documentation says "All pad users' prompts and AI output will be saved for review in playback mode."

Video, audio, and the call

A CoderPad interview can include a "Zoom-powered video or audio chat" started from the pad. The video and audio documentation says "You and the candidate have the option to accept or decline on both the Zoom video and audio permissions." It does not describe the call being recorded or stored.

The one documented audio feature is the AI Notetaker, an enterprise option. Its documentation says participants are told "the call will be recorded to transcript only (no audio/video will be stored)," that "Each individual call participant must opt into the AI Notetaker in order for their voice to be transcribed," and that either side "can stop or mute transcription at any time." So the most CoderPad documents keeping from the call is a transcript you consented to. How that compares with other interview notetakers is in whether an AI notetaker is recording your interview.

What CoderPad Screen records

Screen has its own replay. The code playback documentation states that "For programming, game, and free-text questions, Screen makes a recording of all your candidate's coding activity during a test." The timeline is color coded: "Red when your candidate pastes code," "Green when your candidate runs or submits code," "Dark grey when your candidate leaves or comes back to the test," and "Light grey to show how long your candidate spent outside of the Screen test." Reviewers can scrub it at up to eight times speed.

Screen also enforces full screen and logs monitor switches, but logging is not capture. The Screen cheating prevention documentation says an alert triggers after a 10-second grace period when a candidate exits full-screen mode or switches to another monitor. The report records that it happened and for how long. It does not show what was on the other screen.

Webcam snapshots in Screen

On enterprise plans, a recruiter can request webcam proctoring. CoderPad's candidate webcam guide explains that "occasional snapshots will be taken throughout the test. These snapshots will only capture your image and will not record any video or audio," and that they are "stored securely for a maximum of 90 days." The webcam proctoring documentation adds that "Candidates are not blocked from taking the test even if their webcam is inactive." That is a photo of you, at intervals, with your consent. It is not a recording of your display.

Screen capture versus keystroke capture

Screen captureWhat CoderPad documents
Other windows and tabsVisible in a screenshotNot captured; only the exit and its duration are logged
Code as it was writtenVisible only at snapshot momentsEvery keystroke, replayable
PastesVisible if caught in a frameMarked with content, every time
The callDepends on the toolNot documented as stored; transcript only, opt-in

The difference matters in one direction. CoderPad cannot see what you looked at while away from the pad, but it can see exactly how the code arrived once you came back. A block that appears fully formed after an orange dot is the pattern interviewers are told to ask about. For how a screen share differs when an employer uses one on top of CoderPad, see what interviewers can see when you share your screen.

What this means for candidates

Assume the editor is a full recording and the rest of your machine is not. Type in the pad rather than drafting elsewhere and pasting, keep the tab in the foreground, and if you step away, say so. If a Screen test asks for your webcam, the documentation says you can decline and still take the test; ask the recruiter what declining means for their process before you decide. For the fuller picture of what an alert leads to, read how CoderPad detects cheating. For the interview format itself, the CoderPad interview format and preparation guide covers the rest.

Continue exploring