Is the Amazon OA Proctored? What Gets Logged

The Amazon Online Assessment is not watched by a human while you take it, and Amazon does not describe it as a proctored exam. It is still instrumented. On its own preparation page for university and new-graduate software development engineer roles, Amazon states that "your browser usage is logged," that using print screen will terminate your session and lock you out, and that sites requiring a login or private repositories are off limits. Those three sentences tell you more about what the assessment can see than any feature list, and the third one quietly settles the question most candidates are really asking.

This article covers what Amazon publishes about the OA as of September 28, 2026, what the HackerRank platform it runs on is documented to be capable of, and where the gap between those two things leaves you.

What Amazon publishes about the OA structure

Amazon runs different OA configurations by role and level, and the published timings differ.

For university full-time SDE roles, Amazon's online assessment prep page for SDE roles lists four parts: a coding assessment averaging 70 minutes, a Workstyles Assessment averaging 15 minutes, a Work Simulation averaging 60 minutes, and a 5-minute feedback survey. Amazon advises candidates to "set aside up to two hours of uninterrupted time for the OA."

For SDE internship roles, the same page lists three parts and no Work Simulation: the 70-minute coding assessment, the 15-minute Workstyles Assessment, and the 5-minute survey, taking "about 90 minutes" in total.

For experienced hires, Amazon's SDE II online assessment prep page describes a different shape again: a coding challenge of "90 minutes for 2 questions," a system design section of approximately 15 minutes, a Work Style section of approximately 10 minutes, and a one-minute optional survey. That page states candidates have "seven days to complete the assessment from the date it was sent" and that results arrive within two days of completion.

The practical consequence is that "the Amazon OA" is not one test. If a friend tells you their OA had a Work Simulation and yours does not, neither of you is wrong.

The rules Amazon states in writing

The prep page for university SDE roles is unusually explicit about conduct, and it is the closest thing Amazon publishes to an integrity policy for the coding section.

Public resources are allowed; anything behind a login is not

Amazon states that candidates "are allowed to use publicly accessible online resources (e.g., the Java Developer Kit or Standard Template Library)" and then draws the line: "Don't access sites that require a login or are private repositories. Your browser usage is logged."

That is a permission rule, not a detection rule, and it is broader than it first appears. Language documentation, standard library references, and public specifications are explicitly fine. A private GitHub repository is not. Neither is any service you have to sign in to reach — which, in September 2026, describes every mainstream AI chat product, every hosted coding assistant, and most paste-a-problem-get-an-answer tools.

Candidates often go looking for whether Amazon can detect a given tool. Amazon has answered a different and more decisive question: whether it permits one. On the published rule, it does not.

Print screen ends the assessment

Amazon's instruction is unambiguous: "Don't use the print screen functionality, because your session will be terminated, and you'll be locked out." This is the one stated consequence on the page that is automatic rather than reviewed. Treat the screenshot key as disabled for the duration of the test, including any global screenshot shortcut your operating system or a background application binds.

Copy and paste is discouraged and recorded

Amazon writes: "Avoid copying and pasting in the assessment. We expect this to be your own code." The wording is softer than the print screen rule, but on the underlying platform the behavior is captured either way. HackerRank's own documentation states that "when candidates copy or paste text, the system records the action automatically. Pasted content appears in the candidate's test report." Our breakdown of HackerRank copy-and-paste logging covers how that entry reads on the reviewer's side.

What the HackerRank platform is documented to do

Amazon's coding assessments run on HackerRank; Amazon's SDE II page tells candidates to "get comfortable coding within HackerRank" before starting. That matters because the monitoring available to Amazon is the monitoring HackerRank ships, and HackerRank publishes what that is.

HackerRank's test integrity documentation describes tab proctoring, which "tracks how often and for how long a candidate leaves the test window"; automatic copy-and-paste capture; optional image proctoring, which "requires candidates to enable their webcam before starting the test" and "captures periodic snapshots during the test"; optional photo identification; and an AI plagiarism detection add-on that "flags potential plagiarism by analyzing candidate behavior, code evolution, and submission similarities."

Separately, HackerRank documents a Proctor Mode that is considerably heavier: full-screen enforcement, webcam monitoring, object detection in the webcam feed for phones and tablets, screenshot analysis for unauthorized software, and gaze and conversation heuristics. HackerRank states that Proctor Mode "must be enabled at both the Company level and the Test level," and that it requires both webcam access and screen sharing access from the candidate.

That last detail is the useful one. Proctor Mode is not silent. It asks for screen sharing and camera permission before the test begins, so a candidate can tell whether it is switched on from the consent prompts, not from guesswork. Our guide to reading the HackerRank setup screen for proctoring signals walks through what each prompt indicates, and what HackerRank can observe about your other tabs covers the limits of tab tracking specifically.

What Amazon has not published

Being clear about the gaps is more useful than filling them with inference.

Amazon's university prep page lists a webcam among the technical requirements and includes FAQ entries titled "Do I need to have a webcam for the OA?" and "Do I need to have identification for the OA? (North America only)." The body text of the page does not state whether the camera records continuously, captures periodic snapshots, or is used only for an identity check at the start. Amazon also does not publish which HackerRank integrity settings it enables, whether those settings differ between the internship, new-graduate, and SDE II assessments, or what threshold of flagged behavior triggers a human review.

The honest summary: Amazon has published its rules but not its instrumentation. A candidate cannot know from public sources exactly what is switched on for their specific link, which is a reason to read the permission prompts on the setup screen carefully rather than to assume either the lightest or the heaviest configuration.

What this means if you are taking an Amazon OA

The Amazon OA is a closed-resource coding assessment with a documented exception for public reference material. Amazon's stated rule prohibits anything requiring a sign-in, so AI assistance is out of scope for this particular assessment regardless of what any tool claims about its visibility. The realistic preparation is the unglamorous kind: practice in HackerRank's editor so the environment is not new, have your language's standard library documentation open as a public reference, type rather than paste, and keep the screenshot key untouched.

AI rules are set per employer and per stage, not by the industry, and Amazon's OA sits at the strict end. Other companies have moved the other way for live interviews, and some now expect candidates to use assistance and evaluate how well they verify its output. Our overview of where AI is permitted across technical interview stages sets out how to read a specific invitation rather than generalizing from one employer's policy to the next.

If your assessment invitation is ambiguous about what is allowed, the recruiter who sent it is the correct place to ask, and asking in writing before the test is materially better than reconstructing your intent afterward.

The short version

Amazon does not run the OA as a live-proctored exam, and it does not need to. Browser usage is logged, print screen terminates the session, pasted content lands in the test report, and Amazon reserves the right to enable heavier HackerRank proctoring that announces itself through webcam and screen-sharing prompts. What Amazon has not published is which of those settings it turns on for any given link.

Read the permission prompts on your setup screen, follow the published rule about login-required sites, and treat the coding section as what Amazon says it is: an assessment of code you wrote yourself, with public documentation allowed.