We may earn a commission from some links on this page. Recommendations remain editorially independent.

Amazon publishes a dedicated Online Assessment guide for university students and recent graduates applying to Software Development Engineer roles. Amazon also publishes a separate SDE II interview-preparation guide that includes an online assessment stage. Those structures are not identical. Country, level, internship versus full-time status, business unit, and the text of your invitation can change the assigned Amazon SDE Online Assessment (Amazon SDE OA).

Coding is only one possible component. Workstyles, Work Simulation, System Design scenarios, and a feedback survey may apply depending on track. Amazon’s current university SDE OA page states that no Amazon-specific knowledge is needed for that OA and that candidates must check their OA email to determine their assigned structure.

The invitation controls the live assessment. Preparation can improve readiness, but it cannot guarantee progression, an interview, or employment. JobTestPrep is an independent third-party preparation provider. It is not Amazon, Amazon Jobs, HackerRank, the recruiting team, or the official assessment administrator.

The coding problems and engineering scenarios on this page are original educational exercises. They are not official Amazon, HackerRank, recruiter, hiring-team, interviewer, or JobTestPrep questions and do not reproduce a confidential assessment, recalled candidate item, hidden test case, scoring rule, proprietary scenario, or live question bank.

What Is the Amazon SDE Online Assessment?

The Amazon SDE Online Assessment is a role-specific online screening step used in Amazon’s Software Development Engineer hiring process. For current university students and recent graduates, Amazon describes the SDE OA as the first step for full-time and internship SDE roles. For SDE II, Amazon describes an online assessment that can appear after a job application and before an interview loop.

Do not assume one SDE OA format applies to every country, level, internship, graduate role, experienced role, business unit, software-development job, application year, or invitation.

Amazon SDE OA Quick Facts

Topic Current evidence status
Official university/recent-grad source Confirmed by Amazon: Online Assessment Prep for SDE Roles
Official SDE II source Confirmed by Amazon: SDE II Interview Prep
University full-time scope Coding, Workstyles, Work Simulation, Feedback Survey; one or two parts by country
Internship scope Coding, Workstyles, Feedback Survey; about 90 minutes
SDE II scope Two technical questions in 90 minutes, then Systems Design scenarios (20 minutes) and Work Style Survey (8 minutes)
Other experienced SDE levels Public OA structure often invitation-controlled; do not copy SDE II timing onto every level
Country variation Confirmed for university full-time: one or two parts; Work Simulation may not apply in certain countries (Amazon mentions China)
Coding component Confirmed on university tracks: two coding problems; average about 70 minutes
Workstyles component Confirmed on university tracks (avg 15 minutes) and SDE II (8-minute survey)
Work Simulation Confirmed in university full-time process; average 60 minutes; country exceptions exist
System Design Confirmed in current SDE II OA materials as Systems Design scenarios
Feedback Survey Required on university OA pages; failure to complete delays results
Total duration University full-time: set aside up to two hours; internship: about 90 minutes; SDE II: 90 + 20 + 8 minutes of named segments
Programming languages Invitation/platform controlled; Amazon publishes suggested language lists for university tracks
Public resources during coding Confirmed for university coding: publicly accessible resources allowed; login-required/private repos banned; browser usage logged
Screenshots Confirmed for university coding: print screen terminates session and locks candidate out
Copy and paste Confirmed guidance: avoid copying and pasting; Amazon expects your own code
Device Laptop/desktop recommended; mobile/tablet not recommended
Webcam Parts of the university OA require a webcam
Identification North America FAQ: student or government-issued ID for verification
Accommodations Contact recruiting / ACAT through Amazon accommodations channels
Passing score No universal public cutoff published
Results Completion confirmation and recruiting follow-up; interview outreach if moved forward
Evidence status labels Confirmed by Amazon / country-specific / invitation-controlled / JobTestPrep claim

Who Takes the Amazon SDE OA?

Verified public audiences include:

  • current university students and recent graduates applying to full-time SDE roles;
  • SDE internship candidates in the university process;
  • SDE II candidates whose process includes the online assessment described on Amazon’s SDE II page.

