The Amazon online assessment is a critical early stage in one of the most competitive hiring pipelines in tech. Whether you're applying for a Software Development Engineer position, an Area Manager role, or a business analyst opening, you'll encounter a tailored version of this timed evaluation before you ever speak to a recruiter. Understanding what the assessment contains — and how Amazon scores it — gives you a decisive edge over candidates who walk in unprepared.
Amazon uses the online assessment to filter candidates at scale. The company receives millions of applications each year, and the OA serves as an efficient, standardized way to identify people who combine technical skill with cultural alignment. For SDE candidates, that means two LeetCode-style coding problems typically rated at medium difficulty, administered through platforms like HireVue or Codility. For operations and business roles, you'll face numerical reasoning, verbal reasoning, situational judgment questions, and a work style survey.
Many candidates underestimate the assessment's behavioral components. Amazon's 16 Leadership Principles aren't just interview talking points — they're embedded throughout the work simulation and work style survey. Answers that reflect Customer Obsession, Ownership, Bias for Action, and Invent and Simplify consistently score higher than generic responses. Before you sit down to take the test, you should know these principles well enough to apply them under time pressure without hesitation.
Passing rates vary significantly by role. For SDE positions, roughly 30–50% of candidates who reach the OA stage advance, making thorough preparation non-negotiable. For amazon assessment practice test materials and role-specific drills, using structured mock tests before your OA date is one of the highest-return investments you can make in your application.
This guide breaks down every component of the Amazon online assessment by role, explains exactly how each section is scored, and gives you a step-by-step study plan to maximize your score. From coding problem strategies to work simulation decision frameworks, you'll leave with a clear picture of what's expected and how to meet it. Understanding the timeline matters too: most candidates receive the OA invitation within 48 to 72 hours of submitting an application. You'll have between three and seven days to complete it. Treat that window as a structured preparation period, not just a scheduling task.
Use the first day or two to review the relevant skills, and take the actual assessment when you're rested and at your cognitive peak. The timing of when you sit the OA within the window can measurably affect your score. It's also worth noting that the OA is just one signal in Amazon's hiring process, not the only one.
Your resume, referral status, and the specific team's hiring bar all play a role. However, the OA is the one lever you have the most control over in the short term. A strong OA performance can overcome a less-polished resume; a weak OA rarely gets overridden regardless of other factors.
The Software Development Engineer online assessment is the most technically demanding variant Amazon administers. You receive two coding problems and a window of 70 to 105 minutes depending on the specific OA version. Problems are delivered through Codility or HireVue's built-in code editor, which supports multiple languages including Python, Java, C++, JavaScript, and C#. The environment includes a basic IDE with syntax highlighting but no autocomplete, so you'll want to practice in similar conditions.
Amazon favors problems that test array manipulation, hash maps, binary search, dynamic programming, and graph traversal. The two-problem structure usually pairs one slightly easier warm-up (easy-to-medium boundary) with one genuine medium that requires careful thought. A common trap is spending too long on the first problem trying to micro-optimize, then running out of time on the second. Many successful candidates recommend spending no more than 35 minutes on problem one and reserving the rest for problem two, even if the first solution isn't perfectly optimal.
Partial credit is a real factor in Amazon's scoring. A brute-force solution that passes 60% of test cases scores meaningfully higher than a blank submission. If you can't reach an optimal time complexity, code a working solution first, note the complexity clearly in a comment, and then attempt to optimize. The systems test your code against hidden edge cases, so handle null inputs, empty arrays, and integer overflow explicitly.
For amazon assessment test questions and answers and coding drill practice, structured mock tests targeting medium-difficulty algorithm patterns will build the pattern recognition skills that distinguish prepared candidates. Aim for at least 30 medium LeetCode problems across the key topics before your OA date, with emphasis on solving under a 35-minute per-problem limit rather than unlimited time.
Beyond the code itself, Amazon reviewers look at code clarity, naming conventions, and whether you handle edge cases proactively. Write clean, readable code with meaningful variable names. A solution that's 90% optimal and clearly written often scores better in holistic review than a clever but opaque one-liner. Think of the coding section as a communication exercise as much as a technical one.
One nuance that surprises many candidates is how Amazon handles recursion in its OA problems. Recursive solutions are accepted, but iterative implementations with explicit stacks are often more legible and avoid stack overflow on large inputs. If you reach for recursion instinctively, ask yourself whether the iterative version would be clearer.
For problems involving tree traversal or depth-first search, both approaches are valid — the deciding factor is which you can implement correctly and clearly within the time limit. Practicing both styles in your preparation gives you genuine flexibility on test day. After you've finished both problems, spend any remaining time reviewing your earlier solution for obvious bugs or missing edge cases.
A quick re-read has caught critical errors for many candidates — things like off-by-one errors in loop bounds or incorrect base cases in dynamic programming solutions. Even two or three minutes of review time at the end can convert a partially passing solution into a fully passing one.
Amazon's coding score is calculated from automated test case results plus a manual code quality review. Each coding problem typically has 10–15 hidden test cases. Passing all test cases earns full marks; partial solutions earn proportional credit. An aggregate coding score above roughly the 70th percentile for that OA cohort generally advances you to the phone screen stage.
There is no single public passing threshold because Amazon uses relative scoring — your results are compared against the pool of candidates who took the same OA in the same period. This means a strong performance can matter more or less depending on how competitive the current applicant pool is. Consistency across both problems matters: scoring 100% on one and 0% on the other is generally worse than scoring 70% on both.
The work style survey is a personality and values assessment that maps your responses to Amazon's Leadership Principles. There are no objectively right or wrong answers, but answers that reflect consistent, genuine alignment with principles like Customer Obsession, Frugality, and Dive Deep score higher. Inconsistent responses — where you claim opposing values in different questions — are flagged and scored down.
Speed matters less here than thoughtfulness. You're not racing against a clock in the same way as the coding section, but extremely long response times are noted. The best approach is to answer honestly while keeping Amazon's culture in mind. Candidates who research the Leadership Principles and genuinely reflect on how they've applied them tend to score better than those who try to game the survey with extreme agreement.
The work simulation places you in a series of realistic Amazon workplace scenarios and asks how you would respond. For SDE candidates, these scenarios involve code reviews, cross-team communication, and prioritization decisions. For operations roles, scenarios are set on the warehouse floor. Each choice you make is scored against expected responses based on Amazon's Leadership Principles framework.
The key to scoring well is to treat each scenario as a leadership principle application exercise rather than a common-sense quiz. Think: which principle applies here, and what does it look like in action? Bias for Action means choosing the option that moves forward with available information rather than waiting. Customer Obsession means always choosing the path that best serves the end customer, even when it creates short-term difficulty internally.
Amazon's 16 Leadership Principles are the backbone of every behavioral assessment component you'll encounter in the OA. These principles — Customer Obsession, Ownership, Invent and Simplify, Are Right A Lot, Learn and Be Curious, Hire and Develop the Best, Insist on the Highest Standards, Think Big, Bias for Action, Frugality, Earn Trust, Dive Deep, Have Backbone; Disagree and Commit, Deliver Results, Strive to Be Earth's Best Employer, and Success and Scale Bring Broad Responsibility — aren't marketing language.
They are the actual decision-making framework Amazon managers use every day, and the assessment is designed to identify candidates who already operate this way.
The most frequently tested principles in OA behavioral sections are Customer Obsession, Ownership, Bias for Action, and Deliver Results. Customer Obsession appears in scenarios where you must choose between internal convenience and customer benefit. The correct answer almost always prioritizes the customer, even when it means more work or short-term cost. Ownership scenarios test whether you take accountability for outcomes outside your immediate job description — the right answer is almost always to step in, not to defer.
Bias for Action is particularly important in the work simulation. Amazon explicitly values calculated risk-taking over analysis paralysis. When a scenario presents a choice between waiting for more information and acting on what's available, choose action if the downside risk is manageable. Have Backbone; Disagree and Commit tests whether you'll voice a reasoned disagreement with authority before ultimately committing to the team's decision — the correct responses involve speaking up once, clearly and professionally, then committing fully.
One effective preparation strategy is to write a journal of 10–15 specific professional situations you've been in, tag each one with the Leadership Principles it demonstrates, and practice articulating them in under 90 seconds. This builds the mental library you'll draw from during the work simulation. The more genuine your examples, the more naturally you'll navigate scenario-based questions that probe for authentic responses rather than scripted ones.
The preparation window before your OA is also an ideal time to revisit Amazon's public hiring resources. Amazon posts guidance about its interview process, Leadership Principles, and role-specific expectations on its Jobs site. Reading team-specific engineering blogs and Amazon's annual letters to shareholders gives you authentic context for the principles — you start to see them not as abstract values but as real operating decisions the company makes every day. That contextual depth shows up in your work simulation responses.
Amazon does not provide individual feedback on online assessment results. You'll receive either an invitation to continue in the process or a rejection email, typically within one to three weeks of submission. If you're rejected, the standard cooldown period before you can apply for the same role or team is six months. However, you can apply to different roles or different teams at Amazon during that window, and a new OA for those roles is treated as a fresh attempt.
If you advance past the OA, the next stage is typically a phone screen with a recruiter followed by one or two technical phone interviews. Everything you've prepared for the OA — particularly the Leadership Principles examples and data structure knowledge — transfers directly to these stages. The phone screen often begins with a recruiter asking behavioral questions using the STAR format (Situation, Task, Action, Result) mapped to specific Leadership Principles, so your OA preparation should flow directly into phone screen preparation.
Candidates who fail the OA once and successfully pass on a second attempt (six months later) commonly report that the gap in their preparation was underestimating the behavioral components rather than the technical ones. For amazon assessment questions and answers across all section types, working through realistic practice questions is the most efficient way to identify gaps in your readiness before the real assessment.
Keep in mind that Amazon hires at massive scale — hundreds of SDE positions are open simultaneously across AWS, retail, advertising, devices, and other divisions. If one team's OA doesn't go as planned, a fresh application to a different team six months later with stronger preparation is a genuinely viable path. Many current Amazon employees applied two or three times before making it through. The OA is a filter, not a final verdict on your capabilities.
Candidates who succeed in the OA and land the phone screen often describe a shift in how they think about Amazon's Leadership Principles — from something to memorize to something they genuinely try to practice. That shift is worth pursuing before the assessment itself, not after. When you internalize why Customer Obsession produces better long-term outcomes, your responses in the work simulation come from a place of understanding rather than performance. Interviewers and algorithmic scoring systems alike are designed to detect that difference.
Timing management is the single most impactful skill you can develop before sitting the Amazon online assessment. In the coding section, allocate your time deliberately: read both problems before starting either one. Sometimes problem two is actually more approachable to you, and starting there saves time and builds confidence. If you realize 20 minutes in that you're stuck on an optimization, write a brute-force solution that works, add a comment explaining the optimal approach you'd take with more time, and move on.
In the behavioral sections, avoid the trap of selecting the most aggressive or the most cautious option. Amazon is not looking for extremes. The work simulation is designed to identify Leadership Principle-aligned behavior, and most principles have a balanced quality — not reckless but not passive. Bias for Action doesn't mean jumping in without thinking; it means not letting perfect be the enemy of good. Customer Obsession doesn't mean ignoring business constraints; it means keeping the customer central when making trade-offs.
Technical environment preparation is underrated. Run a browser compatibility test the day before, use a wired internet connection if possible, close unnecessary applications, and disable notifications. Amazon's OA platforms — HireVue and Codility — work best on Chrome or Firefox. If you're in a time zone far from your normal working hours, schedule the OA during your cognitive peak, not just when it's technically available. Performance degrades measurably when you take timed cognitive assessments while tired.
Finally, treat the OA as the beginning of a candidate experience, not a box to check. The Leadership Principles you demonstrate in the work simulation are the same ones your future Amazon manager will evaluate you on in your first 90 days. Candidates who approach the assessment as a genuine reflection of their working style — rather than as an obstacle to game — tend to both score better and perform better once they're hired. Authenticity and preparation together are your strongest competitive advantage.
One often-overlooked aspect of OA performance is what you do in the 24 hours before. Sleep is the highest-leverage preparation variable — cognitive assessments of any kind are measurably impacted by sleep deprivation. Avoid alcohol the night before, eat a normal meal, and don't attempt to cram algorithms in the final hours. What you've practiced over the preceding weeks is what will show up under pressure. Trust your preparation, manage your environment, and approach the assessment with calm confidence rather than last-minute panic.