1. LandOffer
  2. Blog
  3. All articles
  4. Amazon SDE Online Assessment Handoff: Track Each Part, Survey, and Final Confirmation

Job search

Amazon SDE Online Assessment Handoff: Track Each Part, Survey, and Final Confirmation

Two completed university-only handoff and symptom-triage records distinguish parts, required feedback, final messages, emails and hiring outcomes.

9 min readLandOffer team

Finishing coding does not establish that your whole Amazon SDE online assessment has been handed off. Track the parts named in your invitation, any required survey, the final completion message and the relevant confirmation email separately. None of those signals, by itself, means you passed or advanced.

Start by identifying your university route: full-time or internship, and the one- or two-part structure named in your invitation. Keep the assessment handoff precise while continuing your broader search for current tech roles on LandOffer, rather than letting one completed coding screen become your entire application record.

A candidate arranging assessment stages and a final confirmation card

Match the invitation to the correct public guide

Amazon's university SDE OA guide covers students and recent graduates. Full-time structure can be one or two parts depending on country; the invitation identifies which applies. Its feedback survey is required. Do not transfer that requirement to a different route without reading its instructions.

For internships, the university guide lists coding, work styles and feedback. Full-time roles additionally list work simulation. Do not infer that completing the internship components would complete a full-time invitation, or that every invitation divides the components between parts identically.

This guide checked Amazon's current public university OA instructions on October 21, 2026, including a full rendered page read. No private invitation, assessment link, practice question or candidate account was opened. No answers were written or submitted. LandOffer publishes this guide and provides its own job-search product. The records below are original fictional editorial examples. SDE II has separate guidance and is outside this article's scope.

Your invitation is the starting record for the role, country, deadline and part structure. If a public page does not match it, clarify the discrepancy through the contact supplied for your process. A blog cannot establish which assessment configuration was issued to you.

Keep timing estimates attached to their route

The university guide lists average times of 70 minutes for coding, 15 for work styles and five for feedback in the internship route, with an approximately 90-minute overview. The full-time component list adds a 60-minute work simulation. Its averages total 150 minutes, while its headline suggests reserving up to two hours. Preserve that mismatch rather than inventing a universal session maximum.

Use the structure in your invitation to plan the handoff. A component name identifies work to track; an average duration does not establish a timer, a pause allowance or the moment a link becomes active. This guide has not tested those behaviors.

Separate the deadline from the estimated duration in your planning record. The deadline tells you when the required handoff must happen. An estimate helps you reserve uninterrupted time. Neither means you can safely start at the last possible moment or omit the final steps when your reserved block ends.

Keep setup time outside the work you expect to do in the assessment. Read the invitation and public preparation instructions beforehand, but do not open a live link merely to explore it. This article did not test whether any specific link starts a timer, supports pausing or can be reopened.

Worked handoff ledger: two parts are not one completion

Fictional candidate Rhea's invented invitation explicitly describes a two-part university full-time OA. It names Part 1 and Part 2 separately and includes feedback in its required flow. This is an illustrative instruction set, not a claim that every Amazon full-time invitation divides components the same way.

Rhea completes the following handoff ledger using non-question status descriptions:

Checkpoint in the fictional record What Rhea has observed in the example Completed status decision
Part 1 Its end step was reached; its email is present Part 1 handoff recorded, not whole OA complete
Part 2 Assessment work is finished, but required feedback remains Keep the overall record open
Required feedback Later completed as instructed Advance to final-completion verification
Final page A message explicitly says the OA is complete Record final-page confirmation separately
Part 2 confirmation email Not yet observed Leave the email field pending; do not invent a receipt
Recruiting outcome No decision received Mark outcome unknown

Her result at the fourth row is “final page seen, confirmation email pending.” That records the observed handoff without claiming either failure or a passing result. The missing email does not erase the page she saw, but the page does not manufacture an email she has not received.

Rhea's local administrative note contains only the route label, her own permitted completion timestamps and the presence or absence of messages. It contains no coding prompt, test data, answer, work-style item or screenshot. Before keeping any note, she follows the assessment's actual rules about what may be recorded.

She also rejects a tempting shortcut: replacing the two rows with a single checkbox labeled “Amazon test done.” That would hide whether she was waiting for a second part, a required survey or confirmation. Keeping the rows separate makes the next action visible without storing confidential assessment material.

A permitted administrative timestamp should include its timezone. Rhea keeps the local time and timezone together so a later support inquiry does not accidentally describe a different point in time.

For comparison, an internship record would omit the full-time work-simulation row unless its own instructions said otherwise. It would still keep coding, work styles, required feedback and final confirmation distinct. That is a different checklist, not a shorter version of Rhea’s record with the missing row silently marked complete.

