Amazon SDE2 Behavioral Interview Mistakes and Better Stories

What Amazon says an SDE II does, the story mistakes that make you sound junior, and one example told at SDE I and SDE II scope.

In an Amazon SDE2 loop, Amazon says each interviewer will typically ask two or three behavioral questions about successes or challenges and how you handled them using the Leadership Principles. What changes at SDE II is the scope your stories need to show. Amazon describes the role as delivering features that span the software's life cycle, exercising autonomy, making trade-offs between feature work and operational work, and mentoring others. A story about finishing an assigned task well is a good story, but it is pitched one level down. This page covers how to choose and tell stories at the right level; for the full set of questions, see our Amazon STAR questions by Leadership Principle.

What Amazon says an SDE II does, and why it shapes your stories

Amazon's SDE II interview prep page opens with a short job description, which we think is its most useful paragraph for behavioral preparation. It says an SDE II delivers features that span the software's life cycle, works with the team to design solutions, exercises autonomy and makes trade-offs between feature development and operational work. It adds that you will document how your team's software is built, tested, operated and secured, train team members on it, mentor and guide others, and take part in recruiting and interviewing.

Read that as a checklist for your story bank, because each sentence describes something an interviewer can ask you to prove with a past example. A candidate with no story about trade-offs, operations or mentoring has a visible gap.

The job postings point the same way. All three SDE II postings we opened on amazon.jobs in October 2026 asked for at least three years of non-internship professional software development experience, and two of the three also asked for two or more years of design or architecture work on new and existing systems. The SDE I posting we opened asked for one year of non-internship professional software development experience. That gap is a fair guide to what the interviewer expects your examples to contain: systems you helped design, not only code you were handed a specification for.

How the loop tests behavior at SDE II

Before the loop, the online assessment ends with an 8-minute multiple-choice Work Style Survey related to the Leadership Principles, which our guide to the Amazon online assessment covers in detail. The loop itself is four 55-minute interviews. Amazon's page lists data structures and algorithms, problem solving, and logical and maintainable code among its coding resources, and says to expect at least one question on software systems design.

The behavioral part is spread across the loop. Amazon says the non-technical competencies are based on the Leadership Principles, that different interviewers are assigned to evaluate them, and that each interviewer typically asks two or three behavioral questions, so expect behavioral questions in every interview, alongside the technical areas the loop covers.

One sentence on that page is worth reading twice. Amazon says it focuses on the "what" and "how" of your experiences, as well as the "why" of your decisions. At SDE II we think the "why" matters most, because it is the part of the answer that shows judgment rather than effort.

Mistakes that make an SDE II story sound junior

None of these mistakes make a story false. They make it sound like the work of someone who was told what to build, which is the opposite of what the job description asks for.

The story ends when the code merges

A story that runs from "I was assigned the ticket" to "I shipped the fix" covers only one stage of a feature's life. Amazon describes the SDE II role as delivering features across the life cycle, so a strong story includes the design choice before the code and what happened in production afterwards. If your best example stops at the merge, add what you learned from operating it.

Someone else made the trade-off

Many mid-level stories describe hard work on a priority someone else set. Amazon says an SDE II exercises autonomy and makes trade-offs between feature development and operational work, so the interviewer wants to hear a choice you made, what it cost, and how you explained the cost to the people affected. A trade-off you only executed is not yet your trade-off.

"I" turns into a solo hero

Amazon's best practices for this interview say "I" is better than "we", and that advice is right for your actions. The same list also asks for examples where you sought input and included your team in decision-making, and examples of how you built positive relationships with your team. At SDE II, a story in which you did everything alone can suggest you have not yet learned to work through other people, so say clearly what you did and also how you brought others in.

Nobody else grew because of you

The job description says an SDE II mentors and guides others and helps with recruiting, and the Hire and Develop the Best principle says leaders "take seriously their role in coaching others." You do not need a formal mentoring title to have a story here. Onboarding a new teammate, reviewing someone's design with care, or writing the runbook that let others take on-call shifts all count, as long as you can say what changed for the other person.

The failure story has a villain or no stakes

