RepostedAmazon logo

Amazon · Phone screen → Onsite

In process

Amazon Experienced Hire OA and Interviews: 21 Experiences

Software engineer · UnknownBachelor's degreeSep 2026
Shared by

Amazon experienced-hire OA and interviews, August 2026: 21 reports on inventory-allocation OAs, repo debugging, hash-map screens and design loops.

At a glance

  • Process: OA (algorithm task plus AI-assisted repo debugging, 100 minutes in 22, then Work Simulation and Work Style surveys) → phone screen (20 min behavioral + 30 min coding in 09) → virtual onsite of about four rounds, each with Leadership Principles (13).
  • Asked recently: repository debugging in all 8 OA reports; inventory or allocation coding in 5 OAs (04, 07, 16, 18, 22); hash-map and counting screens in 6 interview reports (03, 05, 08, 09, 12, 20).
  • Difficulty: SDE II candidates leaned hardest on repo debugging, ambiguous design and deep follow-ups (13, 16, 22); unfamiliar frameworks such as Spring Boot slowed OA candidates down (01, 10).
  • Practise first: Inventory Allocation, Repair MovieDB Search and Recommendations, Track Package Receipt Gaps and Minimum Grid Inconvenience.

Coverage: 21 Amazon full-time candidates who are not new grads, all reported August 2–30, 2026: 19 software engineers (SDE, SDE II, L4, L5, L6, Senior SDE) plus one Applied Scientist and one Engineering Manager in their own section. Entry numbers 02 and 11 are not used.

What came up

The OA's debugging section came up most; phone screens leaned on hash maps. Counts are out of the 19 SDE reports.

Topic Reports Last seen
Repository debugging (OA) 8 of 19 Aug 2026
Behavioral and Leadership Principles 6 of 19 Aug 2026
Hash maps, counting and arrays 6 of 19 Aug 2026
Inventory and allocation coding (OA) 5 of 19 Aug 2026
Graphs, BFS and topological order 4 of 19 Aug 2026
System design 3 of 19 Aug 2026
Heaps and streaming, OOD, merge DP, interval windows 1 of 19 each Aug 2026

Questions we found

OA coding

Question Reports Last seen
Inventory Allocation (by bid priority) 3 Aug 2026
Minimum Grid Inconvenience 2 Aug 2026
Minimum Merge Conflicts 1 Aug 2026
Minimum Contiguous Replacements 1 Aug 2026
Get Minimum Amount 1 Aug 2026

Interview coding

Question Reports Last seen
Track Package Receipt Gaps 2 Aug 2026
Distinct Duplicate Values 1 Aug 2026
Smaller Clock Hand Angle 1 Aug 2026
Arrange Packages With Compatible Adjacent Weights 1 Aug 2026
Implement a Min-Priority Queue 1 Aug 2026
Streaming Top K Frequent Elements 1 Aug 2026
Count Repeat Customers Across Dates 1 Aug 2026
Rearrange Digits Under an Adjacent-Sum Limit 1 Aug 2026
Print a Shortest Graph Path 1 Aug 2026
Weighted Lottery Winners 1 Aug 2026
Package Dependency Order 1 Aug 2026
Find Maximum Total Amount (k consecutive bags) 1 Aug 2026

Project Coding (OA debugging)

Question Reports Last seen
Repair MovieDB Search and Recommendations 4 Aug 2026
Repair Workflow Issue and Sub-Issue Creation 2 Aug 2026
Controller validation, persistence and status tests 1 Aug 2026

System Design and OOD

Question Reports Last seen
Design a Seller Product-Image Upload Service 1 Aug 2026
Design a Marketplace Product Search Service 1 Aug 2026
Design an ML Training and Deployment Platform 1 Aug 2026
Amazon Locker 1 Aug 2026
Industrial code-based OOD (patterns and generics) 1 Aug 2026

Behavioral (BQ)

Question Reports Last seen
Delivering under a tight or impossible deadline (practice) 3 Aug 2026
Finding a root cause (practice) 2 Aug 2026
Using GenAI to work faster 1 Aug 2026
Raising a quality bar 1 Aug 2026
A hard decision 1 Aug 2026
Disagreement in the team 1 Aug 2026
Customer-experience metrics 1 Aug 2026
Optimizing a process 1 Aug 2026
Saying no to a customer request 1 Aug 2026
Lessons learned 1 Aug 2026

Also named, with no entry recorded: owning work beyond your team, recovering from a missed requirement, metrics that conflicted with customer feedback, building something other teams used, changing direction, handling criticism, and committing to a team decision you argued against. Only Learn and Be Curious and Deliver Results were named outright as Leadership Principles (03).

Online assessments (OA)

01: Commit-order DP and a Spring Boot repo

