Amazon SDE Onsite Interview Questions: 9 Experiences

Shared by janebeingjane ·
Company
Amazon
Reports
9 interview reports
Level
Unknown
Stages
Onsite

Nine Amazon onsite reports posted in October 2026, from two SDE interns and seven SDE II candidates, with the coding, system design and LLD tasks.

At a glance

  • Process: Interns: two technical rounds of coding and behavioral questions (01, 02). SDE II: three to five rounds mixing coding, system design and LLD (03, 05–07, 09). Report 04 had two rounds, then an interviewer no-show; 08 had done two of four planned rounds.
  • Asked recently: Interns: no design tasks. SDE II: LLD and system design in five of seven reports each, graph or grid traversal in four, a job scheduler twice (07, 09).
  • Outcomes: Interns: both rejected (01, 02). SDE II: an offer in 07, rejections in 03, 06 and 09, no answer yet in 04, 05 and 08.
  • Difficulty: Interns: 02 called it average. SDE II: 03 called it hard; 09 found the first coding round pretty easy and the first LLD round the toughest.
  • Practise first: Shortest Grid Path with Obstacle Eliminations from the offer loop, and Design a Scheduled Job Execution System for the scheduler topic.

Coverage: All posted in October 2026; dated interviews ran March to October 2026. Interns: AWS database team (02), APAC (01). SDE II: India (05, 08, 09), AWS (03), no location (04, 06, 07).

Each hiring level has its own section and tables: SDE intern (01–02), then SDE II (03–09).

SDE Intern

What came up

Both intern loops were coding plus behavioral questions, with no design round.

Questions we found

Last seen is the interview month when the report gave one, otherwise the posting month.

Algorithms / Data Structures

Question Reports Last seen
Minimum Window Substring 1 ~May 2026
Minimum Length After Spacing Equal Characters 1 ~May 2026
4Sum 1 ~May 2026
Maximum Candies per Child 1 ~May 2026
Squirrel Nut Collection Shortest Path 1 Mar 2026
Longest Increasing Subsequence (custom variant) 1 Mar 2026

Intern timelines

01: APAC intern, four coding tasks and a project grilling

Interview date: about May 2026 · Report date: Oct 10, 2026 · Role: SDE Intern, July–December cohort · Result: Rejected

Online assessment: two coding problems, then nine sections of Leadership Principle questions.

Technical round 1

  1. Smallest window. Find the shortest part of one string that holds every character of another, repeats included. In "timetopractice", the shortest part covering "toc" is "toprac". The candidate used a sliding window with a count map: Minimum Window Substring.
  2. Spread out equal letters. Rearrange letters so equal ones sit at least k apart, adding blank slots if needed, and return the shortest length. For a, b, a, a, a, b with k = 3 the answer is 13. The candidate placed the most frequent letters first: Minimum Length After Spacing Equal Characters.

The candidate gave several approaches to each and felt good.

Technical round 2 (a week later, two interviewers)

  1. Project deep dive, about 20 minutes, on the candidate's image classifier: why ResNet50, transfer learning, how the model was judged, and how they caught wrong AI-tool suggestions. Both kept circling back.
  2. Four numbers that add up to a target. Sorting plus two pointers, or hashing: 4Sum.
  3. Candies per child. Piles can be split but not merged, and each of k children gets candy from one pile. Find the most each can get. The candidate binary searched on the answer and dry-ran the code: Maximum Candies per Child.

The candidate thinks the project answers cost them. The rejection came about six weeks later, with no feedback.


02: Summer intern, AWS database team