Amazon asks for examples of taking responsibility for shortfalls or mistakes, and tells candidates not to finger-point or blame-shift. At SDE II the stakes should also be real, such as a missed date, a customer-facing error or a design that did not hold up. A failure that cost nothing, or one where the real cause was another team, reads as a story chosen to avoid the question.

The result has a number but no baseline

Amazon calls itself data-driven and asks for metrics or data where applicable, and its best practices mention gathering metrics to evaluate the effectiveness of your solutions. "Latency dropped to 200 milliseconds" means little without the starting point and the reason it mattered to a customer, so give the before, the after and how you measured it.

A worked example: one story at SDE I and SDE II scope

The scenario below is invented to show the difference in scope, and its numbers are illustrative. It is not a real candidate's answer. The question is a common one rather than one Amazon publishes: "Tell me about a time you took ownership of a problem."

The SDE I version sounds like this. "Our nightly order-export job was timing out, and my lead asked me to look at it. I profiled the job, found a query scanning the whole orders table, and added an index and a date filter. Runtime dropped from about 50 minutes to 8, and the timeouts stopped. I learned to profile before guessing." This is a clear answer with a real result, but the problem, the priority and the scope were all given to the candidate, and the story ends when the fix ships.

The SDE II version starts earlier and ends later. "I was on call and noticed the order-export job had paged us nine times in a month, and each page cost about two hours. Nobody owned it, so I wrote up the pattern and asked my manager to let me spend most of a sprint on it, which meant pushing a planned feature back by a week. I wrote a short design doc comparing three options: an index and filter, incremental exports, and moving the job onto a queue. I chose incremental exports because they fixed the growth problem rather than only the symptom, and because we could switch back to full exports with a flag if something went wrong. A senior engineer reviewed the doc and pointed out a gap in how we handled late-arriving orders, which I fixed before building. I paired with a new teammate on the implementation so that she could own the job afterwards, and we added an alarm and a runbook together. Pages from that job dropped from nine a month to none over the next quarter. The feature slipped by the week I had warned about, and I told the product manager about the delay the day I made the call rather than at the deadline."

The second answer is stronger because it covers what the SDE II job description lists: the candidate spotted the problem, traded feature work for operational work, explained the cost and owned the design. It shows Ownership in thinking long term, Dive Deep in the paging data, Earn Trust in the early warning and Hire and Develop the Best in the handover. It also gives the "why" behind the decision, including the choice of an option that could be reversed, which is the part Amazon says it wants to hear.

It also invites follow-ups, such as why the queue option was rejected or what the new teammate did without help, that the candidate can answer only because the details are real. Amazon tells candidates to prepare to go deep into the details and says it is the interviewer's job to get them, so a story at this level is only as strong as your answer to the third question about it.

How to pick stories at the right level

Start, as Amazon suggests, with your most memorable experiences and their details, and only then ask which principles they show. Before polishing any story, we would test it against the SDE II description with these checks.

• Ask whether you made a decision in the story, or only carried one out, and drop or rework the stories where you only carried one out.
• Check that the story covers more than one stage of a feature's life, such as design and operation, not only implementation.
• Make sure you can name what your choice cost and who you told about it, because that is where a trade-off becomes visible.
• Look for someone else who could do more afterwards because of your work, such as a teammate, a reviewer or an on-call rotation.
• Prefer recent work, since Amazon's phone screening page asks candidates to reference recent situations whenever possible, and SDE II postings ask for non-internship experience.

Across the whole set, aim for at least one design or trade-off story, one operational story, one story about raising someone else's work, one disagreement and one genuine failure. Our guide to behavioral interview questions explains how answers are scored more generally, and the STAR page linked above maps common questions to each principle.

Prepare questions for the interviewers too. Amazon's phone screening page suggests asking about team initiatives, culture or the scope of the role, and the scope answer tells you which of your stories will matter most later in the loop.

Practising out loud with Verve AI

