CoderPad does not record your entire desktop or outside applications, but it does record substantial activity inside the coding environment: your keystrokes, a play-by-play replay of how you built your solution, and timestamps of when you left the editor. Whether the camera is also recorded depends on the employer's settings.
What CoderPad records
CoderPad is a technical interviewing and assessment platform. It has two products — live interviews and the automated take-home testing product, CoderPad Screen — and the recording behavior differs slightly between them.
Inside the coding pad (both products):
- Code playback. CoderPad generates a chronological replay of how the code was written, color-coding the timeline to show when you typed, ran code, pasted text, or left the test environment.
- Keystroke history. The editor records the sequence of edits rather than just the final answer.
- Tab-switching logs. The platform timestamps how much time you spend outside the testing tab.
- Copy-paste tracking. Pasting code into the editor is logged and can be flagged in the report.
Not recorded:
- Your external desktop and other browser tabs.
- Applications running outside the CoderPad tab.
Webcam (optional):
If the employer enables webcam proctoring, CoderPad Screen takes periodic snapshot photos for identity verification. It does not record continuous video or audio — the snapshots are still images used to confirm the right person is present.
Live interviews vs. Screen assessments
In a live interview, the code editor history and keystrokes are recorded, and audio/video is captured only if the interviewer turns on the call feature. In a CoderPad Screen assessment (automated take-home), code playback and tab-switching logs are standard, with webcam proctoring as an opt-in layer.
What candidates should know
Candidates commonly overestimate what CoderPad sees. The platform does not snoop on your other tabs or the rest of your screen — it tracks activity within the coding environment itself. What you type, paste, and when you leave the editor are all logged, but a PDF you have open in another window is not captured.
If webcam proctoring is required, you will be prompted to activate your camera before the test starts and will see periodic snapshot requests during the session.
Why this level of monitoring exists
CoderPad's monitoring is designed to detect cheating without the overhead of full desktop capture. Playback lets a hiring team watch how a candidate arrived at a solution — not just the result — which is a stronger signal of real skill. This sits within a wider candidate screening process: assessment signals, structured interviews, and reference checks together build a fairer picture than any single tool.
Bottom line
CoderPad records activity inside the coding pad — keystrokes, code playback, and tab-switch logs — but not your full desktop. Webcam recording is optional and, when enabled, captures periodic snapshots rather than continuous video. Check your test invitation to see whether the employer has turned proctoring on.