How do I know if my online assessment is proctored?

Read the invite and the pre-start screens for seven tells: proctoring vocabulary and environment rules in the email, a required desktop client or browser extension, a system compatibility check, a camera permission prompt, a separate microphone prompt, an identity photo or ID step that blocks the start button, and a screen share prompt. Each one names a specific capture. No prompts and no install means no camera, microphone or screen recording.

Can an online assessment record me without asking permission?

Not through an ordinary browser tab. Camera, microphone and screen capture each require an explicit permission prompt naming the site, and the browser and operating system both show an indicator while capture runs. An installed desktop client or secure browser is different, because it asks once at install time and can hold those permissions afterwards, which is why an install request is the heaviest tell.

Why does a proctored assessment run a system check first?

Because it plans to upload media. A test that only grades code needs nothing from your webcam, your microphone or your upload bandwidth. A compatibility page that measures those things is preparing for a continuous stream rather than a single photo, so treat a bandwidth or camera preview step as evidence of recording, not of general technical caution.

Does an unproctored assessment mean nothing is being logged?

No. Paste events, tab focus and blur events, keystroke level replay of how your code was built, and similarity comparison against other submissions need no permission and produce no prompt. They run inside the assessment page itself. An assessment with no camera, no install and no screen share can still produce a detailed report on how the work was done.

Does hiding a window from screen capture make a proctored assessment safe?

No, and it is the wrong question. Screen capture exclusion affects one channel only. It does nothing about a webcam pointed at your face, room audio, an identity photo taken before the clock, a lockdown client with operating system privileges, a phone propped up as a second camera, or the paste and replay logs recorded inside the page.

What should I do if the invite is ambiguous about proctoring?

Open the assessment link early, before the timer starts, and stop at the first screen that asks for anything. Most platforms separate the setup flow from the clock, so you can see the install request, the system check and the permission prompts without spending assessment time. If the flow gives no separation, email the recruiter and ask which channels are enabled.

How to Tell If an Online Assessment Is Proctored: 7 Tells

You can almost always tell before you press Start, because proctoring cannot be silent. Every capture channel needs either an install, a permission prompt, or a blocking step in the flow, and each of those leaves a visible mark in the invite email or the pre-start screens. Seven marks are worth reading, and the useful part is that each one names a specific capture rather than a vague level of strictness. The exception is the logging that never asks for anything, which is the last section here.

Treat "proctored" as a count, not a switch. One employer sends a link that opens in a normal tab and records nothing but your keystrokes. Another sends a scheduled slot, a client to install, an ID step and a room scan. Both are called an online assessment in the email. What follows maps each visible step to the capture it generally implies. Platforms differ, and employers configure the same platform differently, so read these as strong signals rather than as guarantees about a specific vendor.

The seven tells, and what each one implies is being captured

Tell	Where it shows up	What it implies is captured	What its absence tells you
1. Proctoring vocabulary and environment rules	The invite email. Words like proctored, monitored, secure browser, certified, one attempt, one sitting, plus rules about a quiet well lit room, a clear desk, a single monitor, or no headphones.	Rules about your room exist because something is sampling your room. Desk and lighting language points at a camera. Headphone and quiet room language points at a microphone. A booked time slot rather than a deadline points at a live human proctor or a scheduled recording session.	An invite that gives you only a deadline, a duration and a link is describing an unsupervised test.
2. A required desktop app or browser extension install	A download button, an .exe or .dmg, a "secure browser", or an "add the extension to continue" step before the assessment will open.	The heaviest tell of the seven. A web page can only record what you explicitly grant it. Seeing which applications are running, blocking other windows, restricting copy and paste at the system level, or locking the machine into one full screen window all need software with operating system privileges. Assume full desktop recording plus some degree of control over the machine.	No install means the test lives in an ordinary tab, and every capture it performs has to pass through a prompt you will see and could refuse.
3. A system compatibility check	A pre-flight page that previews your webcam, shows a microphone level meter, measures upload bandwidth, and checks your browser version and operating system.	A test that grades code needs nothing from your camera, your microphone or your upstream speed. Measuring those is preparation for a continuous media upload, which means recording rather than a single photo. The bandwidth step in particular is hard to explain any other way.	A check that only tests page load and browser version is a compatibility check, not a proctoring check.
4. A camera permission prompt	The browser's own dialog, naming the site, usually right after the system check. The operating system and the browser then both show a camera indicator.	Webcam capture of whoever sits in the camera's cone, either as periodic stills or as continuous footage. This is the record a reviewer scrubs later looking for a second person, an empty chair, or sustained glances off to one side.	No camera prompt and no installed client means no webcam capture. This one is genuinely binary in a browser.
5. A separate microphone prompt	A second dialog, distinct from the camera one. Some flows combine them, many ask twice.	Room audio for the duration. The signal it exists to catch is a second voice or one half of a conversation, not your code. It also explains any no headphones rule in the invite.	A camera prompt on its own, with no microphone prompt, means video without audio.
6. An identity photo or ID step that blocks the start button	A headshot taken through the webcam, and in stricter flows a government issued ID held up to the camera. It runs before the timer, and you cannot skip past it.	Attribution. The score is being tied to a named person and stored against the session. This appears where a result is portable between employers, or where the assessment sits late in a process and carries real weight.	Its absence usually means the score is being read as one signal among several rather than as a credential.
7. A screen share prompt	The browser's share picker, offering Entire Screen, Window or Tab, followed by a sharing indicator that stays up for the whole session.	Recording of whatever surface you selected. If the picker offers only Entire Screen while Window and Tab are greyed out, that is a deliberate configuration, and everything on that display is in frame including notifications.	Without it, the assessment can log that focus left the page, but not what you switched to.

