What CodeInterview Can and Can't Detect in 2026

When you open a CodeInterview session, the platform spins up a sandboxed web page that runs the coding problem and the surrounding UI. Behind the scenes, a few JavaScript hooks and optional webcam/mic streams collect signals that help the test administrator enforce integrity. Below is a plain‑language rundown of what the platform can actually observe, what it cannot, and how you can respect the rules without getting tangled in speculation.

How CodeInterview Monitors Browser Activity

Tab focus and visibility

The test page includes a visibilitychange listener. When you click away, the browser fires a document.hidden event and the platform logs a timestamp. In most deployments, the test will flag a focus loss if you leave the tab for more than a few seconds. The log is usually displayed to the proctor or used in a post‑test audit.

Tab switching and navigation

If you open a new tab within the same browser window, the original test tab still receives the visibilitychange event. However, the platform cannot see the URL of the new tab unless the test explicitly asks for it via a custom extension, which is rare. In most public CodeInterview offerings, the only thing recorded is the fact that you switched away, not what you visited.

Copy‑paste detection

A small script intercepts copy, cut, and paste events inside the code editor. When you paste, the platform captures the length of the pasted text and the time it occurred. This is useful for spotting bulk pastes that might indicate cheating, but it does not block the paste itself. If the test instructions allow you to use external resources, you can safely copy‑paste as long as you stay within the allowed time windows.

Proctoring Features: Webcam, Microphone, and Screen Capture

Webcam and microphone streams

When a test requires live proctoring, the platform asks for permission to access your webcam and microphone. The video feed is streamed to a monitoring dashboard, where a human or AI reviewer watches for suspicious behavior (e.g., another person in the frame). The audio is typically recorded for later review. Neither stream captures keystrokes or application windows.

Screen recording (optional)

Some enterprise customers enable a screen‑recording extension that captures the content of the test tab only. This extension cannot see other windows or tabs, and it stops recording the moment the test page is closed. If you see a prompt asking for screen‑share permission, the extension is active; otherwise, the test relies solely on the focus‑loss logs.

What is not recorded

• Keyboard events: CodeInterview does not log individual key presses unless a custom proctoring tool is added, which is disclosed in the test instructions.
• Background applications: The platform has no visibility into other programs running on your machine.
• Network traffic: There is no built‑in network sniffing; the test cannot see which sites you visit outside the browser.

Typical Use Cases and What Triggers Alerts

The platform does not automatically disqualify you for a single focus loss or a small paste. Instead, reviewers look for patterns that suggest a breach of the test policy.

How to Stay Within the Rules

1. Read the test instructions carefully – Every CodeInterview deployment can have its own allowance for external resources. Some companies explicitly permit open‑book coding; others forbid any outside help.
2. Keep the test tab in front – If you need to glance at documentation, open it in a new window before the test starts and keep the test tab active. The focus‑loss timer resets each time you return.
3. Use copy‑paste deliberately – When you paste code, be ready to explain why you did so. A brief comment in the editor can help reviewers understand that you are reusing a known snippet.
4. Maintain a clean webcam view – Position your camera so only you are visible, and avoid backgrounds that could be misinterpreted as additional participants.
5. Practice aloud – Rehearsing your story about a project helps you stay concise and grounded in your resume. Tools like Call Assistant can simulate the interview flow, letting you practice delivering answers without adding extra visual clutter.

Common Misconceptions

• “CodeInterview watches my whole desktop.” The platform only sees the test tab unless a screen‑recording extension is explicitly installed, and even then it records that tab alone.
• “If I copy‑paste, I’m automatically disqualified.” Paste events are logged, not blocked. The key is whether the paste aligns with the test’s policy.
• “The webcam can hear everything in the room.” The microphone feed is captured, but it is used mainly to verify that the candidate is speaking. Ambient noise is not flagged unless it masks the candidate’s voice.
• “Proctoring AI can read my mind.” AI reviewers can detect obvious anomalies (multiple faces, long focus losses) but cannot infer intent beyond the data they receive.

How to Practice This

1. Run a mock session – Use a free coding sandbox, enable the browser‑focus logger, and intentionally switch tabs. Observe how the timer behaves.
2. Record yourself – Set up a webcam and practice solving a problem while speaking your thought process. Review the footage for any accidental background movement.
3. Use Call Assistant for rehearsal – Have the assistant prompt you with typical interview questions, then answer aloud. This builds fluency and keeps your narrative tied to concrete resume points.

---

FAQ

• Q: Does CodeInterview capture my clipboard contents? A: No. It only logs that a paste occurred and the length of the pasted text. The actual clipboard data remains private.

• Q: Can I use a second monitor for reference material? A: Yes, as long as the test tab remains the active window on the primary screen. Focus‑loss logs only trigger when the test tab itself loses visibility.

• Q: What happens if my webcam freezes for a few seconds? A: A brief interruption is usually tolerated, but repeated gaps may be flagged for review. Keep your camera steady and avoid covering it.

• Q: Are there any legal concerns with the data CodeInterview collects? A: The platform’s privacy policy outlines what is recorded and how it is used. In most jurisdictions, the collection is permissible when candidates give explicit consent before the test begins.