Rhea therefore writes the route at the top before checking any component. If the role title or invitation changes, she revisits the component map rather than copying completion labels from an earlier application. A reusable blank structure is useful; a reused completed status is not evidence about a new invitation.

The ledger does not predict the scoring decision. Rhea can report that she reached a completion step; she cannot infer that every answer was accepted, that a threshold was met or that an interview will follow. Administrative completeness and hiring evaluation answer different questions.

Distinguish a missing page from a delayed email

For the university route, the guide says that if the final confirmation page does not appear after two minutes, close the browser and reach the recruiting contact. For a two-part OA, a missing completion email after 24 hours calls for checking spam/junk and using the contact details in the OA email. Those are different triggers and routes, not one universal waiting period.

Use the instruction for the symptom you actually have. Waiting a full day when the page never appeared would ignore the separate page guidance. Treating an email delayed for a few minutes as proof of a failed submission would add a conclusion the evidence does not support.

Keep the two university troubleshooting thresholds attached to their specific signals. The page problem concerns what happened immediately after final submission. The email problem concerns the relevant part's later message. If an invitation contains additional instructions, retain them alongside the public guidance rather than replacing them with an assumption.

This guide did not test any support response time, retry behavior or restoration process. A completed support message draft would not prove that a session was recovered, and an automated acknowledgment would not establish a recruiting decision.

Worked triage: Noel chooses the correct next step

Fictional candidate Noel makes a four-situation triage record before the assessment so that a problem does not lead to improvised retries. Each row is an alternative scenario, not a sequence of events in an actual account.

Alternative situation Minimal evidence available Noel's completed decision Claim Noel will not make
University final page still absent after the documented interval Approximate submission time; no finish message Follow that guide's close-and-contact instruction “The whole OA is confirmed complete”
Two-part university flow shows completion, but the relevant email is absent beyond the documented window Final page observed; inbox and spam checked Use the contact details in the OA email with the missing-email issue “The assessment failed”
University internship coding ends while work styles or feedback remain Coding end state only Continue the required university flow “The internship OA is complete”
University full-time coding and work styles end, but work simulation or required feedback remains Only the completed components are accounted for Keep the full-time handoff open and follow the invitation “The internship component list is enough”

Noel finishes with a distinct next step for each symptom. It also prevents the same symptom from being described differently when he feels anxious. An absent message is recorded as absent, not translated into a score or an automatic rejection.

For the missing university email scenario, his illustrative inquiry is fully drafted but unsent:

I completed the part identified in my OA invitation and saw the final completion message at approximately 16:20 UTC on October 26. The confirmation email has not appeared in my inbox or spam folder within the stated window. Could you confirm the appropriate next step? I have not included assessment questions or answers.

Those details are fictional and must not be copied as a factual report. A real inquiry should use the candidate's own minimal, permitted administrative details and the contact channel supplied in their invitation. Do not send unique assessment links, identity documents or question content to an unrelated address found in a forum.

Noel does not repeatedly reopen a completed session, create a second application or ask someone else to inspect his assessment. This article has not established that those actions are allowed or useful. He follows the supplied support path while preserving the distinction between what he saw and what he wants confirmed.

Separate stage cards, a clock and an envelope representing final confirmation checks

Preserve completion evidence without capturing the test

The university guide warns that using print-screen terminates the session and locks the candidate out. Do not screenshot the assessment as completion proof or use screen recording to build a record of its contents. Follow the actual assessment's restrictions, including any broader limits on copying or recording.

Instead, use whatever non-question administrative evidence the process permits: a confirmation email, an allowed minimal timestamp note or the completion message you personally observed. Observation is not a screenshot file, and this article supplies no method for bypassing capture restrictions.

Keep the record small enough that it cannot become a collection of assessment items. The purpose is to identify a missing handoff, not to reproduce the test. If you are unsure whether a proposed note is permitted, clarify before recording it rather than assuming that “for my records” creates an exception.

Neither public-resource guidance nor a preparation article establishes permission for live AI assistance. This guide makes no such permission claim and provides no coding answers, work-style responses or advice for concealed help. Use the tool and conduct rules attached to your own assessment.

Close the administrative loop without guessing the outcome

Before calling your personal record complete, check whether each required part has a supported status and whether the final handoff was actually observed. Account for the required feedback survey as well as the assessment components. Retain any unresolved confirmation issue as unresolved until the appropriate channel addresses it.

If an email arrives later, update the pending email field rather than rewriting the earlier observation. If a recruiter supplies a next step, record that new instruction with the relevant application. A later invitation is evidence of advancement; a completed OA task on your own checklist is not.

Finally, keep preparing and searching without repeatedly checking a completed session for reassurance. A precise record should reduce unnecessary reopening, not become another assessment task. Record the route, required parts and confirmation signals, then return to roles aligned with your experience while the actual hiring process continues.

Sources and Further Reading