Does CodeSignal use your webcam?

Only when proctoring is enabled on that assessment. Where it is, your browser asks for camera permission during setup, the camera indicator light comes on, and the platform captures stills of you through the test rather than a continuous film. If you were never shown a camera permission prompt and never saw a preview of yourself, no webcam capture is running.

Does CodeSignal record your screen?

Screen capture is a separate setting from webcam capture and is not present on every CodeSignal test. Where a test does capture your screen, the browser shows an explicit share prompt naming what will be shared, and most browsers keep a visible sharing indicator for the whole session. No screen capture starts silently inside a browser tab without that prompt.

Can CodeSignal detect tab switching?

Yes, when activity logging is enabled. The assessment page records that its window or tab lost focus, at what time, and for how long, and the employer's report shows those events. It does not record what you switched to. CodeSignal cannot read your other tabs, name the application you opened, see a second monitor, or see your phone.

Do you need an ID for a CodeSignal assessment?

Certified Assessments include an identity step before the timer starts, normally a webcam photo of your face, and in some flows a photo of a government ID held up to the camera. Company-built assessments frequently skip this entirely. Where an ID is required the invite or the setup screen says so in advance, so read the invite rather than finding out at start time.

Does hiding a window from screen capture defeat CodeSignal proctoring?

No. Screen-capture exclusion removes a window from screen-share streams, recordings and screenshots taken on your own machine. It does nothing about a webcam pointed at your face, nothing about paste events, focus events or code replay logged inside the assessment page itself, and nothing about a locked-down test environment. Treating it as proctoring evasion is a misreading of what it does.

Is CodeSignal Proctored? Camera, ID, Screen and Tab Rules

Q: Is CodeSignal proctored?

It depends which assessment you were sent. CodeSignal Certified Assessments, the ones that produce a score you can share with several employers, are proctored by default and include an identity photo, webcam capture and full-screen enforcement. An assessment a single company builds and sends itself is configurable, and proctoring can be switched off entirely. The setup screens before the timer tell you which one you have.

It depends which CodeSignal assessment landed in your inbox, and you can work that out before the timer starts. A Certified Assessment, whose score you can send on to several employers, is proctored by default: identity photo, webcam capture, full-screen enforcement, activity logging. An assessment a single company built and sent itself is configurable, and plenty go out with proctoring off. The setup screens do the telling. No camera prompt means no camera.

Three products, three different answers

CodeSignal is not one test, and the answer differs for each thing carrying the name.

	Certified Assessment	Company-built assessment	Live interview
Who sets the rules	CodeSignal, identically for everyone. The General Coding Assessment is the best known	The employer, per test, from a settings panel	The interviewer on the call
Proctoring	On by default. The score is portable, so it must be trustworthy to a company that never watched you take it	Optional. Anything from nothing at all to webcam plus full screen plus activity logging	A person watches the session directly
Identity step	Yes. A webcam photo before the clock starts, and in some flows a government ID held to the camera	Usually absent unless the employer enabled it	You are on camera with a human
How you can tell	The invite names it, and setup will not proceed without a camera	Watch for the camera prompt and the jump to full screen	It was scheduled with a person

The pre-test sequence, click by click

Setup runs in a fixed order, and every screen is evidence about how the test is configured. Read them rather than clicking through.

The assessment card, before you open anything

The invite and the dashboard card carry the assessment name, the duration, the task count and, on proctored tests, a statement of the proctoring requirements. It is the one screen you can read days early. If a camera is required, sort that out now, not at start time.

The instructions and rules page

Untimed. It lists the languages available and what you may consult. Certified Assessments generally allow official language documentation while forbidding outside help of any kind; company tests vary widely. This page, not a forum post about someone else's test, is the authority on yours.

Identity capture

Where enabled, you take a webcam photo of your face, and in some flows a second photo of a government ID held to the camera. Both are stored against the session. The step exists so a score can be attributed to a person, which is why portable Certified Assessments include it and one-off company tests usually skip it.

Browser permission prompts

The browser, not CodeSignal, asks for camera access, and asks separately for the microphone where audio is captured. Your camera light comes on and stays on. This is the most reliable signal in the flow: a camera prompt alone means no audio, and no prompt at all means no webcam capture. Declining on a proctored test stops you continuing.

