Articles

CodeSignal Score Not Verified: What It Means, Common Causes, and What to Do Next

Learn what CodeSignal Not Verified means, common proctoring causes, what employers see, and the exact steps to contact support and request next steps.

Updated August 20, 2026.

You finished a CodeSignal assessment, received a coding score, and expected the result to move forward. Instead, the status changed to Not Verified or Proctoring Rejected.

That message is alarming, but it needs to be read precisely. A CodeSignal result can be technically scored and still fail the separate proctoring verification process. The status does not automatically explain the cause, prove intentional misconduct, or guarantee that the hiring company will offer another attempt.

This guide explains what CodeSignal score not verified means, the common causes listed in CodeSignal's current documentation, what the employer may receive, and the steps to take next.

Quick answer: What does CodeSignal Not Verified mean?

Not Verified means CodeSignal did not certify a proctored assessment session after reviewing the identity information and session recording. In employer-facing CodeSignal documentation, the same outcome may appear as Proctoring Rejected.

This status applies to proctored assessments. It is separate from the automatically calculated coding score. CodeSignal's candidate documentation explicitly says proctoring does not affect the score calculation, while its employer documentation describes verification as a later review of whether the candidate provided the required identification and followed the displayed rules.

However, the hiring workflow can still treat an unverified result as unusable. For example, CodeSignal's Workday integration documentation says a non-verified proctored result can be sent to Workday with a score of zero and a rejection reason. That downstream zero is a hiring-system representation of a rejected verification, not evidence that the coding engine recalculated every solution as incorrect.

Pending verification, Verified, and Not Verified are different

CodeSignal status	What it means	What to do
Pending verification	The assessment was submitted and the proctoring review is not complete.	Wait through the normal review window before escalating.
Verified	CodeSignal certified the proctored session.	The requesting company can use the verified result in its process.
Not Verified / Proctoring Rejected	The session did not pass verification.	Identify the stated reason, contact CodeSignal Support, and notify the recruiter.
Expired (Not Verified)	A rejected verification has later moved to an archived expired state in an integration.	Do not confuse it with an invitation that was never attempted.
Not proctored	The assessment did not use the same proctored certification workflow.	Review any separate integrity status or employer instructions.

CodeSignal says its proctoring team generally verifies certified assessment results within one to three business days. A result that remains pending for several hours is not the same as a rejected result. Weekends, holidays, and the requesting company's internal systems can also make the hiring portal lag behind CodeSignal.

How CodeSignal verification works

Before a proctored assessment, CodeSignal can require access to your camera, microphone, and entire screen. The setup may also collect a face photo and one or two images of a government-issued photo ID.

After submission, CodeSignal's proctoring verification team reviews whether the required access remained available, whether the identity information is valid and consistent, and whether the session followed the assessment rules displayed during setup. This happens after the coding platform calculates the technical result.

For a detailed explanation of what is recorded and what the requesting company receives, read Does CodeSignal Record Your Screen?

Common reasons a CodeSignal result is not verified

CodeSignal's current employer guide lists several common reasons. The exact reason for one candidate should come from the report or CodeSignal Support, not from guessing based on another person's experience.

You were not alone in the room

Another person entering the camera view or remaining in the room can make the session inconsistent with a rule requiring you to work alone. Even if that person did not help, the reviewer may not be able to verify an uninterrupted individual assessment.

Use a private space when possible. Tell household members when the test starts and place a note on the door. If an unavoidable interruption occurs, record the approximate time and contact support promptly after submission.

You left the camera view

CodeSignal lists getting up and exiting the camera's view as a common non-verification reason. This is different from briefly looking away while thinking. The important issue is whether the proctoring record can confirm the same candidate remained present and followed the session rules.

Handle water, medication, charging, temperature, and restroom needs before the timer starts. If a medical or accessibility need may require movement, request an accommodation in advance.

You used another device

A phone, tablet, second computer, or unapproved display can create a verification problem. Put unused devices away rather than leaving them face down beside the keyboard. Follow the exact monitor and device policy shown during setup.

