Is Codility Proctored? What Codility Records and Flags

What Codility can see at all

• Pastes into the IDE, with the pasted code stored and readable
• Tab switches away from the Codility browser tab
• Time spent on each task, against the expected duration
• Attempts to copy the task description
• Typing patterns, as a preview feature
• Webcam snapshots at intervals and on flagged events
• Your screen, as snapshots or a continuous recording, when enabled
• The presence of known cheating tools, when Device Integrity is enabled

Three layers, all optional, all chosen in advance

Codility's own summary of its integrity features names three controls: Proctoring, AI Follow-Up Questions, and Device Integrity. All three are configured per test, and Codility is explicit that proctoring is disabled by default and can only be enabled before the first candidate is invited — an existing test with candidates has to be duplicated first.

That has a useful consequence for a candidate. Whatever is watching you was decided before your invitation was sent, and the signals on your report are only the ones selected at that moment. It also means the answer to "is Codility proctored" is genuinely per-invitation.

Behavioural events, then multimedia

The base layer looks at what you did rather than at you. Codility tracks pastes into the IDE and logs the pasted code in the report's Timeline; tab switches away from the Codility tab; unusually fast task completion; attempts to copy the task description, which it names as a common signal of AI tool use; and, in preview, typing patterns.

The multimedia layer is separate and stacked on top. Webcam capturing takes snapshots at intervals and on flagged events, kept 30 days. Screen proctoring records the screen, as periodic snapshots or as a full recording. Test session recording is the maximum setting: screen, webcam and microphone for the entire session, with a required opt-in and a visible recording indicator next to the timer.

All of it feeds an Integrity Risk score presented as None, Low, Moderate or High, drawn from identity and network verification, behavioural signals and plagiarism checks. Where signals are disabled, Codility says the score is calculated from whichever remain.

Device Integrity, and why Codility built it

Codility is unusually direct about the reason this feature exists. Its integrity overview describes a growing category of AI tools that run as hidden desktop applications feeding candidates answers in real time and are built to be invisible to screen sharing, and states the problem in one line: proctoring cannot catch what it cannot see.

The answer it shipped is the Codility App, a lightweight desktop application for macOS and Windows that checks the device for known cheating tools. Detections appear in the integrity widget on the report alongside copy-paste and tab activity. On a Screen assessment with Device Integrity enabled, Codility says the candidate must install the app and cannot complete the assessment in a standard browser.

Codility also draws the boundary itself: the app checks only for the presence of known cheating tools, and does not record the screen, monitor keystrokes, or collect personal data beyond what the standard assessment already collects. It is a Preview feature and does not support Linux.

What is recorded, and what is only flagged

An artefact a reviewer can open later is a different thing from an event counted on a report, and both are different from an action the platform simply prevents. Every control Codility documents, tagged and sourced:

What Codility's documentation does not say

The gaps are as useful as the features, and they are the part nobody else writes down. Where Codility states a limit, it is quoted below. Where it is silent, the entry says it is silent — undocumented is not the same as absent, and we are not going to present it as one.

• Proctoring is off unless someone turns it on. Codility states it is disabled by default and configured per test, and that it can only be enabled before the first candidate is invited — an existing test has to be duplicated first.
• The Codility App is narrower than it sounds. Codility states it checks only for the presence of known cheating tools, and does not record the candidate's screen, monitor keystrokes, or collect personal data beyond what the standard assessment already collects.
• Device Integrity does not run on Linux. Codility says the app is available for macOS and Windows only, and the feature is in Preview.
• Codility does not treat its own signals as verdicts. Its documentation says not all behavioural signals on their own indicate cheating, and that the responsibility for the determination lies with the recruitment team.
• Video proctoring is not silent. Candidates see a disclosure on the intro page, must enable audio and video recording before starting, and see a recording indicator next to the time remaining.

What candidates get wrong about Codility

Most candidates assume a Codility test is a plain browser tab with a timer, and most of the time they are right — proctoring is off by default. The mistake is assuming that generalises. A test with the full stack enabled records screen, webcam and microphone for the whole session, and you will know because you have to opt in and a recording indicator sits next to the clock.

The second mistake is ignoring the intro page. Codility gives recruiters an Assessment and Hiring Policies field precisely so the rules can be stated, and it renders in the Before You Begin section. That text is the rulebook your report will be read against.

The third is misreading Integrity Risk. It is a composite of identity checks, behavioural signals and plagiarism comparison — not a cheating verdict — and Codility says explicitly that the determination is the recruitment team's to make, with a follow-up interview as the recommended next step when something is unclear.

The fourth is not knowing Device Integrity exists. It is new, it is in Preview, and where it is switched on for a Screen assessment there is no browser route at all: the assessment runs inside Codility's own desktop application.

Worth knowing before you sit down

• Codility tells recruiters to state their expectations in an "Assessment and Hiring Policies" section that appears in the Before You Begin part of your intro page. Read it — it is where the rules for your specific test are written down.
• The number of signals on your report depends on what was enabled when your invitation was sent, not on what Codility offers in general.
• If screen proctoring is on, you are expected to have only one monitor active and an up-to-date browser, or the feature will not trigger.
• Webcam snapshots are kept for 30 days; the recruiter can expand and review the captured images in the report.
• AI Follow-Up Questions can appear after a take-home submission: three questions generated from your own code, two minutes each, with copy-paste prevention and keystroke monitoring during your answers.
• Where Device Integrity is enabled on a Screen assessment, you must install the Codility App — there is no browser fallback.

What this means if you use an AI assistant

Codility is the platform that has written the honest version of this section for us. Its own documentation says that hidden desktop assistants are built to be invisible to screen sharing, that proctoring cannot catch what it cannot see, and that this is why it built a device-level check instead. Anyone weighing up assistive software should read that paragraph on Codility's site before deciding anything.

That reframes the whole question. Screen and video proctoring capture pixels; Device Integrity does not look at pixels at all. It is a native process asking the operating system what is installed and running, and no screen-capture behaviour is relevant to it. We cannot tell you what any particular version of that check finds, and we will not pretend to.

Where Device Integrity is not enabled, the failure mode is the familiar one: a full-session capture of your screen, plus a webcam pointed at your room, plus a microphone. Those are three independent channels and screen-capture behaviour speaks only to the first.

The behavioural layer is indifferent to all of this. Time-to-solve, pastes, task-description copying and typing patterns are inferences from what happened in the editor, and they land on a report whether or not anything was ever captured visually.

Stealth Interview's documented behaviour is that it is a desktop app for macOS and Windows and is not captured by screen-sharing or meeting software. Codility's documented behaviour, in Device Integrity mode, is a desktop check for known tools. Those are two honest statements about two different layers, and neither of them is a claim about the other.

Codility proctoring: common questions

Sources

Every page below is published by Codility or its parent company. Last checked in August 2026; vendors change these features often, so check the date on the page you land on.

• Codility — Proctoring: Behavioral Events Detection
• Codility — Screen Proctoring
• Codility — Video Proctoring
• Codility — Device Integrity for Screen
• Codility — Assessment Integrity Features
• Codility — Device Integrity for Interviews

Product home: Codility

Other platforms you may be facing

• Every platform in this cluster — assessments, live coding tools and meeting software, side by side.
• The blog — how the technical interview loop is actually scored.
• AI interview assistant — what Stealth Interview does during a live interview.