Interview date: March 2026, in person · Report date: Oct 7, 2026 · Role: SWE Intern, summer 2026 (bachelor's, referred) · Result: Rejected

The online assessment was in December 2025. The onsite had two rounds, one with a manager and one with an engineer. Behavioral questions covered conflict and generative AI. The candidate called it average difficulty.

  1. Squirrel and nuts. The shortest total walk for a squirrel carrying nuts to a tree: Squirrel Nut Collection Shortest Path.
  2. A custom twist on longest increasing subsequence. The report did not describe the twist, and the candidate needed hints to finish. Our Longest Increasing Subsequence is the standard version.

SDE II

What came up

Every SDE II report had coding. Five had low-level design (04, 05, 07, 08, 09) and five had system design (03, 05, 06, 07, 09). Graph or grid traversal showed up in four (03, 04, 05, 07), and two asked for a job scheduler (07, 09).

Questions we found

Last seen is the posting month unless the report gave an interview month.

Algorithms / Data Structures

Question Reports Last seen
Are Two People Relatives in a Family Tree? 1 Oct 2026
Sliding-Window Rate Limiter 1 Oct 2026
Word Break 1 Oct 2026
Next Greater Element I 1 Oct 2026
Search in a Rotated Sorted Array 1 Oct 2026
Word Dictionary with Wildcard Find 1 Oct 2026
Matrix walk from all edges (no detail) 1 Oct 2026
Minimum Time to Spread Through a Grid 1 Oct 2026
First Unique Character in a Stream 1 Oct 2026
Search a Row and Column Sorted Matrix 1 Oct 2026
Shortest Grid Path with Obstacle Eliminations 1 Oct 2026
Minimum Obstacle Removals on a Shortest Grid Path 1 Oct 2026
Top K Upvoted Songs by Artist 1 Oct 2026
Connect N Ropes With Minimum Cost 1 Jun 2026
Binary Tree Spiral Level Order 1 May 2026
0/1 Knapsack (variant) 1 May 2026

System Design

Question Reports Last seen
Fleet software deployment 1 Oct 2026
Smart meter monitoring 1 Oct 2026
Examination system 1 Oct 2026
Support chat with issue prediction 1 Oct 2026
Scheduled job execution 1 Oct 2026
Scheduler for dependent jobs 1 Jun 2026
Database migration behind one API 1 Jun 2026

Low-Level Design (LLD/OOD)

Question Reports Last seen
Train ticket booking 1 Oct 2026
Package delivery assignment 1 Oct 2026
Agentic chatbot 1 Oct 2026
Multi-channel notifications 1 Oct 2026
Streaming subscription system 1 Jun 2026
Saga orchestrator classes 1 Jun 2026
Delivery estimate service 1 May 2026

SDE II timelines

03: AWS, four whiteboard rounds

Interview date: October 2026 · Report date: Oct 28, 2026 · Role: SDE II · Background: master's, switching jobs, via an agency · Result: Rejected six days later

The team was picked before the onsite, and the schedule came two days ahead. All code was on a whiteboard and did not need to compile. Each round was about 30 minutes of a task plus behavioral questions. The candidate rated it hard.

  1. Are two people related? Given a family tree, check whether two people are relatives. It looks like a common-ancestor task, but the family graph is not a simple tree. The candidate ran a breadth-first search over both people's ancestors and looked for overlap: Are Two People Relatives in a Family Tree?.
  2. System design, possibly the bar raiser: roll software out to a fleet of machines and orchestrate the deployment. Ours is Design a Fleet Software Deployment and Orchestration System.
  3. Throttling API. Each user gets a set number of requests in any time window: Sliding-Window Rate Limiter.
  4. Hiring manager: titles with bad spacing. Is a queried book title in the library, when the query may have extra or missing spaces? Stripping spaces from the library was turned down. An inverted index of library words was accepted, but not the matching after it. The interviewer wanted backtracking that cuts the string into pieces and checks each piece is a known word: Word Break.

Behavioral topics: hardest project, conflict, influencing a teammate, a rushed decision, AI projects, and acting without telling the manager. The incident story the candidate told for that last one fell flat. They now think it was a Bias for Action question. Only the manager round felt weak.


04: A loop that stalled after a no-show

Report date: Oct 26, 2026 · Role: SDE II · Result: No answer at posting time

A recruiter invited the candidate to two in-person elimination rounds. A month of silence later, two more were booked. The online interviewer never joined, and the recruiter never replied.

  1. Coding. A matrix walk starting from all the edges, with no more detail given. Then a trie: insert words, and find words that may hold wildcards: Word Dictionary with Wildcard Find.
  2. LLD: a train ticket booking service: Design a Train Ticket Booking Service.

05: Hyderabad, grid, chatbot and smart meters

Report date: Oct 24, 2026 · Role: SDE II · Background: 5 years · Result: No answer after 2–3 weeks

Each round also had two Leadership Principle questions.

  1. Coding: a grid task like rotting oranges, where a state spreads to neighbors each minute. It went smoothly: Minimum Time to Spread Through a Grid.
  2. LLD: a chatbot that takes user questions and generates answers. The basic flow got done, but time ran out for more: Design an Agentic Chatbot Domain.
  3. System design: collect readings from home smart meters and show usage on a dashboard: Design a Smart Meter Electricity Monitoring System.

06: Design first and last

Report date: Oct 22, 2026 · Role: SDE II · Result: Rejected

  1. System design: an examination system, plus the SOLID principles, an ownership story and how generative AI fits the candidate's work: Design a Scheduled Examination Platform.
  2. Coding: the first unique element in a data stream, plus Dive Deep and Invent and Simplify stories: First Unique Character in a Stream.
  3. Bar raiser, coding: find a value in a matrix whose rows and columns are sorted, plus Deliver Results and Learn and Be Curious: Search a Row and Column Sorted Matrix.
  4. Hiring manager, system design: guess a customer's problem from past orders and route them to the right support agent. Follow-ups: chat traffic spikes, why EC2, why SQL over NoSQL, autoscaling, consistency and ACID. Stories on Earn Trust and disagreeing with a manager: Customer Support Chat Platform.

07: L5 offer, a repo-fix OA and two grid tasks

Report date: Oct 22, 2026 · Role: SDE II (L5) · Result: Offer

Online assessment: one coding question, then a project with tests already written. The job was to find broken or missing code and finish it until all tests passed. The candidate chose Java with Spring Boot; JavaScript and Python were also offered.

Four interview rounds. The report lists the tasks but not their rounds.

  1. LLD: notifications for many users, each set up for SMS or email. Talk covered Factory, Strategy and Singleton, errors, and adding channels later: Design an Extensible Multi-Channel Alerting Platform.
  2. Grid with obstacles: fewest steps from top-left to bottom-right, then a follow-up allowing up to k obstacle removals: Shortest Grid Path with Obstacle Eliminations.
  3. Same grid, new goal: the fewest removals while still taking a shortest route: Minimum Obstacle Removals on a Shortest Grid Path.
  4. System design: a scheduler for one-time and repeating jobs. Schema, scaling, MongoDB versus DynamoDB, a queue versus in-memory, Kafka and errors: Design a Scheduled Job Execution System.
  5. Top songs, part coding and part LLD. One call upvotes a song by an artist, another returns that artist's top k. Updates had to run in log time with a sorted set: Top K Upvoted Songs by Artist.

08: Fintech backend, two rounds in

Interview date: October 2026 · Report date: Oct 17, 2026 · Role: SDE II · Location: India · Background: 5 years, Java · Result: Waiting

The recruiter shared prep notes and laid out four rounds: two coding and two design, with Leadership Principles in each. The first two ran back to back.

  1. Coding, 60 minutes, in Amazon's plain shared editor with no compiler. First, the next bigger value to the right, with a monotonic stack: Next Greater Element I. Then binary search in a rotated array: Search in a Rotated Sorted Array. Bias for Action and Dive Deep stories, each with several follow-ups.
  2. LLD, 60 minutes, on an online whiteboard: package delivery for an online store. Assign packages to agents, track status and handle failed attempts. Follow-ups: Prime orders first, and the best-rated agent for Prime customers: Design a Package Delivery Assignment Domain. Stories on Deliver Results and recovering from a surprise.

09: Alexa Devices, Bangalore, five rounds

Interview dates: May 23 and June 13, 2026 · Report date: Oct 4, 2026 · Role: SDE II, Alexa Devices · Background: 2.8 years · Result: Rejected June 19

  1. Coding: a zig-zag tree level order and a knapsack variant, both done in 30 minutes. The knapsack went from plain recursion to memoization: Binary Tree Spiral Level Order and 0/1 Knapsack, the base version. Self-rating: strong hire.
  2. LLD: a delivery estimate service. Two Leadership Principle answers went badly first. Then the candidate struggled to pin down the requirements, even with hints. Self-rating: no hire. Try Design a Delivery Estimation Domain.
  3. System design, three weeks later, with a veteran manager: a scheduler for jobs that depend on each other. Topics: Kahn's algorithm, queues, partitioning, the database, failures, backoff retries, logging, scaling: Design a Distributed Recurring Workflow Scheduler.
  4. Bar raiser, coding: a long, vague Alexa-device story that hid connect-the-ropes. Wording about a maximum of minimums made the candidate think of binary search at first. After one hint the candidate used a min-heap, then printed which devices got merged. The recruiter warned that hints can count against you: Connect N Ropes With Minimum Cost.
  5. Extra LLD, about 1 hour 45 minutes, because round 2 gave too little signal. First a streaming subscription system: Design Movie Subscription Pricing. Then moving users to a new database behind the same API: Design Zero-Downtime Database Migration. Last, saga step, context and orchestrator classes: Design a Workflow Orchestrator Domain. The candidate struggled with the last two. Self-rating: lean hire.

The candidate blames the rejection on the LLD rounds.


Common questions

How many rounds is the Amazon SDE II onsite?

Three in 05, four in 03, 06 and 07, and five in 09, where an extra LLD round was added. Report 08's recruiter planned four.

Does the Amazon SDE II onsite include low-level design?

In five of seven reports (04, 05, 07, 08, 09). Reports 03 and 06 had system design instead.

Are Leadership Principle questions in every Amazon round?

In every round of 03, 05, 06 and 08, and in rounds 1–4 of 09 (its extra LLD round mentions none). Report 08's recruiter said so up front.

Do Amazon SDE intern onsites include system design?

Not in these two reports (01, 02). Both were coding plus behavioral, and 01 added a long project talk.

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.