Jobra
🐞Step 1 of Jobra:AI Debugging Rounds
DSA+AIPreparing you for both.
JOBRA · AI DEBUG ROUND (PREVIEW)sum.cpp
// buggy snippet
int total(vector<int>& a, int n) {
    int sum = 0;
    for (int i = 0; i <= n; i++) { // 🐞        sum += a[i];
    }
    return sum;
}
A real codebase. A real bug. You + AI.

Jobra drops you into a broken repo. Find it, fix it, ship it. AI helps you debug like on the job.

Prompt:Correct the loop condition
Tap 'Let Jobra fix it' below to simulate AI debugging...

Amazon Senior (SDE III and above) Interview Guide: Coding, System Design and the Bar Raiser

3 min read

Prepare for Amazon software engineer senior interviews with reported assessment patterns, interview questions, and preparation advice.

In this article
On this page

Last reviewed November 15, 2026.

For SDE III, L6 and senior candidates.

Built by the Codinzhub team from Amazon senior interview experiences that candidates shared. Each experience is one person's interview, so use this as a map, not a promise.

The 30-second version. A referral or recruiter call, a 45-minute phone screen (LP questions and one coding problem), then a loop of four or five one-hour rounds in one day with 15-minute breaks. L6 loops had five rounds, and the recruiter would not say which was coding, design or Bar Raiser. Every round has LP questions. Coding is mostly medium, but the bar is high, and system design often decides the result.

Round-by-round breakdown

Stage 1: Application, where candidates applied

How it works. Candidates had referrals or were contacted by a recruiter. Some were switched between teams for matching several times.

Stage 2: Shortlisting, how candidates moved forward

How it works. A recruiter call about the role, timeline and relocation, about two weeks after a referral. The phone screen came a week later.

Stage 3: Phone screen

At a glance

  • Length: 45 to 90 minutes
  • Questions per round: 2 LP questions and 1 coding problem
  • What was asked: customer experience, obstacles, trees
  • Most common: lowest common ancestor of employees

Questions candidates reported:

Question (our summary)Follow-up reported
Lowest common manager of two employeesMany employees at once
Lock and unlock nodes of a tree (Operations on Tree variant)Vague requirements; build the tree from a parent array

More questions: Browse Amazon questions.

Stage 4: The loop

How it works. Four or five one-hour rounds in one day. Each round ends with time for your questions, so bring a different one for each interviewer.

Coding rounds

At a glance

  • Length: about 45 minutes of coding after LP questions
  • Questions per round: 1 problem with follow-ups on complexity
  • What was asked: trees, DFS, pricing logic, low-level design with changing requirements
  • Most common: vertical order traversal; a price calculator

Questions candidates reported:

Question (our summary)Follow-up reported
Vertical order traversal of a binary treeGet the indexes right
A ride price calculator that maximises company gainChanging rules
A low-level design whose requirements kept changingRework the design
Top K from a streamNone

More questions: Browse Amazon questions.

System design round

At a glance

  • Length: about an hour
  • Questions per round: 1 design
  • What was asked: APIs, schemas, scale, caches
  • Most common: no design repeats

Questions candidates reported: a Kindle reader (APIs, schema, scale); a risk management system; a distributed cache.

More questions: Browse Amazon questions.

Bar Raiser and LP

Questions candidates reported: how you evaluate customer experience; a major unexpected obstacle (it had to be big enough); Ownership; Learn and Be Curious; Dive Deep; Deliver Results.

More questions: Browse Amazon questions.

Stage 5: Decision

How it works. Results came two days after the loop in one report, with no detailed feedback.

The Codinzhub Next-Round Playbook

What senior candidates who moved on did. Put together by the Codinzhub team from the senior experiences in this guide.

  • Prepare 8 to 10 STAR stories, each tagged with Leadership Principles, and make obstacles big enough for the level.
  • In system design, lead with the high-level architecture and scale before APIs and schemas; one candidate failed by starting with details.
  • Practise low-level design where requirements change mid-round.
  • Pace yourself: the loop is a full day.

About this guide

This guide is researched and written by the Codinzhub team. We read every Amazon senior interview experience we could find, kept only what candidates actually described, and rewrote it in our own words. Found something out of date? Share your own experience on Codinzhub and we will update the guide.

Ready for the next topic?

Keep track of what you’ve learned.