CodeSignal does not say that it does. Its help centre and product pages describe a proctored session as camera, microphone, screen recording and a government photo ID check. None of those pages names eye tracking, gaze detection or where your eyes go on screen.
The question comes up because the webcam runs for the whole session, and CodeSignal does not publish how its reviewers or its AI read the video.
What CodeSignal says a proctored session captures
The help centre article on proctoring says CodeSignal prompts you to "share your camera, microphone, and screen for the duration of the assessment" and to show a government-issued photo ID.
The cheating and fraud page on codesignal.com describes the same capture as recording "video, audio, and screen activity for the entire assessment session."
Proctoring is not on every test. CodeSignal says some assessments include it, and candidates see whether theirs requires it in the Assessments section before the assessment starts.
What the review checks, and who runs it
After you submit, the recording goes to what CodeSignal calls its proctoring verification team. The help centre lists three things that team checks: that camera, microphone and screenshare stayed shared for the whole evaluation, that the ID is valid, unexpired, and carries your full name and photo, and that you observed all the rules shown in the evaluation instructions.
The product page describes evaluation through "multi-agent analysis, with human reviewers validating flagged activity and final decisions." CodeSignal's blog calls it "a blend of multiple AI reviews and human oversight."
That same article says identification and proctoring data is reviewed by CodeSignal only, "stored and deleted within 15 days," and not shared with the company that requested your report. The company receives "a copy of your assessment result and score."
Why a session comes back not verified
CodeSignal tells employers it verifies a proctored result "within 1-3 business days" and marks it verified or proctoring rejected.
The listed reasons are specific: not being alone in the room, getting up and leaving the camera's view, using other devices, using an external IDE, and searching online beyond syntax help. Gaze is not on that list.
Proctoring also does not change your score. The help centre states that "proctoring has no impact on the score you receive."
What candidates report
In an r/leetcode thread from October 2026, a candidate asked whether their eyes moving between the question and the code editor could get them flagged. One reply said reading the question and then looking down to type is "normal behavior and every test taker does it." Another said "the things people usually get flagged for are leaving the window or pasting big chunks of code."
Candidates in r/csMajors report that CodeSignal stopped showing them their own verification outcome. One wrote it used to arrive by email and appear in the interface, and "now you can't anymore."
If a rejection looks wrong, send CodeSignal Support the session details, then tell the recruiter a review is under way.
How employers should read a CodeSignal rejection
A proctoring rejection means CodeSignal did not certify the session after reviewing the recording and the ID. The rejection reasons CodeSignal lists do not include where the candidate looked. CodeSignal publishes no accuracy or false-positive figure for its reviews, so the stated reason is the evidence you get.
Ask which rule the reviewer cited and when it happened, then watch that segment. A candidate who stood up once is a different case from one found with another person in the room.
A verified or rejected CodeSignal session is one input in AI Candidate Evaluation, and a single rejected assessment should inform that decision rather than settle it.