You used an external IDE

For the General Coding Assessment, CodeSignal's current rules require candidates to work in the provided environment and list external IDE use as a common reason for a result not being verified. Another assessment, such as a data workflow, may explicitly permit external tools. The instructions for your assessment control.

Your web search went beyond syntax reference

CodeSignal's GCA guidance permits limited syntax reference but not outside assistance with solution logic. Looking up how to call a standard library method is different from searching for an implementation of the problem. The same guidance says AI use is not allowed for syntax search in the traditional GCA.

Do not assume a resource is permitted because it is public or because another assessment allowed it. Read the rules shown immediately before your session and use only the resources they authorize.

Your ID could not be verified

The ID must be government-issued, unexpired, and clear enough to show the required name, photo, and expiration date. CodeSignal says candidates may redact other information. If the name and photo appear on different sides, the setup supports a second ID image.

A preferred name, legal-name change, blurry image, glare, expired document, or mismatch between the account and ID can complicate verification. Contact CodeSignal Support before the assessment if your preferred name differs or you need an alternative form of identification.

Camera, microphone, or screen sharing was interrupted

CodeSignal requires the configured permissions for the duration of a proctored session. Browser permissions, an unstable connection, another application taking control of the camera, or an incorrect screen-share selection can interrupt the record.

A technical interruption is not the same as intentional rule-breaking, but it can still prevent verification. Save the error message, approximate time, browser version, and what you tried. CodeSignal recommends contacting both its support team and the company contact when an issue interrupts an assessment.

What the employer can see

The requesting company can see the verification status in CodeSignal and, according to CodeSignal's employer documentation, can view the reason by opening the report and hovering over the Proctoring Rejected status. Supported ATS integrations may also receive a rejection reason.

CodeSignal's candidate-facing proctoring page draws an important privacy boundary: CodeSignal says the identification and proctoring data is reviewed by CodeSignal, stored and deleted within 15 days, and not shared with the requesting company. The employer receives the assessment result and verification outcome rather than your raw ID and proctoring recording.

This is another reason to contact CodeSignal Support for a verification issue. The recruiter may see the status and reason but may not possess the underlying recording needed to investigate the session.

Does Not Verified mean CodeSignal accused you of cheating?

Do not use the status as a complete statement about intent. It means CodeSignal did not certify the proctored result. Some rejection reasons involve prohibited assistance; others may involve identity, permissions, environment, or a technical interruption that prevents verification.

At the same time, avoid minimizing a clear rule violation as a technicality. If the assessment prohibited an external IDE, solution search, AI tool, second device, or another person in the room, the correct response is not to invent an appeal argument. Give CodeSignal and the recruiter a concise factual account.

What to do immediately after seeing Not Verified

1. Confirm the exact status

Distinguish Pending Verification from Not Verified or Proctoring Rejected. Check the assessment result, email, candidate portal, and employer portal. Save a screenshot of the visible status without exposing sensitive ID information.

2. Write down the session facts

Before memory fades, record the assessment name, date, start and finish time, device, browser, network, visible warnings, interruptions, permission failures, and any support messages. Keep the account email and company invitation handy.

3. Contact CodeSignal Support

Email support@codesignal.com or use the help center request flow. Ask for clarification on the verification outcome and provide factual details. Do not send a scan of your ID through ordinary email unless CodeSignal's secure support process specifically requests it.

4. Notify the recruiter

Tell the company contact that the technical assessment was completed but the result shows a verification issue and that you contacted CodeSignal. Keep the message short. The recruiter may be able to pause an automated rejection or tell you how the company handles retakes.

5. Wait for a retake decision

A retake is not automatic. CodeSignal says a candidate normally cannot make multiple attempts from one invitation, and certified assessments may have cooldown limits. However, attempts affected by technical issues or extenuating circumstances identified by CodeSignal may not count against attempt limits.

The company or CodeSignal may need to issue or enable another attempt. Do not create another account to bypass a cooldown; CodeSignal explicitly prohibits that.

A message you can send to CodeSignal Support