Report date: August 30, 2026 · Role: Full-time SDE · Result: Waitlist

  1. Minimum Merge Conflicts: merge two commit-priority strings, keep each one's internal order, and minimize inversions.
  2. Debug a Spring Boot Movie DB CRUD service against six tests (closest practice). The AI could suggest directions but not edit the code.
  3. The candidate spent about 45 minutes and felt slowed by not knowing Spring Boot.

04: Contiguous quality groups and API tests

Report date: August 25, 2026 · Role: Full-time SDE

  1. Minimum Contiguous Replacements: replace whole groups of quality values so each value forms one block, using as few replacements as possible.
  2. Repair controller validation, persistence and response-status tests in an existing repository.

07: Inventory allocation and a Django repo

Report date: August 21, 2026 · Role: Full-time SDE

  1. Coding: Inventory Allocation by Bid Priority (Inventory Allocation).
  2. Debugging: Issue creation in Django and Python (matching workspace). No more detail was shared.

10: Grid BFS and six failing tests

Report date: August 18, 2026 · Role: Full-time experienced hire · Result: Expected to fail

  1. Minimum Grid Inconvenience, described as multi-source BFS plus binary search.
  2. Spring Boot debugging with six failing tests (closest practice). The candidate cleared the first two test groups, then ran out of time on persistence and status bugs.
  3. Python was another framework option.

15: The distribution-center grid and Issue debugging

Report date: August 14, 2026 · Role: Full-time SDE

  1. Minimum Grid Inconvenience: a binary grid with Chebyshev distance, n, m <= 500; add one center to minimize inconvenience. The candidate used BFS, a feasibility check and binary search.
  2. Repair Workflow Issue and Sub-Issue Creation: request validation, ID generation, Issue creation and schema compliance.

16: Flash-sale inventory and a lowercase bug

Report date: August 11, 2026 · Role: SDE II

  1. Unfulfilled Customers by Inventory Priority (Inventory Allocation): give stock by bid, share tied bids round-robin in timestamp order, and return the customers who got nothing.
  2. Repair MovieDB Search and Recommendations, in Spring Boot: one bug failed to lowercase a partial-title query while the stored values were lowercase.

18: Greedy inventory and a Django + React repo

Report date: August 7, 2026 · Role: Full-time SDE · Result: Fail

  1. Get Minimum Amount: make each quality value contiguous at the lowest replacement cost, a greedy interval-merge or sweep-line task.
  2. Repair MovieDB Search and Recommendations: debug unfamiliar Django and React code from unit tests.
  3. Java, C++ and Python were offered.

22: An SDE II OA that led to a phone screen

Report date: August 4, 2026 · Role: SDE II · Result: Advanced to phone screen

  1. Taken August 3: a 100-minute section with an algorithm task and an AI repository task.
  2. The algorithm was Unfulfilled Customers by Inventory Priority (Inventory Allocation); the repository bug was not described in detail.
  3. Then a Work Simulation of about 15 minutes and two Work Style surveys of about 10 minutes.
  4. The phone invite came August 4, for August 14 at 3:00 p.m. Pacific.

11 SDE phone screens and loops

03: Duplicates and a clock angle

Report date: August 26, 2026 · Role: Full-time SDE · Result: Pass

  1. The recruiter flagged Learn and Be Curious and Deliver Results. One behavioral answer drew a trade-off follow-up.
  2. Distinct Duplicate Values.
  3. Smaller Clock Hand Angle: after a wrong start, corrected with the interviewer, the candidate finished the whiteboard code and dry-ran it.
  4. The pass came the next day.

05: From sorting to counting digits

Report date: August 24, 2026 · Role: L4 SDE · Result: Fail

  1. Arrange Packages With Compatible Adjacent Weights: the candidate first sorted and alternated large and small values. The interviewer pushed for O(n), using the fact that values are only 0–9.
  2. Interviewed on a Friday, rejected on Monday.

06: An Alexa Shopping L6 loop

Report date: August 24, 2026 · Role: L6 · Result: Fail

  1. Design a Seller Product-Image Upload Service.
  2. Implement a Min-Priority Queue, building the heap by hand.
  3. Design a Marketplace Product Search Service.
  4. Streaming Top K Frequent Elements: the most frequent IDs among millions of requests, in pseudocode with complexity.
  5. Behavioral: using GenAI to work faster, impossible timelines, customer metrics, quality bars, hard decisions and team disagreement.

08: Repeat customers in a huge log

Report date: August 19, 2026 · Role: Full-time experienced SDE · Result: Pass

  1. Behavioral: finding a root cause and optimizing a process.
  2. Count Repeat Customers Across Dates: count customers who visit on different dates.
  3. Follow-ups: one shared time window, then a huge log.
  4. The pass came about two days later.