Other software-development levels may use different assessments. Always read the invitation.

Is the SDE OA the First Hiring Step?

For Amazon’s university full-time and internship SDE roles, Amazon currently states that the SDE OA is the first step in the hiring process. That statement should not be extended to every experienced-hire or non-university software role without separate evidence.

Does Every Software Engineer Candidate Take the Same OA?

No. Track, country, level, and invitation details can change components, order, and timing.

Amazon SDE OA Structure by Candidate Track

Dimension Full-time university / recent-grad SDE SDE internship SDE II Other experienced SDE roles
Confirmed audience Current university students or recent graduates Internship SDE applicants in university flow SDE II applicants described on SDE II prep page Publicly less authoritative; invitation-controlled
Coding Two problems; average 70 minutes Two problems; average 70 minutes Two technical questions; 90 minutes Invitation-controlled
Workstyles Average 15 minutes Average 15 minutes 8-minute Work Style Survey Invitation-controlled
Work Simulation Average 60 minutes; may not apply in certain countries Not listed in current internship process Not listed in SDE II OA block Invitation-controlled
System Design Not listed in university OA process Not listed 20 minutes Systems Design scenarios Invitation-controlled
Feedback Survey Average 5 minutes; required Average 5 minutes; required Not described the same way on SDE II page Invitation-controlled
Published total-time guidance Set aside up to two hours uninterrupted About 90 minutes 90 + 20 + 8 minutes of named segments Invitation-controlled
Country variation One or two parts; check OA email Check invitation Do not assume identical worldwide beyond published page High uncertainty
Official source amazon.jobs university SDE OA page Same page, internship section amazon.jobs SDE II Interview Prep Invitation / recruiter
Uncertainty Exact platform and identity checks vary Exact platform varies How consistently OA appears by locale is invitation-sensitive Do not infer from SDE II

Full-Time University SDE Online Assessment

Current Amazon university guidance says the OA evaluates coding skills, technical problem solving, and Leadership Principles. Depending on the country, the OA may be one or two parts. Check the OA email for structure. Amazon recommends setting aside up to two hours of uninterrupted time and finding a quiet location.

Published average component times:

  • Coding Assessment: about 70 minutes;
  • Workstyles Assessment: about 15 minutes;
  • Work Simulation: about 60 minutes;
  • Feedback Survey: about 5 minutes.

Amazon states you will be asked to solve two coding problems and recommends using a familiar language, listing examples such as Java, Python, JavaScript, C, C++, C#, Objective C, Ruby, Scala, Go, Kotlin, or Swift, while noting the list is not exclusive. Amazon also notes that Work Simulation may not apply in certain countries, such as China.

Amazon SDE Internship Online Assessment

Current Amazon internship guidance says the OA takes about 90 minutes and evaluates coding, technical problem solving, and Leadership Principles. Published process components are Coding Assessment (average 70 minutes), Workstyles Assessment (average 15 minutes), and Feedback Survey (average 5 minutes). Amazon currently describes two coding problems and a preferred-language list for the internship coding section.

Work Simulation is not listed in the current internship process block on that page.

Amazon SDE II Online Assessment

Amazon’s current SDE II Interview Prep page describes this process after application: online assessment, then interview loop if successful, with interview outcome guidance measured in business days. For the online assessment, Amazon currently states that candidates have 90 minutes to complete two technical questions, followed by 20 minutes of Systems Design scenarios and an 8-minute multiple-choice Work Style Survey related to Leadership Principles.

Do not treat interview-loop system design as identical to the OA Systems Design scenarios.

What About SDE I Outside University Hiring?

Amazon’s university OA page is written for student and recent-graduate SDE roles. JobTestPrep editorial copy often describes an “SDE I” university-adjacent package structure. Treat experienced-hire SDE I formats as invitation-controlled unless your Amazon materials name them explicitly.

What About SDE III and Senior SDE Roles?

Do not infer SDE II OA timings for SDE III, senior SDE, principal, or manager roles. Use the invitation and recruiter guidance.

Can the OA Have One or Two Parts?

