Amazon SDE I / New Grad Interview Guide: OA, Four-Round Loop and the Bar Raiser
Prepare for Amazon software engineer new grad interviews with reported assessment patterns, interview questions, and preparation advice.
On this page
Last reviewed November 15, 2026.
For new grads and early-career SDE I candidates.
Built by the Codinzhub team from Amazon new grad interview experiences that candidates shared, including the ones posted on Codinzhub. Each experience is one person's interview, so use this as a map, not a promise.
The 30-second version. Apply online (no referral needed), take a three-part OA (a hard coding question, an AI debugging task in a real project, a work-style survey), then usually no recruiter call: Amazon University Talent Acquisition emails for availability. The loop is three or four one-hour rounds over one or two days: hiring manager, Bar Raiser, and SDE interviewers. Each mixes LP questions with coding or low-level design. Offers often come within a week.
Round-by-round breakdown
Stage 1: Application, where candidates applied
How it works. Candidates applied on the careers site, many without a referral, some in January for an April OA. Others were contacted by HR on LinkedIn. One IIT Roorkee graduate applied through the careers page for the University Talent Acquisition program.
Stage 2: Shortlisting, how candidates moved forward
How it works. After the OA, an email asked for availability, and the loop came about a week later. One candidate passed but the role was filled, so they waited for a new team match.
Stage 3: Online assessment
At a glance
- Length: about an hour of coding, an hour of AI debugging, then surveys
- Questions per round: 1 or 2 coding questions, 1 debugging task, a work simulation
- What was asked: hard DP, adjacent swaps, arrays and hash maps, fixing a Django or React app
- Most common: one hard coding problem with hidden tests
OA questions candidates reported:
| Question (our summary) | What it tests |
|---|---|
| A hard DP problem with growing edge cases | DP |
| Fewest adjacent swaps to group all 0s and 1s | Greedy counting |
| Fix a Django blog so users can publish posts | Debugging with AI |
| A monotonic stack problem (easy and medium) | Stack |
More questions: Browse Amazon questions.
Stage 4: The interview loop
How it works. Three or four one-hour rounds. Most rounds give the last 30 to 35 minutes to coding and the rest to LP questions. The Bar Raiser is usually all LP.
Hiring manager round
At a glance
- Length: about an hour
- Questions per round: AI questions, 1 coding problem, a project
- What was asked: how you use AI, a past project, a medium problem
- Most common: Merge K Sorted Lists; a rate limiter
Questions candidates reported:
| Question (our summary) | Follow-up reported |
|---|---|
| Merge k sorted linked lists | Brute force, then optimal |
| Design a rate limiter from a vague prompt | Clarify everything yourself |
| Build a comment thread from a flat array with parent IDs (frontend) | Rendering |
Coding and low-level design rounds
At a glance
- Length: about an hour
- Questions per round: 1 or 2 problems, or 1 design, plus LP questions
- What was asked: graphs, strings, DP, sliding windows, parking lots, pricing
- Most common: a parking lot; LRU cache; edit distance
Questions candidates reported:
| Question (our summary) | Follow-up reported |
|---|---|
| Parking lot | Concurrency with threads and locks |
| Movie ticket pricing by format, showtime, seat tier and add-ons | Easy to extend |
| Fewest points across reward programmes to pay an amount | Greedy |
| Rearrange a string so no two neighbours match | Heap |
| Edit distance | Allow one full reversal |
| Group anagrams; top K frequent; number of islands | The matrix arrives row by row |
| Sliding window maximum | Monotonic deque |
More questions: Browse Amazon questions.
Bar Raiser round
At a glance
- Length: about an hour
- Questions per round: 2 to 4 LP questions with deep follow-ups
- What was asked: resume deep dive, Dive Deep, risk, influence without authority
- Most common: Dive Deep stories
Questions candidates reported: a calculated risk and its fallback; influencing others without authority; three Dive Deep stories and one on critical feedback; noticing your team was heading the wrong way.
More questions: Browse Amazon questions.
Stage 5: Offer
How it works. One offer email came the Monday after a Thursday loop; another came six days after the onsite. A rejection came after five business days.
The Codinzhub Next-Round Playbook
What new grads who got offers did. Put together by the Codinzhub team from the new grad experiences in this guide.
To get past the OA
- Practise hard DP with many edge cases, and a timed debugging task with an AI assistant.
To get past the loop
- Write a STAR story for every line of your resume's experience and projects.
- Pick a project for the hiring manager where AI clearly helped.
- Practise common low-level design problems and ask which rules may change.
- Keep a sheet of the core problem set with approach, complexity and gotchas.
To get past the Bar Raiser
- Use fresh stories, not ones from earlier rounds.
- Prepare a question for every interviewer.
About this guide
This guide is researched and written by the Codinzhub team. We read every Amazon new grad experience we could find, kept only what candidates actually described, and rewrote it in our own words. Questions are our own short summaries; the practice links point to similar problems, not the exact interview questions. Found something out of date? Share your own experience on Codinzhub and we will update the guide.
Keep track of what you’ve learned.