Yes, in the one way that survives the interview: CoderPad's playback marks every moment the pad lost browser focus, and those marks sit on the same timeline as your keystrokes and your runs. Anyone with the link can scrub back to a gap, see how long it lasted, and watch what appeared in the editor the second it ended. What the marker cannot say is where you went, because the browser event behind it carries no destination. And CoderPad has no view of your machine beyond its own tab, unless you are the one screen sharing.
Most write-ups stop at the live interview, where a human is already watching your caret move. Playback is the part that outlives the call: a replayable artefact attached to the pad, openable by someone who was never in the room, and on an asynchronous pad often the only thing a reviewer looks at.
The three layers stacked on one timeline
Playback is not a video and not a diff. It is a reconstruction of the pad rebuilt from the events it recorded, which is why it can be scrubbed to any second and why it shows things a finished file cannot.
The edit history, at keystroke resolution
Your solution reassembles itself at the speed you typed it. The reviewer sees the order you built things in, not the tidy final order: the helper you wrote first, the variable renamed twice, the twenty seconds the caret sat still before you saw the trick, the block you deleted. They also see the opposite shape, forty finished lines appearing in one frame with no typing in between.
Every run, with the output it produced
Each time you hit run, that execution and its result are pinned to the timeline where it happened. This is the layer candidates forget exists. The failing test you fixed quietly, the stack trace you never mentioned, the five runs in ninety seconds while you guessed at an off by one, all replayable beside the code as it stood at that instant.
Markers wherever the pad lost focus
Focus losses appear as their own marks along the timeline, rendered in orange in the interface, each with a start point and a duration. Clicking one jumps the replay to it. That placement is the whole point: a gap is never read on its own, it is read together with the code that arrived immediately after it.
Exact labelling and colouring depend on the CoderPad version and the plan the hiring team is on, so treat the orange marks as the current shape of the feature rather than a fixed contract. The signal underneath is stable: the browser's own visibility and focus events, recorded with timestamps.
A worked example: two identical solutions, two very different replays
Two candidates finish the same string parsing question with near identical final code. Here is what the scrubber shows.
- 00:00 to 04:10, both. Reading, a few clarifying comments typed into the pad, a first naive loop.
- 04:10, candidate A. A ninety second focus gap. When it ends, typing resumes at the same pace as before, on the same naive loop, which then gets refactored over six minutes with three runs and two failing outputs along the way.
- 04:10, candidate B. A four minute focus gap. When it ends, thirty two lines of a correct sliding window appear in one frame, followed by a single run that passes first time, then nothing.
- Final state, both. Working code, similar structure, similar length.
Nothing in the playback says candidate B did anything. The marker holds no URL, no window title and no screenshot. What it does is place a four minute absence directly against a burst of finished code that never failed once, and reviewers react to that shape even when they cannot name it. Candidate A's gap is longer than a notification, but the work either side is continuous. Duration on its own decides very little. Adjacency decides a lot.
The dev console counts, and so do four other innocent things
The surprise for engineers is that opening developer tools registers as a focus loss. Docked or undocked, the tools take the keyboard away from the document, so the pad receives the same event it would receive for a second tab. A front-end candidate who reflexively hits F12 to read why a fetch is failing leaves a marker on the timeline while never actually leaving the page.
The habit that produces the marker is the habit you want in a hire. In playback it looks identical to the habit you do not.
The same goes for a chat notification that steals focus, a password manager popup, the machine locking itself, and clicking a second monitor while the pad stays fully visible on the first. None arrive labelled as innocent, and playback cannot tell them apart. In a live pad the fix is verbal: say what you are doing before you do it, because a gap announced in advance carries no information.
| Question a reviewer might have | Can playback answer it? |
|---|---|
| When did they stop typing, and for how long? | Yes, to the second |
| What did the code look like at any given moment? | Yes, scrub to it |
| What did their third run output? | Yes, runs and results sit on the timeline |
| Did a large block arrive all at once? | Yes, this is very visible in replay |
| Which tab or app did they switch to? | No, the browser event has no destination |
| What was on the rest of their screen? | No, the pad holds no screen recording |
| What did they type in another window? | No, the pad records only itself |
| Was anyone else in the room with them? | No, playback has no camera |
Where CoderPad's view genuinely stops
This is the half that gets overstated in both directions online. CoderPad is a web application running in a browser tab. It has no operating system level access to your computer: it cannot enumerate your running applications, read other windows, list your open tabs, capture your desktop, see a second monitor or inspect your clipboard history. It knows its own tab gained or lost focus, and it knows what entered the editor.
The exception is screen sharing. If the round runs on a video call and you share your screen, everything inside that share is visible and, where the team records the call, recorded. That stream belongs to the meeting tool, not the pad, and is not part of playback. Two separate records can exist from one interview, with different retention and different audiences.
Where OfferPilot AI is the wrong tool
Worth stating plainly on a page published by a company that sells an interview assistant. The OfferPilot overlay is excluded from screen capture at the operating system level, so it does not appear in a Zoom, Teams or Meet share, in a recording, or in a screenshot. That property is irrelevant to everything on this page. Focus detection never looks at pixels. It reads which window the operating system considers focused, so clicking any overlay, or firing the Code Copilot capture shortcut, moves focus off the pad and produces the same marker anything else would. Capture exclusion also does nothing against webcam monitoring, a lockdown browser, eye tracking, a second device camera or a proctor sitting beside you.
There is a second reason a shared pad is the wrong venue. Playback records how the answer was built, so a solution you cannot rebuild, defend and extend on request reads worse than an honest partial one you wrote yourself. The realistic use of an assistant here is before the round rather than during it.
Making your playback read the way your work actually went
- Narrate anything that moves focus, the console included. One sentence beforehand turns a marker into a non event.
- Keep the pad on one screen and put nothing you will click on the other, since a click over there blurs the pad even though it never leaves your view.
- Type your scaffolding rather than pasting it. Text typed by hand replays as typing, the same text pasted from a notes app arrives in one frame.
- Run early and run often. A trail of failing then passing runs is good evidence of a real debugging process, and it is all on the timeline.
- Mute notifications before you join. Every toast that steals focus is a mark someone may scrub to later.
If your next round is a conversation rather than a shared editor, that is the format Interview Copilot is built for, on Windows 10 and 11, free for five minutes a day with no card. Terms are on the pricing page.