For the university full-time track, yes. Amazon currently says the OA may be in one or two parts depending on the country and that candidates must check their OA email. After each section of a two-part OA, Amazon says candidates receive email guidance about next steps.

How Long Is the Amazon SDE OA?

Distinguish:

  • university full-time preparation guidance: up to two hours uninterrupted;
  • university component averages: 70 / 15 / 60 / 5 minutes;
  • internship total: about 90 minutes;
  • SDE II named segments: 90 minutes coding, 20 minutes Systems Design, 8 minutes Work Style Survey;
  • any invitation-specific timer shown in your assessment.

Do not invent one universal total by adding every component from every track.

How Many Coding Questions Are There?

Current university full-time and internship pages both describe two coding problems. Current SDE II materials describe two technical questions. Do not assume every software role worldwide uses exactly two questions.

Is Your Coding Time Fixed or Average?

Amazon labels university coding time as an average (about 70 minutes). SDE II materials state 90 minutes for two technical questions. Follow the live timer and instructions.

What Programming Languages Can You Use?

Publish language guidance only as invitation-controlled or track-specific. University full-time materials currently list example languages and say the list is not exclusive. Internship materials currently provide a concrete preferred-language set. Use a language you already know. Do not switch languages immediately before the OA without good reason.

Does Amazon Use HackerRank?

Amazon currently links to an official Online Assessment Practice Test at https://hr.gs/TheAmazonCodingDemo. That practice environment is useful, but it does not by itself prove that every live OA worldwide uses HackerRank. Confirm the live platform from your invitation.

What Coding Topics Should You Study?

Amazon’s Software Development Topics page recommends reviewing fundamentals and practicing coding outside an IDE. Topics commonly listed include programming language fundamentals, data structures, algorithms, coding, object-oriented design, databases, distributed computing, operating systems, internet topics, and general machine learning and AI where role-relevant. Not every OA covers every topic.

Data Structures

Prepare arrays, strings, hash maps, sets, stacks, queues, linked lists, trees, and graphs for university-style coding screens. Exact live coverage varies.

Algorithms

Prepare searching, sorting, recursion, greedy methods, and dynamic programming as fundamentals practice. Do not memorize claimed “real OA lists” from unofficial dumps.

Time and Space Complexity

Be ready to explain expected runtime and memory use after you have a correct approach. Prefer clear correct code before premature micro-optimization.

Testing and Edge Cases

Test normal cases, boundaries, empty input, duplicates, large input, overflow risk, and invalid assumptions. Amazon’s later interview guidance also emphasizes edge cases and validated input; treat that as general engineering hygiene for OA practice too.

Code Readability and Maintainability

University coding descriptions emphasize clarity, maintainability, and efficiency as evaluation themes. Write readable names and straightforward control flow.

Can You Run and Test Your Code?

Follow the live editor. Amazon’s practice test helps you learn the sample environment. Do not assume every live feature matches practice.

Are There Hidden Test Cases?

Amazon’s public university pages emphasize solving problems and quality of code. They do not publish a complete public hidden-test policy for every platform version. Assume thorough testing still matters, but do not invent scoring weights.

Can You Use Online Resources?

For the university coding assessment, Amazon currently allows publicly accessible online resources such as language documentation references, while forbidding login-required sites and private repositories. Browser usage is logged. Follow your live instructions if they differ.

Is Browser Activity Logged?

Yes, current university coding guidance states that browser usage is logged.

Can You Take Screenshots?

Do not use print screen. Amazon states that doing so terminates the session and locks you out.

Can You Copy and Paste?

Amazon advises avoiding copying and pasting and expects the code to be your own. Follow the live rules.

Can You Use ChatGPT or GitHub Copilot?

No unauthorized generative AI or coding assistance. Do not use ChatGPT, GitHub Copilot, or similar tools during the live assessment unless your invitation expressly permits them.

Can Someone Help You?

No. Do not use another person, screen sharing for assistance, or impersonation.

Amazon SDE Workstyles Assessment