Full-screen enforcement

Proctored assessments push the tab into full screen and log every exit with a timestamp and a duration. Leaving full screen usually gives a warning and a logged event rather than instant termination, but a test can be set to end the session, and the rules page says if yours is. This is a browser mechanism, not an operating-system lockdown.

Start, and the clock

Setup normally sits outside the timed portion, so identity and permissions do not eat your budget. Do not assume it. The timer on screen is the authority, and once it moves, everything below is recorded.

What the report can carry once the clock is running

Proctoring is not one switch but a set of independent logs, each recording something narrower than candidates assume.

Signal	What it literally records	What it cannot tell anyone
Window and tab focus	Each time the assessment window stopped being the active window, with a timestamp and a duration	What you switched to. Not the application, not the other tab's contents, not a second monitor, not your phone
Paste into the editor	That content arrived in one event rather than as typing, with a timestamp, and in many configurations the pasted text itself	Where the text came from. A helper you wrote in task one and something fetched elsewhere look identical until a human reads it
Time per task	Minutes attributed to each task, and the order you moved between them	Whether those minutes were thinking, debugging or staring out of the window
Code replay	The build-up of your solution, so a reviewer can play back how it was written rather than only read the final state	Intent. A fast, confident coder and a rehearsed one look alike. The signal candidates most often forget exists
Webcam stills	Images of whoever sits in front of the camera, taken at intervals	Anything outside the camera's cone. Not your desk, not a screen behind the camera, not the room at your back
Code similarity	How close your code sits to other submissions and to known public solutions	Copying. Standard problems have canonical answers that honest candidates converge on

How these reach the employer has shifted over the years. Older CodeSignal material surfaced them partly as an aggregate suspicion indicator; newer presentations lean on individual flags. Trust the mechanism over the label, since the logs outlast the dashboard around them.

They combine, and that is where a review turns. The shape that gets escalated looks like this: twenty-two minutes on task two, then task three finished in four; one paste of forty lines at minute fifty-one; a replay showing that solution arrive whole, no failed run, no exploratory print. Any one alone is noise. All three on one timeline is a conversation, and usually that conversation is a request to walk through your solution live rather than a silent reject.

Where OfferPilot AI is the wrong tool for this

Worth being blunt, because the query that brings people here is often a different question underneath. Code Copilot is a Windows 10 and 11 desktop overlay that reads a problem off your screen and returns a solution with the intuition, a dry run and the Big-O analysis. Its window is excluded from screen capture at the operating-system level, so it stays out of Zoom, Teams, Meet, OBS and screenshots. That guarantee is narrow. Here is where it stops.

It touches no signal in the table above. Capture exclusion hides pixels from a screen-share stream. It has no effect on focus events, paste events, per-task timings, code replay or similarity checks, all of which are logged inside the assessment page.
It does nothing about a webcam. The camera points at your face, not your display. Same for a lockdown environment, an invigilator in the room, eye tracking, or a phone propped up as a second camera. None of those are screen capture.
A proctored Certified Assessment is the clearest case to leave it out of. The whole value of that score is that a company which never watched you take it can trust it. Treat the tool as unavailable there.
It is Windows only. No macOS, no Linux, no mobile, no browser extension. On a Mac there is no decision to make.

The honest use is before the assessment window opens. Working timed problems against something that explains the intuition and the complexity, rather than handing over an answer, is what makes a replay read like fluency. For the interview that follows a passing score, the company Q&A generator builds a bank for that firm and role.

The sixty-second check before you click Start

Read the invite for the words "Certified Assessment". If they appear, assume full proctoring.
Watch for a camera prompt during setup. No prompt, no webcam capture.
Watch for a separate microphone prompt. Camera alone means no audio.
Watch whether the tab jumps to full screen at start. That is the enforcement switch, and exits are logged.
Read the rules page for what you may consult, and whether leaving full screen warns or ends the test.

Five checks, all observable, all before the clock. Far better than guessing from a forum thread about a different employer, because two tests on this platform can be configured nothing alike.

Is CodeSignal proctored, and how do you tell before you start?