Amazon 2026 SDE Intern VO: Two Technical Rounds Breakdown
Two technical rounds. About 30 minutes of Leadership Principles grilling in each. One custom BFS problem that does not appear on LeetCode. This is what Amazon's 2026 SDE Intern Virtual Onsite actually looks like, documented by a candidate who went through the process in March 2026, as published on DEV Community.
The Format: Behavioral + Coding, Repeated Twice in 2026
Amazon's SDE Intern VO follows a clean two-round structure. Both rounds are identical in format: behavioral questions first, a coding problem to close. No separate HR round, no system design at this stage, just behavioral and coding, twice over.
According to the DEV Community post by net_programhelp, both interviewers were engineers, and communication was smooth and natural throughout the conversations, a detail the candidate specifically noted as a positive.
| Round | Behavioral Duration | Coding Format |
|---|---|---|
| Round 1 | ~30 minutes | Custom BFS state search problem |
| Round 2 | ~30 minutes | Coding problem (see source for full details) |
What this means for prep: If you are walking into this VO expecting to spend most of your time on code, recalibrate. Behavioral consumed roughly half the total interview time across both rounds. Amazon Leadership Principles are not a warm-up, they are a scored evaluation that lasted longer than the coding in both sessions.
Round 1: Deadline Pressure, Follow-Up Depth, and a BFS Problem
Behavioral: Working Under a Tight Deadline
Round 1 opened with a classic Leadership Principles question: describe a situation where you completed a project under a tight deadline. Standard enough on the surface, but the follow-up questioning is where Amazon's process separates itself.
After the candidate introduced the background and explained the situation, the interviewer immediately began probing for specifics. The follow-up questions included the data sources involved in the project and why those sources were chosen, the objective of the analysis and how success was measured, mistakes made during the project, what went wrong, how it was caught, and what was done to fix it, and the decision-making process at each stage.
The behavioral section in Round 1 lasted close to 30 minutes. If you have never practised a single STAR story for 25 minutes of continuous follow-up questions, this duration will catch you off guard. The candidate describes the interviewer as someone who "began digging into details with several follow-up questions" immediately after the initial setup, there is no grace period where you finish your narrative and move on.
This topic maps directly to Amazon LP#5 (Deliver Results) and LP#9 (Bias for Action). The mistakes probe, a recurring follow-up in both rounds, targets LP#7 (Insist on the Highest Standards) and LP#11 (Earn Trust).
What to build into every STAR story before this VO:
- Why you made each specific technical choice, not just what the choice was
- What your biggest mistake in the project was, how you caught it, and what changed after
- How you measured success at the end
- What you would do differently today with the same constraints
Coding: Custom BFS State Search
The coding problem in Round 1 was not a direct LeetCode question, the candidate explicitly flags this. It was a custom state search problem built around BFS logic.
The task structure: start from a defined initial state, explore all possible transitions from that state step by step, and continue until reaching a valid target condition. This is breadth-first search in its structural form, but wrapped in a novel problem domain that required the candidate to model the state correctly before writing any traversal code.
Standard BFS practice (grids, graphs, shortest path problems) builds mechanical fluency with BFS. Amazon's version here tested whether candidates could take an unfamiliar problem domain and translate it into a BFS model from scratch, the harder skill.
The modelling process that works for this type of problem:
- Define the state: what does one "node" in your graph represent?
- Define valid transitions: what operations move you from state A to state B?
- Define the termination condition: what does "valid target" look like?
- Run BFS from the initial state, tracking visited states to prevent cycles
- Return the result when the target is hit, or handle the no-solution case cleanly
LeetCode problems that train this mental model: Open the Lock (752), Sliding Puzzle (773), Word Ladder (127), Word Ladder II (126), Shortest Path in a Grid with Obstacles Elimination (1293).
Round 2: Decision-Making Stories and a Second Technical Problem
Round 2 followed the same structure as Round 1. The behavioral focus shifted from deadline pressure to decision-making processes, how the candidate evaluated options, weighed trade-offs, and committed to a direction under uncertainty.
The DEV Community post notes this section "involved detailed discussion around decision-making processes" and also ran close to 30 minutes. This topic maps to LP#4 (Are Right, A Lot) and LP#2 (Ownership), Amazon wants to see that you have a structured approach to evaluating competing options, not just that you eventually made a choice.
For the coding portion of Round 2, the original DEV Community post contains the full problem details at the source URL below.
The 2026 Prep Playbook for Amazon's SDE Intern VO
Behavioral Prep, Start Here, Not With LeetCode
Build 6-8 STAR stories that each serve 2-3 Leadership Principles. The overlap matters, you will burn through stories faster than expected under 30-minute follow-up questioning. If every story covers only one LP, you will run out of material.
Run the 30-minute drill. Set a timer, tell your STAR story to a friend or mock interviewer, then spend 20 minutes fielding follow-up questions. The goal is not to have a perfect story, it is to have an answer for every follow-up that story can generate. Amazon interviewers probe until they have mapped your full decision tree.
Prepare an explicit mistakes story. Both rounds in this VO included probing around project errors and decisions. Have a real failure with a clear root cause, a specific action you took to fix it, and what you changed in your process afterwards. Deflecting this question or claiming you made no mistakes is a red flag on multiple LPs.
Know your LP pairings for common topics:
- Tight deadline → Bias for Action + Deliver Results
- Disagreeing with a team decision → Have Backbone; Disagree and Commit + Earn Trust
- Decision under uncertainty → Are Right, A Lot + Ownership
- Mistakes and recovery → Insist on the Highest Standards + Earn Trust
Coding Prep, Beyond Standard LeetCode Patterns
BFS is required, but state-space BFS is the target skill. Standard grid and graph BFS problems build mechanical fluency. To handle Amazon's custom problem format, practice problems where the "state" is abstract, lock combinations, word transformations, puzzle configurations, and the model is the hard part, not the traversal.
Model before you code. For a custom problem like Amazon's state search question, spend the first 3-5 minutes defining state, transition, and termination out loud before writing a line of code. Amazon interviewers are evaluating how you decompose novel problems, not just whether you can produce correct BFS code.
Priority LeetCode problems for this VO: 752, 773, 127, 126, 1293.
Day-Of Checklist
- Test video and audio at least 30 minutes before the first round, both rounds are fully virtual
- Have STAR stories written and accessible during the VO, referencing notes is fine
- Keep a notepad or whiteboard nearby for state modelling during coding problems
- Do not rush through behavioral, 30-minute behavioral rounds are expected and are not a warning sign
Common Mistakes to Avoid
Cutting behavioral stories short to save time, Amazon interviewers follow up regardless. A short initial STAR answer produces follow-up questions that sound unprepared. Tell the full story, then answer follow-ups with the same depth.
Jumping to code without modelling state, for a custom BFS problem, writing code before defining state and transitions produces logic bugs that are hard to isolate under interview pressure.
Treating behavioral as lower stakes than coding, in this VO, behavioral consumed more total time than coding. Both are scored equally.
Practising only named LeetCode BFS problems, Amazon's custom state search problem is designed to test modelling ability, not pattern recognition. You need both.
Not having a mistakes story, this came up in the follow-up questioning in Round 1. Having no prepared answer for "what went wrong and what did you do about it" is a significant gap.
Real-world data points
- 2 technical rounds in the Amazon 2026 SDE Intern Virtual Onsite
- ~30 minutes of behavioral per round, approximately 60 minutes of behavioral across the full VO
- 1 custom BFS state search problem in Round 1, not a standard LeetCode question
- At least 4-5 follow-up questions per behavioral story in Round 1
- VO format: fully virtual, both rounds
- March 2026, date the experience was documented on DEV Community
- Round 1 behavioral topic: completing a project under a tight deadline
- Round 2 behavioral topic: decision-making processes and trade-off evaluation
FAQ
How many rounds are in Amazon's 2026 SDE Intern Virtual Onsite? Two technical rounds. Both follow the same format: approximately 30 minutes of behavioral interview, then a coding problem. There is no separate HR round or system design section at the intern VO stage.
What coding problem was asked in Amazon's SDE Intern VO? One round included a custom BFS state search problem, not a standard LeetCode question. The task involved defining an initial state, exploring transitions step by step, and reaching a valid target condition using breadth-first search. Practice problems: LeetCode 752 (Open the Lock), 773 (Sliding Puzzle), 127 (Word Ladder).
How long does the behavioral section take? Close to 30 minutes per round. Interviewers ask detailed follow-up questions after each STAR story, probing decision-making, mistakes, technical choices, and measurement of outcomes. Budget more prep time for behavioral than for coding.
Which Leadership Principles came up in this VO? Based on the topics described, tight deadlines, project mistakes, decision-making processes, the relevant LPs are Bias for Action, Deliver Results, Are Right, A Lot, Ownership, and Earn Trust. Prepare stories that span multiple LPs so you have flexibility under 30-minute follow-up questioning.
Is the Amazon SDE Intern VO conducted online? Yes, the 2026 process described here is a Virtual Onsite. Both technical rounds are conducted online via video call.
Sources & credits
Explore this topic cluster
More resources in Company Placement Papers
Use the category hub to browse similar questions, exam patterns, salary guides, and preparation resources related to this topic.
Paid contributor programme
Sat this this year? Share your story, earn ₹500.
First-person experience reports help future candidates prep smarter. We pay verified contributors ₹500 via UPI per accepted story — with byline.
Submit your story →Ready to practice?
Take a free timed mock test
Put what you learned into practice. Our mock tests match the 2026 pattern with timer, navigator, reveal, and score breakdown. No signup.
Start Free Mock Test →