Workstyles is distinct from coding. On university tracks it asks you to choose statements that represent your work style in the context of Leadership Principles. Amazon currently says no practice is required for that portion. Still answer honestly and consistently. Do not reverse-engineer a preferred personality.

For dedicated Work Style preparation, see Amazon Work Style Assessment.

Amazon SDE Work Simulation

Amazon currently lists Work Simulation in the university full-time SDE OA process (average about 60 minutes) and notes that it may not apply in certain countries. It is scenario-based workplace decision-making in an engineering context, not a coding puzzle.

For broader simulation prep, see Amazon Work Simulation Assessment.

Amazon SDE II System Design Scenarios

Current SDE II materials include 20 minutes of Systems Design scenarios in the online assessment. Treat that as distinct from live interview system-design whiteboarding.

Is the System Design OA the Same as the Interview?

No. The OA Systems Design scenarios are asynchronous assessment content. The interview loop can include separate system-design discussion with interviewers.

What Is the Feedback Survey?

On the university SDE OA pages, Amazon describes a short feedback survey about candidate experience. Amazon currently says it is required and that failure to complete it delays results and next steps.

Is the Feedback Survey Scored?

Amazon presents it as experience feedback, not as a coding score. Do not invent a survey scoring model.

What Happens After Part One?

For two-part university OAs, Amazon says you receive email informing you whether you move to the next step after each section. Check spam/junk folders.

What Happens After Completing the OA?

Amazon describes a confirmation page after submission. If it does not appear within about two minutes, contact your recruiting contact. Complete the feedback survey. If moved forward, Amazon reaches out directly.

How Long Does It Take to Receive Results?

Amazon does not publish one universal results timer for every track. For two-part OAs, Amazon says to contact the recruiting details in your OA email if you do not receive a completion email within 24 hours of completing a part. That is email-timing guidance, not a hiring-decision guarantee.

Does Amazon Share Your Score?

Public university SDE OA materials emphasize completion, next-step emails, and recruiting outreach rather than a candidate-facing detailed scorecard. Do not assume you will receive section scores.

Is There a Passing Score?

Amazon does not publish a universal public SDE OA cutoff on the pages reviewed for this guide. Complete every assigned section. Prioritize correctness, clarity, and efficient problem solving. Follow the invitation.

Can You Retake the Amazon SDE OA?

Public materials emphasize contacting recruiting for process questions. Do not invent a retake entitlement or cooldown.

Amazon currently says to complete the OA within the timeline in the OA email. Hiring is described as rolling, and delay may impact candidacy. For special circumstances, contact Amazon using the details in the OA email.

What If You Have a Technical Problem?

Amazon publishes troubleshooting guidance (including browser, pop-up blocker, cookies, and alternate browser suggestions) and tells candidates to use the OA email contact details for additional help.

Do You Need a Webcam?

For the university SDE OA FAQ, Amazon currently states that parts of the OA require a webcam and that you should verify the webcam before starting. It links to webcam support guidance.

Do You Need Identification?

Amazon’s FAQ answer about identification is scoped to North America and currently says yes: have a student or government-issued ID ready for verification. Do not assume the same rule worldwide.

Can You Use a Mobile Device or Tablet?

Amazon currently does not recommend mobile devices or tablets because of limited functionality and user-interface experience. Prefer a laptop or desktop that meets the published requirements.

Can You Request an Accommodation?

Yes. Use Amazon’s recruiting/accommodations process and ACAT channels. Request early. This page does not provide medical or legal advice.

Use this comparison to avoid mixing preparation formats. Details still depend on your recruiter schedule.