Why the install request outranks the other six

The other tells each describe one channel. An install describes a capability. Inside a browser tab the sandbox is doing real work on your behalf: a page cannot list your running applications, cannot read another tab, cannot see a second monitor it was not granted, and cannot start any capture without a dialog and a visible indicator. Installed software sits outside that sandbox by design, which is the entire reason a lockdown client exists.

So the hierarchy is short. An install request means assume broad capture, and read the client's own documentation before you agree to it. A stack of browser prompts means exactly the channels those prompts named, no more. Nothing but a link means the recording surface is empty, which is not the same thing as the logging surface being empty.

The three things no prompt will ever warn you about

Here is where the yes or no framing misleads people. Three record keeping mechanisms need no permission, produce no dialog, and are commonly on by default even in tests nobody would call proctored:

Paste events. The editor knows content arrived as one event rather than as typing, with a timestamp, and in many configurations it keeps the pasted text as well.
Focus and blur events. The page knows when it stopped being the active window and for how long. It cannot name what you switched to.
Keystroke level replay and similarity comparison. The build up of your solution is reconstructable, so a reviewer can watch it appear rather than only read the final state, and submissions can be compared against one another.

None of these depend on a camera, a client or a screen recording. An assessment showing zero tells from the table above can still produce a detailed report on how the work was done. If your audit concludes unproctored, the accurate word is unrecorded, not unobserved.

A ninety second audit before the clock starts

Most platforms separate setup from the timer, so this costs you nothing. Stop at the first screen that asks you for something instead of clicking through it.

Reread the invite for rules, not for warnings

Skip the boilerplate about integrity. Look for instructions about your physical room, your monitors, your headphones, or a booked time slot. Rules about the world around you are the cheapest evidence that the world around you is being sampled.

Open the link early and stop at the first request

If the flow asks you to install anything, that is tell two, and the answer is yes and broadly. Note the name of the client so you can look up what it actually does before you agree.

Read the system check for what it measures

A camera preview, a microphone meter and an upload speed test mean media is going to be streamed somewhere. A browser version check on its own means nothing is.

Count the browser dialogs individually

Camera, microphone and screen share are three separate permissions. Note which appeared and which did not, because that list is your real capture set, then check whether the indicators stay lit once the test begins.

Note whether anything blocks the start button

A headshot or an ID scan you cannot skip means the result is being attributed to a person and stored. Treat that assessment as high stakes no matter how casual the email sounded.

Assume the silent logging either way

Paste, focus and replay never appear in an audit because they never ask. Plan your approach around them being on, because on most platforms they are.

If the flow gives you no separation between setup and the clock, ask the recruiter which monitoring is enabled. It is an ordinary logistics question, and a scheduling coordinator can usually answer it in one line.

Where OfferPilot AI is the wrong tool

A vendor publishes this page, so here is the plain limit. 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, and its window is excluded from screen capture at the operating system level, so it does not appear in Zoom, Teams, Meet, OBS or screenshots. Set that against the table above and the boundary is obvious.

Capture exclusion touches one channel. It does nothing about a webcam pointed at your face, room audio, an ID photo taken before the clock, a lockdown client holding system level privileges, eye tracking, a proctor watching in person, or a phone propped up as a second camera.
It does not reach the logs inside the page. Paste events, focus events and code replay are recorded by the assessment itself, and no display setting is anywhere in that path.
If your audit came back with an install, an ID step or a camera, that is the case to leave it out of entirely. The point of a monitored assessment is that a company which never watched you take it can rely on the result, and this is not positioned as a way around that.
Windows only. No macOS, no Linux, no mobile, no browser extension, so on a locked down Mac the question never even arises.

The use that holds up sits before the assessment window opens. Working timed problems against something that explains why an approach works is what makes a later replay read like fluency rather than recall.

The short answer

Count the tells. An install means broad capture. A system check that measures bandwidth means streaming. Each browser prompt means exactly the one channel it names and nothing beyond it. A blocking ID step means the score is attributed to you by name. And an invite with none of the seven still leaves paste, focus and replay running quietly underneath, which is the part worth remembering long after you have answered the original question.