Subject: Proctored assessment result shows Not Verified Hello CodeSignal Support, I completed [assessment name] on [date and time] using the account [email]. My result now shows [exact status]. During the session, [brief factual description of any warning, interruption, ID issue, or permission problem]. I followed the displayed assessment rules and would appreciate clarification on the verification outcome and whether any additional information is needed. The requesting company was [company]. Thank you.

Do not over-argue the case in the first message. A precise timeline is more useful than speculation about what the system may have detected.

A message you can send to the recruiter

Subject: CodeSignal verification issue Hello [Name], I completed the requested CodeSignal assessment on [date], but the result currently shows [Not Verified / Proctoring Rejected]. I have contacted CodeSignal Support and provided the session details. I wanted to notify you promptly and ask whether you prefer to wait for their review or follow another process. Thank you.

Will CodeSignal change the result or grant a retake?

There is no public guarantee that every rejected verification will be reversed or retaken. The outcome depends on CodeSignal's review, the reason, the assessment type, and the requesting company's process.

CodeSignal's documentation does show that technical issues and identified extenuating circumstances can affect whether an attempt counts toward cooldown limits. Its Workday integration also notes that when CodeSignal grants a retake after a technical issue, the retake result is sent to Workday. Those policies support contacting CodeSignal quickly, but they are not a promise that any specific case qualifies.

How to prevent verification problems next time

When	What to check	Why it matters
Several days before	Confirm account name, valid ID, browser, camera, microphone, and accommodation needs.	Identity or equipment issues need time to resolve.
One day before	Read the assessment-specific rules and practice in the permitted environment.	Rules differ across assessment types.
Before setup	Close unrelated apps and tabs, disconnect unapproved displays, silence notifications, and clear the room.	Protect privacy and reduce ambiguous events.
During setup	Share the entire requested screen and verify that face and ID images are clear.	Incomplete capture can block verification.
During the test	Stay visible, use only authorized resources, and follow every displayed rule.	The session is reviewed against those rules.
If something breaks	Use available support, preserve the error details, and notify the recruiter promptly.	A timely factual record is easier to investigate.

Technical preparation also reduces the temptation to reach for an unapproved resource.

Frequently asked questions

How long does CodeSignal verification take?

CodeSignal currently says proctored certified assessment verification generally takes one to three business days. A pending result during that window is not yet a rejection.

Can a high CodeSignal score be Not Verified?

Yes. Technical scoring and proctoring verification are separate. A strong coding score does not guarantee that the recorded session satisfies the identity and rule requirements.

Can the employer see why my result was not verified?

CodeSignal's employer documentation says authorized company users can open the report and view the reason associated with Proctoring Rejected. ATS integrations may also receive a rejection reason.

Does the employer receive my ID or full proctoring video?

CodeSignal says the identification and proctoring data is reviewed by CodeSignal, not shared with the requesting company, and deleted within 15 days. The company receives the result and verification outcome.

Can I appeal a CodeSignal Not Verified result?

Contact CodeSignal Support and provide the exact status and factual session details. Public documentation does not promise a formal appeal or reversal in every case, so also notify the recruiter and ask about the employer's process.

Can I retake immediately?

Not necessarily. Retakes depend on the invitation, assessment cooldown, CodeSignal's handling of the issue, and the employer. Do not create a second account to work around the restriction.

What if my portal shows a score of zero?

Some ATS integrations represent a non-verified proctored result as zero and include a rejection reason. CodeSignal separately states that proctoring does not change the automatic coding-score calculation. Ask the recruiter which status their system received.

Final takeaway

A CodeSignal score marked Not Verified means the proctored session was not certified. It is not the same as a low technical score, but it can still prevent the employer from using the result.

Confirm the status, document the session, contact CodeSignal Support, notify the recruiter, and wait for a formal retake decision.

Sources and Further Reading

Research note: CodeSignal and employers may change assessment, verification, retention, and retake policies. The rules shown for your assessment and direct guidance from CodeSignal Support and the requesting company are the source of truth.