09: An SDE II Resilience Hub screen

Report date: August 19, 2026 · Role: SDE II · Team: Resilience Hub · Result: Pass

  1. 20 minutes of behavioral, then 30 minutes of coding.
  2. Behavioral: a root-cause deep dive and delivering on a tight deadline.
  3. Rearrange Digits Under an Adjacent-Sum Limit: the candidate clarified the rules, reasoned greedily, covered edge cases, proposed tests, dry-ran two and gave the complexity.
  4. The next-round email came the following day.

12: Tracking package receipts

Report date: August 14, 2026 · Role: Full-time experienced SDE · Result: Pass

  1. Track Package Receipt Gaps: take package IDs out of order; report where the unbroken run from zero ends, plus the missing IDs. Example: 0,1,2,3,100 gives 3 and 4..99.

13: An SDE II loop with industrial OOD

Report date: August 14, 2026 · Role: SDE II · Result: Fail

  1. Four rounds, each with Leadership Principles.
  2. Coding was unfamiliar but at array and hash-map level.
  3. System design started as production architecture until the interviewer said they meant infrastructure.
  4. OOD used dense, industrial Java-like code with unexplained fields, and expected a design-pattern and generics answer rather than plain conditionals.
  5. The rejection came more than a week later, with a one-year cooldown.

19: An L5 boomerang with two teams

Report date: August 6, 2026 · Role: L5 (returning employee) · Result: Offer

  1. First team: Print a Shortest Graph Path, a weighted lottery that picks k winners, and Design an ML Training and Deployment Platform. The candidate felt the ML design did not fit the role.
  2. Second team: whiteboard their own past architecture and solve an Amazon Locker problem.
  3. The offer came two hours later because another deadline was close.

20: A Senior SDE package tracker on AWS

Report date: August 5, 2026 · Role: Senior SDE · Location: Bay Area · Result: Fail

  1. Behavioral: an urgent timeline, turning down a customer request, and lessons learned.
  2. Coding repeated Track Package Receipt Gaps; another candidate said a hash map plus one variable was enough.

21: Installing packages with dependencies

Report date: August 4, 2026 · Role: Full-time experienced SDE

  1. Phone: implement installWithDependencies, installing dependencies first and detecting cycles. Package Dependency Order is the practice version.
  2. Onsite: return the build order for target package x with a DFS topological sort, Visiting / Visited states and O(V+E) analysis.

23: The best k consecutive bags

Report date: August 2, 2026 · Role: SDE II · Stage: Not stated · Result: Waitlist

  1. Find Maximum Total Amount: non-overlapping [l, r, value] intervals and the best window of exactly k consecutive bags.

Applied Scientist and Engineering Manager

14: An Applied Scientist breadth screen

Report date: August 14, 2026 · Role: Applied Scientist L6 · Team: Amazon Ads · Result: Pass

  1. A 30-minute rapid-fire technical screen with no behavioral part.
  2. Statistics, A/B testing, experiment design, power analysis, anomaly detection, bagging and boosting, transformers, attention variants and model families.
  3. Bootstrap Mean and Confidence Interval, plus an optimization without a loop.
  4. The pass came two days later.

17: An Engineering Manager latency calculation

Report date: August 8, 2026 · Role: Engineering Manager

  1. Behavioral: handling a low performer, balancing hard work with team health, and motivating a team.
  2. Given an MLP with HBM at 1 TB/s, 25 MB of SRAM, BF16 at 100 TFLOPS/s and dimension 4096, work out batch-1 and batch-256 latency and show which is memory-bound and which is compute-bound.

Patterns across the reports

  1. The same OA shape. All eight OA reports pair an algorithm task with repo debugging; Spring Boot in 01, 10 and 16, Django in 07 and 18.
  2. Bid-priority inventory. Entries 07, 16 and 22 got the bid-priority allocation task; 04 and 18 got a related contiguous-quality task.
  3. Repeated interview questions. Track Package Receipt Gaps appeared in 12 and 20; Minimum Grid Inconvenience in OAs 10 and 15.

Common questions

What is in the Amazon experienced SDE OA?

An algorithm task plus repo debugging where the AI can suggest but not edit (01, 22), then a Work Simulation and Work Style surveys (22).

How long is the Amazon SDE II phone screen?

Entry 09 had 20 minutes of behavioral and 30 minutes of coding.

How fast does Amazon reply after a phone screen?

The next day in 03 and 09, about two days in 08, and the following Monday in 05.

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
2 comments

Comments

2
FastPrep fren2 months ago

Great share

JaneBeingJaneAUTHOR2 months ago

THANK YOU MY FREN~!