Proctored Coding Assessments: What Gets Flagged and What To Do After a Mishap

More online coding assessments now open with a camera check, a full-screen requirement, a monitor check, and sometimes a photo ID step. Honest candidates then worry about ordinary things: glancing away while thinking, a keyboard shortcut that changes tabs, picking up a phone to check the time, or needing a bathroom break halfway through.

This guide explains what proctoring tools say they monitor, how to set up so routine habits do not create avoidable integrity events, and what to do if something goes wrong anyway. It does not explain how to get around monitoring. The safest strategy is to follow the stated rules, prepare your environment, and report a real mishap briefly and factually.

Before your next proctored assessment:

1. Read the rules screen and the invitation email before the timer starts. Write down what is allowed: scratch paper, a calculator, documentation, breaks, and speaking aloud.
2. Ask the recruiter about anything the rules do not answer, especially breaks and accommodations. Ask in writing before you begin.
3. Run any system check the invitation offers on the same computer, browser, camera, and network you will use.
4. Rehearse once in the same conditions: one browser window, one tab, full screen, one monitor, and no phone within reach.
5. Prepare a two-sentence note you can send afterward if a mishap occurs.

What proctoring tools say they record

Proctoring is configured by the hiring company and differs by platform and test. Treat the rules shown in your invitation as the authority for your session. Vendor documentation is still useful because it shows the kinds of signals a test can collect.

The two vendors also describe what happens after the session differently. HackerRank says Proctor Mode produces an integrity result for the hiring team. CodeSignal says its own verification team reviews the recording, that proctoring has no impact on the automatically calculated score, and that identification and proctoring data is not shared with the company that requested the report. Do not assume that one platform's process applies to another, and do not rely on third-party claims about secret thresholds.

A flag is evidence to review, not an automatic verdict

Neither documentation page describes a flag as an automatic rejection. A logged event means the system recorded something that a reviewer may need to interpret. You cannot see that review, and you cannot control how a particular employer weighs it. You can control two things: reducing accidental events and giving a clear account when one happens.

That is also why over-correcting is unhelpful. Staring rigidly at the editor, refusing to move, or narrating every action to the camera does not make an assessment more valid. Work normally within the rules. Reading the problem, looking down at permitted scratch paper, and pausing to think are normal assessment behavior.

Set up your room and computer before the timer starts

Most reported mishaps are habits: a phone used as a clock, a shortcut, a help link that opens a new tab, or an unexpected need to step away. Remove those triggers before you begin.

• Use the platform timer. Full screen can hide the system clock. Find the assessment's own timer during setup so you do not reach for a phone or watch with notifications.
• Open the test in a fresh window. Close other tabs and applications. If you use a shortcut such as Cmd or Ctrl plus a number in your editor, remember that browsers often use similar shortcuts to change tabs.
• Silence and remove devices. If the login requires a code on your phone, complete it, then put the phone out of reach and out of camera view.
• Disconnect extra monitors. Unplug them before the system check instead of only turning them off.
• Prepare the room. Use stable power and the most reliable network available. Put permitted water and scratch paper within reach before the timer begins.
• Know where help lives. Before starting, read the invitation for the support contact and the recruiter's address. A help icon inside the test may open another page.

Practice once in the same conditions

Do one timed rehearsal that matches the real environment. Choose two problems you have not solved recently, set a 45-minute limit, and work in a single full-screen browser window with no second monitor.

Use concept prompts to warm up your explanations, such as hash tables and collision resolution and choosing DFS or BFS. Answer each aloud in two minutes, then write the time and space complexity of one implementation without looking anything up.

Score the rehearsal honestly:

• Did you reach for a phone, clock, tab, or second screen even once?
• Did you read every constraint before coding?
• Did you run or trace at least two edge cases before submitting?
• Did you stop polishing one problem when the timer said to move on?

The general online coding assessment guide covers problem patterns and pacing. If the platform will not let you run code, use the method in tracing code without a compiler.

Worked example: an accidental tab switch

This scenario is fictional. A candidate starts a 70-minute assessment with tab monitoring, camera monitoring, and full screen enabled. At minute 12, they press a shortcut out of habit. The browser changes tabs for about two seconds, the candidate returns, and a warning says the activity was recorded. It happens once more at minute 19.

During the assessment

1. Return immediately and keep working. The remaining time still matters more than the event.
2. Write the approximate times on permitted scratch paper, or remember them if paper is not allowed.
3. Do not open other applications to capture evidence unless the rules allow it. That can create additional events.
4. Change the habit for the rest of the session. For example, move your hand away from the modifier key while navigating code.

After you submit

Send one short message to the recruiter or coordinator the same day. Do not argue that the event could not have mattered and do not ask them to ignore it. State what happened.

“Hello [Name], I completed the [role] assessment today. I want to note that I accidentally changed browser tabs twice, around minutes 12 and 19, because of a keyboard shortcut I use in my editor. I returned immediately each time and did not use outside resources. I am happy to answer any questions. Thank you.”

That message is useful because it gives times, a cause, and a clear statement without a long apology. It is not a guarantee. If you did use an outside resource, do not claim otherwise.

Other branches

• Bathroom emergency. If a break was not arranged, follow any instructions on screen. If there are none, step away only when necessary, return as quickly as possible, and include the time and reason in the same type of note. Next time, ask before the test whether breaks are allowed.
• Power, network, or platform failure. Contact the support channel listed in the invitation as soon as you are able, then email the recruiter with the time and the error you saw. Ask whether the test can be reset or rescheduled.
• Phone picked up by habit. Put it down and out of view immediately. Mention it briefly afterward only as what it was, such as checking the time.

Ask for accommodations early, and protect your ID

If you need extra time, scheduled breaks, assistive technology, or an alternative to a camera-based step, request it before you begin. Use the recruiter or the accommodation contact in the invitation. CodeSignal's FAQ, for example, says candidates without government-issued photo ID can contact support to request an alternative. The interview accommodations guide includes wording that does not require oversharing.

A platform ID step is different from an unexpected request to hold your ID up during a live call with an agency you cannot verify. Before sharing identity documents, confirm the company, the recruiter, and the purpose of the request. The recruiter verification guide explains how to check that the process is genuine.

If you are rejected after a mishap

You may never learn whether an integrity event affected the decision. Scores, other candidates, and the employer's threshold also matter. If you sent your note and receive a rejection, you can ask once whether the result was based on the score, the integrity review, or both. Accept that many teams cannot share that information.

Then improve the factor you control. Repeat the rehearsal with the same environment, and check the employer's reapplication rules before trying again.

Sources and scope

Recent public discussions show the same concerns across several communities: an accidental tab switch caused by an editor shortcut, October 13, 2026; a candidate noticing that an online assessment now required webcam proctoring, October 12, 2026; a question about whether eye movement is flagged, October 20, 2026; a bathroom break during an assessment, October 22, 2026; and a phone picked up to check the time followed by a help link that left full screen, October 26, 2026. These accounts are mostly from students and early-career software candidates. They illustrate common worries; they are not evidence of how any employer evaluated a flag.

Platform behavior comes from the vendors' public documentation linked above, checked on November 7, 2026. Features and configurations change, and the rules displayed for your own assessment take precedence over this guide.