Related step Difference in one line
General Amazon Online Assessment The Amazon Online Assessment page covers the broad meaning of Amazon OA across roles. This page owns SDE-specific tracks, co
Amazon Coding Interview The OA is typically an asynchronous online assessment. Later coding interviews are live conversations with additional evaluation dimensions.
Amazon Work Simulation Work Simulation can be one OA component on some university full-time tracks. The dedicated [Amazon Work Simulation Assessment](/employer-assessment-tests/amazon-work-simulation-ass
Amazon Work Style Assessment Workstyles/Work Style surveys can appear inside SDE OA tracks. The dedicated Amazon Work Style Assessment page covers st
SDE Interview Loop SDE II materials separate online assessment from the interview loop of multiple interviews. Behavioral Leadership Principles interviews remain a later-stage skill; see [Amazon Beha

Practice Limitation Notice

Amazon SDE assessment formats vary by candidate track, country, level, platform, and current invitation. The problems below are original computer-science exercises for preparation before an assessment. They do not reproduce official Amazon questions, recalled candidate questions, hidden tests, scoring criteria, or proprietary platform content.

Original Coding Practice Problems

These problems are original educational exercises. They are not official Amazon, HackerRank, recruiter, or JobTestPrep questions and do not reproduce live OA items, hidden tests, or scoring rules.

Difficulty labels below are unofficial educational classifications. They do not correspond to official Intern, SDE I, or SDE II difficulty bands.

Section 1: Arrays, Strings, and Hash Maps

Problem 1: Validate inventory label counts

Unofficial difficulty: Introductory

Primary topics: Arrays, hash maps, frequency counting

Problem: You are given a list of item labels. Return true if every label appears at most k times. Otherwise return false.

Example:

  • Input: labels=["a","b","a"], k=2
  • Output: true

Solution approach: Count frequencies with a hash map. Reject as soon as any count exceeds k.

Problem 2: Longest stretch with at most two signal types

Unofficial difficulty: Intermediate

Primary topics: Strings, variable-size sliding window, hash maps

Problem: Given a string of signal characters, return the length of the longest contiguous substring that contains at most two distinct characters.

Example:

  • Input: s="ababac"
  • Output: 5 # ababa

Solution approach: Maintain a sliding window and a frequency map of characters inside the window. Shrink from the left whenever the window has more than two distinct characters.

Problem 3: Group codes by digit-sum signature

Unofficial difficulty: Intermediate

Primary topics: Strings, hashing, grouping

Problem: You receive a list of numeric codes as strings of digits. Group codes that share the same sum of digits. Return the groups as a list of lists, with groups ordered by increasing digit-sum and codes inside each group kept in input order.

Example:

  • Input: codes=["12","3","21","30"]
  • Output: [["12","3","21","30"]] # all digit-sums equal 3

Solution approach: Compute digit-sum for each code, append to a map from sum to list, then emit lists sorted by sum.

Section 2: Stacks, Queues, and Linked Structures

Problem 4: Validate nested task markers

Unofficial difficulty: Introductory

Primary topics: Stacks, parsing

Problem: A notes string uses only characters “(”, “)”, “[”, and “]”. Return true if every opening marker is closed by the matching type in the correct order.

Example:

  • Input: s="([])"
  • Output: true

Solution approach: Push opening markers. On a closing marker, pop and check the pair. Reject on mismatch or leftover openers.

Additional coding drills follow the same pattern: restate constraints, choose an approach, and verify edge cases under a timer.

Engineering-Decision Scenario Practice

The six scenarios below are unscored. They are not Amazon Work Simulation or System Design items.

Scenario 1: Prioritizing a customer-impacting defect

Scenario: At NovaLedger, a payments API started returning intermittent 500 errors for about 4% of checkout attempts after today’s deploy. A planned performance refactor is also on the sprint board.

Decision to analyse: Whether to pause the refactor and focus the team on the defect, or continue planned work while one engineer investigates.

Information provided: Error rate, deploy time, affected endpoint, on-call ownership, and that refunds may rise if failures continue.

Information still needed: Exact blast radius by region, rollback safety, feature-flag options, and whether the refactor touches the same code path.

Options to compare: Immediate rollback; feature-flag disable; dedicated incident pod while refactor continues narrowly; full stop on planned work.

Trade-offs to discuss: Customer trust versus roadmap speed; incomplete diagnosis versus fast mitigation; communication load across support and product.

Verification plan: Confirm metrics after mitigation, add regression tests, and write a short incident summary with follow-up actions.

Primary technical focus: Incident triage and release-risk judgment.

Possible Leadership Principles evidence: Customer Obsession, Ownership, Bias for Action, Insist on the Highest Standards.

Integrity boundary: Unscored educational scenario. Not an Amazon Work Simulation item and not a preferred-answer key.

Scenario 2: Responding to incomplete operational metrics

Scenario: MeshMetrics shows request latency rising, but the dashboard is missing error-rate and saturation panels for one dependency.

Decision to analyse: Whether to act on incomplete data now or wait until instrumentation is restored.

Information provided: p95 latency trend, recent traffic growth, and one dependency owning the missing panels.

Information still needed: Dependency health signals from logs, queue depth, recent config changes, and customer complaint volume.

Options to compare: Temporary synthetic probes; scale up guesswork; freeze releases; restore metrics before changing capacity.

Trade-offs to discuss: Acting on partial evidence versus delayed response; cost of over-scaling versus prolonged latency.

Verification plan: Rebuild the missing panels, compare before/after latency, and document the decision criteria used under uncertainty.

Primary technical focus: Observability-limited operations judgment.

Possible Leadership Principles evidence: Dive Deep, Deliver Results, Earn Trust.

Integrity boundary: Unscored educational scenario. Not an official Amazon simulation.

Scenario 3: Coordinating a safe rollback

Scenario: BrightCart’s catalog service deploy correlates with elevated timeouts. Multiple teams consume the service through a shared gateway.

Decision to analyse: How to roll back safely without stranding dependent teams mid-migration.

Information provided: Deploy marker, timeout increase, list of dependent teams, and that a schema migration was marked expandable.

Information still needed: Whether the migration is backward compatible, current canary percentage, and rollback rehearsed status.

Options to compare: Immediate full rollback; staged canary reduction; dual-write freeze; coordinated change window.

Trade-offs to discuss: Speed of recovery versus coordination overhead; data consistency versus availability.

Verification plan: Validate health after rollback, confirm dependents reconnect, and capture a preventative checklist for the next release.

Primary technical focus: Multi-team release safety.

Possible Leadership Principles evidence: Earn Trust, Ownership, Insist on the Highest Standards.

Integrity boundary: Unscored educational scenario. Not a reconstructed Amazon Work Simulation.

Scenario 4: Storage for a growing read-heavy service

Scenario: PageFlo serves article pages. Reads are about 40x writes. Cold articles are rarely requested; hot articles create cache stampedes after deploys.

Decision to analyse: Which storage and caching design best balances freshness, latency, and cost.

Information provided: Read/write ratio, p99 latency target, current relational store, and cache hit-rate drops after deploy.

Information still needed: Object size distribution, consistency needs after edits, and budget ceiling.

Options to compare: Relational primary with CDN/edge cache; document store; materialized read models; write-through versus stale-while-revalidate cache.

Trade-offs to discuss: Consistency after edits, operational complexity, and cache invalidation design.

Verification plan: Load-test read path, measure deploy stampedes, and confirm edit visibility SLAs.

Primary technical focus: Read-heavy storage and caching.

Possible Leadership Principles evidence: Invent and Simplify, Frugality, Deliver Results.

Integrity boundary: Unscored educational system-design decision practice. Not an Amazon OA System Design item.

More scenario drills use the same evidence checklist: trade-offs, ownership, and measurable outcome.

Coding Preparation Checklist

  • supported language confirmed;
  • language syntax reviewed;
  • arrays and strings;
  • hash maps and sets;
  • stacks and queues;
  • linked lists;
  • trees;
  • graphs;
  • sorting and searching;
  • recursion;
  • dynamic programming;
  • greedy methods;
  • complexity analysis;
  • edge cases and overflow awareness;
  • input parsing and output formatting;
  • code readability;
  • testing and debugging;
  • coding without IDE assistance;
  • official practice environment reviewed;
  • assessment-integrity rules reviewed.

OA Technical-Setup Checklist

  • correct invitation and deadline;
  • correct time zone;
  • laptop or desktop ready;
  • supported browser updated;
  • JavaScript, cookies, and pop-ups configured as required;
  • bandwidth and power cable checked;
  • stable internet;
  • webcam tested when applicable;
  • identification ready when applicable (North America FAQ);
  • screen resolution adequate;
  • quiet environment;
  • recruiting contact saved;
  • accommodation arrangements completed if needed;
  • backup plan for technical failure.

Do not use multiple devices for unauthorized assistance.

Problem-Solving Framework

Unofficial preparation framework:

  1. Read the complete problem.
  2. Restate the requirement.
  3. Identify inputs and outputs.
  4. Review constraints.
  5. Identify edge cases.
  6. Consider a direct solution.
  7. Estimate its complexity.
  8. Select a data structure.
  9. Improve the algorithm if needed.
  10. Implement a correct baseline.
  11. Test normal cases.
  12. Test boundaries.
  13. Review complexity.
  14. Submit only after checking the required output.

Debugging Checklist

  • syntax and imports;
  • variable initialization;
  • indexing and loop bounds;
  • empty or duplicate input;
  • negative values where permitted;
  • large values and overflow;
  • recursion depth;
  • mutable defaults;
  • state reset between cases;
  • sorting assumptions;
  • graph cycles and disconnected components;
  • output format;
  • accidental debug printing.

Workstyles Preparation Boundary

  • understand each statement;
  • answer honestly;
  • distinguish actual behavior from aspiration;
  • stay factually consistent;
  • do not reverse-engineer a hidden personality;
  • do not copy suggested answers;
  • do not invent an ideal employee persona;
  • review Leadership Principles for context only.

This is not an Amazon Workstyles answer key, personality score, suitability profile, or passing strategy.

Fourteen-Day Preparation Plan

This schedule is optional and unofficial. Fourteen days is neither required nor guaranteed to be enough.

  • Day 1: verify invitation and track;
  • Day 2: baseline coding assessment in a familiar language;
  • Day 3: arrays, strings, hash maps;
  • Day 4: stacks, queues, linked structures;
  • Day 5: trees and graphs;
  • Day 6: searching, sorting, intervals;
  • Day 7: dynamic programming and greedy methods;
  • Day 8: complexity and code quality;
  • Day 9: two timed original problems;
  • Day 10: Workstyles honesty checklist and Leadership Principles context;
  • Day 11: Work Simulation or engineering judgment practice if relevant to your track;
  • Day 12: System Design scenario practice if relevant to your track;
  • Day 13: full mock session matching your invitation components as closely as is ethical and public;
  • Day 14: technical setup and light review.

Common Mistakes

  • treating every SDE OA as identical;
  • confusing university and experienced-hire tracks;
  • assuming SDE II rules apply to interns;
  • assuming internship rules apply to every SDE I invitation;
  • ignoring country variation and one-versus-two-part structure;
  • relying only on third-party role tables;
  • focusing only on coding;
  • ignoring Workstyles or Work Simulation when assigned;
  • confusing OA system design with interview system design;
  • assuming every assessment has exactly two coding questions or a universal 70-minute timer;

Free versus Paid Preparation

Start with official materials when available. Paid third-party drills are optional after you confirm the exact assessment.

Official Amazon SDE Assessment Resources

Amazon controls the current OA. The invitation controls the assigned structure. The recruiting team controls deadlines and progression. Official resources linked from Amazon Jobs do not use affiliate fragments.

For ranked-response or work-style sections, Amazon work style assessment preparation may also be useful when you need extra drills under time pressure.

For role-specific Amazon online modules, Amazon assessment preparation can help candidates practise work-style and simulation-style formats under timed conditions. Third-party packs are not official employer or publisher materials; confirm the product matches your invitation before buying.

FAQ

Is the feedback survey scored?

Amazon presents it as candidate-experience feedback. Do not invent a score.

Is there a passing score?

No universal public cutoff should be assumed.

Are the 12 coding problems official Amazon questions?

No.

Is JobTestPrep official?

No.

Does preparation guarantee an interview?

No.

What is the Amazon SDE Online Assessment?

A role-specific Amazon online screening process for Software Development Engineer hiring. University and SDE II public guides describe different structures.