Stories that read well on paper often thin out under follow-up questions, so practise them aloud. Verve AI's AI Mock Interview has an AI recruiter ask questions one at a time, and you can choose its behavioral question bank or select questions from your Question Bank to practise through Custom Questions. If you set up an interview profile with your resume and the SDE II job details, the scoring is evaluated against your background and the role, and afterwards you receive "a detailed performance report with personalized feedback and scoring." Practise before the interview rather than during it: ITPro's report of 14 March 2025, based on internal Amazon documents seen by Business Insider, says the guidelines tell candidates to follow a rule against using generative AI tools during the interview unless explicitly permitted, and that failure to follow it may result in disqualification.

FAQ

How is the Amazon SDE II behavioral interview different from SDE I?

The questions draw on the same Leadership Principles, so the difference is the scope your answers need to show. Amazon describes an SDE II as delivering features that span the software's life cycle, making trade-offs between feature and operational work, and mentoring others. Stories about completing assigned work well are pitched closer to SDE I, while SDE II stories should show decisions you made and why.

How many behavioral questions are in the SDE II loop?

Amazon's SDE II prep page describes four 55-minute interviews and says each interviewer typically asks two or three behavioral questions, with different interviewers assigned different Leadership Principle competencies. Behavioral questions therefore appear alongside the coding and system design work, not in one dedicated round.

Do I need a mentoring story if I have never formally mentored anyone?

You need a story about helping someone else grow, but it does not require a title. Amazon's SDE II description includes mentoring and guiding others, and onboarding a new teammate, reviewing designs carefully or writing documentation that let others take on work all qualify. Say what changed for that person.

Can I use stories from internships or university projects?

The three Amazon SDE II postings we opened in October 2026 each asked for at least three years of non-internship professional experience, and Amazon's phone screening page asks candidates to reference recent situations whenever possible. An older story can still help if it is your best example of a principle, but recent professional work should carry the set.

Sources

• SDE II role description (features across the life cycle, design, autonomy, trade-offs between feature development and operational work, documentation, training team members, mentoring, recruiting and interviewing), online assessment format including the 8-minute Work Style Survey, four 55-minute interviews, at least one question on software systems design, coding resources (data structures and algorithms, problem solving, logical and maintainable code), Leadership Principle competencies assigned to different interviewers, two or three behavioral questions per interviewer, the "what", "how" and "why", memorable experiences first, data-driven and metrics, best practices ("I" over "we", responsibility for shortfalls, no blame-shifting, seeking input, positive relationships, gathering metrics, going deep into details), the interviewer's job to get the details they need: https://amazon.jobs/content/en/how-we-hire/sde-ii-interview-prep
• Leadership Principle wording (Ownership, Hire and Develop the Best "take seriously their role in coaching others", Dive Deep, Earn Trust): https://www.amazon.jobs/content/en/our-workplace/leadership-principles
• Reference recent situations whenever possible, and questions to ask about team initiatives, culture or the scope of the role: https://amazon.jobs/content/en/how-we-hire/phone-screening
• SDE II posting requirements (3+ years non-internship professional software development, 2+ years design or architecture), opened 2026-10-25: https://www.amazon.jobs/en/jobs/10587867/software-development-engineer-ii-aws-dynamodb
• SDE II posting with the same requirements, opened 2026-10-25: https://www.amazon.jobs/en/jobs/10588004/software-development-engineer-ii-sagemaker-ai-inference
• SDE II posting asking for 3+ years of non-internship professional software development, 3+ years of building complex software systems and 2+ years of designing and developing large-scale software systems, rather than the design or architecture line, opened 2026-10-25: https://www.amazon.jobs/en/jobs/10585712/software-development-engineer-ii-aws
• SDE I posting requirement (1+ years non-internship professional software development), opened 2026-10-25: https://www.amazon.jobs/en/jobs/10580014/software-development-engineer-i
• Amazon's guidance to candidates on GenAI tools during interviews, as reported in March 2025 from documents seen by Business Insider: https://itpro.com/business/careers-and-training/amazon-bans-ai-tools-during-job-interviews
• Verve AI Mock Interview: AI recruiter asks questions one at a time, behavioral question bank, Custom Questions, interview profile used for scoring against background and role, "a detailed performance report with personalized feedback and scoring": https://docs.vervecopilot.com/features/mock-interview