Amazon SDE2 mock interview

Mid-level loop with substantive system design and project-scope LP stories. The level where down-leveling to SDE1 happens — usually because LP scope reads as 'task-level' instead of 'project-level'.

  • 4-5
    Onsite rounds
  • ~32
    Days hire-to-offer
  • Project
    LP scope expected
  • Free
    First mock

Why Amazon SDE2 is the level most international candidates target — and where most down-level

Per IGotAnOffer's Amazon SDE2 guide and Glassdoor's SDE2 hiring data, the average SDE2 candidate takes 32 days to get hired, vs Amazon's overall 28-day average. The extra time mostly goes into the Bar Raiser debrief and team matching — not interview rounds themselves. The level is competitive: SDE2 is where the largest international-student cohort applies, and it's also where down-leveling to SDE1 is most common.

The down-level signal isn't usually weak coding. It's LP scope reading as task-level instead of project-level. A story about a 2-week feature delivery is SDE1 scope; a story about a system owned across 2 quarters with cross-team dependencies is SDE2 scope. The behavioral round explicitly grades this distinction, and the Bar Raiser pushes harder on it than at SDE1.

System design at SDE2 is substantive but not multi-region (that's SDE3 territory). What it requires: concrete scale numbers, articulated bottlenecks, and at least one explicit trade-off. Designs without numbers — even if architecturally sound — read as junior.

What the loop looks like

Round-by-round

  1. 01

    Online Assessment

    Pre-onsite
    70-90 min

    HackerRank/Chime — 2 DSA coding (medium-hard) + work-style simulation. Bar is higher than SDE1 on optimization passes.

  2. 02

    Recruiter screen

    Pre-onsite
    15-30 min

    Fit, target team, level expectation. Sometimes hints at SDE1 backup if SDE2 signal is borderline.

  3. 03

    Technical phone screen

    Pre-onsite
    60 min

    1 coding question + 2-3 LP follow-ups. Production-quality code expected on first pass.

  4. 04

    Coding rounds × 2

    Onsite
    60 min each

    DSA medium-hard with LP follow-ups (10-12 min per LP block). Production code quality graded — edge cases, naming, error handling.

  5. 05

    System design

    Onsite
    60 min

    Substantive at SDE2 (not 'light' as at SDE1). Common: design Amazon Ads server, recommendation system, distributed cache. Multi-region NOT required (that's SDE3).

  6. 06

    Behavioral / LP

    Onsite
    60 min

    3-4 LPs evaluated, project-scope stories required. 'I owned this feature' beats 'I contributed to this feature'.

  7. 07

    Bar Raiser

    Onsite
    60 min

    Senior outsider with veto. Tests Dive Deep + Deliver Results + Customer Obsession. Sharper bar than SDE1 — looking for project-level scope and metric clarity.

Question bank

Real interview questions reported by candidates

  • LP

    "Tell me about a project you owned end-to-end. What were the trade-offs you made? (Ownership)"

    Source · IGotAnOffer Amazon SDE2 guide 2025, interviewing.io Amazon LP 2025
  • LP

    "Describe a time you simplified a complex process. What did you cut and why? (Invent and Simplify)"

    Source · designgurus.io Amazon LP guide 2025, levels.fyi LP guide
  • LP

    "Tell me about a time you had to make a decision with incomplete data. (Bias for Action / Are Right A Lot)"

    Source · aceround.app Amazon LP playbook 2025, IGotAnOffer 2025
  • LP

    "Describe a customer issue you discovered that wasn't escalated to you. (Customer Obsession)"

    Source · levels.fyi Amazon LP guide 2025
  • LP

    "Tell me about a time your work was challenged in a debrief. How did you respond? (Have Backbone; Disagree and Commit)"

    Source · interviewing.io Amazon LP 2025
  • System design

    "Design Amazon Ads server. Discuss components, scalability, ad targeting pipeline, billing/attribution. ~1h25min sessions reported."

    Source · Glassdoor Amazon SDE2 reports 2025, Saiteja Dasari Medium SDE2 experience
  • System design

    "Design a distributed cache or message queue. Discuss eviction strategy, consistency model, partition tolerance."

    Source · Onsites.fyi 2025 Amazon SDE2 guide, IGotAnOffer Amazon SDE2 2025
  • Coding

    "Implement an LRU cache with thread safety. Follow-up: support TTL eviction."

    Source · Onsites.fyi 2025 Amazon SDE2 guide, LeetCode Discuss Amazon SDE2 2025
  • Coding pattern

    "String/array problem with multiple optimization passes — usually 3 levels: brute, optimal time, optimal time+space."

    Source · Glassdoor Amazon SDE2 reports 2025, GeeksforGeeks Amazon SDE2 sets
  • Coding pattern

    "Tree/graph problem with non-obvious edge case the interviewer adds mid-interview. Tests adaptability."

    Source · interviewkickstart.com Amazon SDE2 guide 2025, LeetCode Discuss Amazon SDE2 2025
Common signals to fix

What gets you rejected at this level

  • LP scope reads as 'task-level' instead of 'project-level'

    SDE2 #1 down-level reason. Stories about a single PR or a 2-week feature read as SDE1 scope. SDE2 needs stories spanning quarters: a system you owned, a project with cross-team dependencies, a decision you made that affected the team's roadmap.

  • Single-region thinking on system design

    Wait — SDE2 design does NOT require multi-region (per IGotAnOffer SDE2 guide). What it does require: concrete scale numbers, articulated bottlenecks, and at least one explicit trade-off (consistency vs availability, latency vs cost). Designs without numbers read as L4-equivalent of Google.

  • Generic LP answers without follow-up depth

    At SDE2 the Bar Raiser pushes 5-8 minutes of follow-ups per story. Memorized answers fall apart at depth. Practice having someone push back on your stories — 'why did you choose X over Y?' 'what happened when Z went wrong?' If you can't answer, the story isn't deep enough.

  • No 'I' in cross-functional LP stories

    Cross-functional projects naturally invite 'we' phrasing. SDE2 needs explicit individual ownership inside cross-functional context — 'I drove the architecture decision across 3 teams', not 'we agreed on the architecture across 3 teams'.

  • Code-quality issues in onsite rounds

    SDE2 expects production-quality code: edge cases handled without prompting, sensible naming, error paths thought through. Whiteboard-pseudocode-style answers that pass at SDE1 read as junior at SDE2.

How Applr's AI mock interview tracks Amazon's SDE2 rubric

Applr loads the SDE2-specific rubric — substantive (not light) system design, LP follow-ups attached to every coding round, Bar Raiser with 5-8 min follow-up depth on Dive Deep and Deliver Results, and behavioral grading on 'project-level' vs 'task-level' scope.

The behavioral round explicitly flags task-scope stories with a suggested rewrite that surfaces the project-level ownership signal. Bar Raiser follow-ups are calibrated to actual Amazon depth — if your story can't survive 'why did you choose X over Y?' and 'what was the cost of that decision?', the scorecard records the gap.

Adjacent loops

Related practice

FAQ

How is SDE2 different from SDE1 in scope expectations?

Per IGotAnOffer's Amazon SDE1 vs SDE2 comparison and Saiteja Dasari's 2025 SDE2 Medium write-up: SDE2 must show project-level ownership, not just task ownership. A feature you delivered in 2 weeks is SDE1 scope; a system you owned across 2 quarters with cross-team dependencies is SDE2 scope. The behavioral round explicitly grades this — 'I led' beats 'I contributed', and the difference between getting an SDE2 vs SDE1 offer often lives in whether your strongest LP stories surface that scope.

Does Amazon SDE2 require multi-region system design?

No, per IGotAnOffer's Amazon SDE2 guide and 2025 Glassdoor reports — multi-region thinking is SDE3 territory. SDE2 needs concrete scale numbers, articulated bottlenecks, and at least one explicit trade-off (consistency vs availability, latency vs cost) on a single-region scaled design. Spending the design round on multi-region details is over-prep that costs you depth on the dimensions actually graded.

What does the SDE2 Bar Raiser test that SDE1 doesn't?

Per multiple 2025 Bar Raiser write-ups (Carlos Arguelles' Memoirs of an Amazon Bar Raiser Medium, alifeengineered.substack.com): SDE2 BR pushes harder on Dive Deep (can you debug an unfamiliar codebase? what did you actually do when X broke?) and Deliver Results (where's the metric? what was the cost of the decision?). The BR also looks for evidence of coachable leadership — managing without authority, mentoring junior engineers, navigating ambiguity. SDE1 BR is more about basic LP coverage.

What's the typical SDE2 timeline?

Per Glassdoor data and IGotAnOffer's Amazon SDE2 guide: candidates take an average of 32 days to get hired, slightly above Amazon's overall 28-day average. Bar Raiser debrief is 4-7 days after onsite. International candidates may face longer timelines due to visa coordination.

How does SDE2 compare to Google L4 / Meta E4?

Same band, very different rubrics. Google L4 has NO mandatory system design (most contrarian fact for Google L4); Meta E4 has system OR product design with the new AI-enabled coding round; Amazon SDE2 has substantive system design plus LP-heavy behavioral. If you're applying to all three, prepare each loop separately — generic 'mid-level FAANG prep' under-serves all of them.

Does Amazon support OPT/H-1B sponsorship at SDE2?

Yes generally, but timing varies by team and pipeline. SDE2 is the most common Amazon hiring level for international candidates with 2-5 years of US-based experience or strong international backgrounds. Confirm sponsorship slot with recruiter during the screen — some teams have visa-quota constraints that affect timing.

Ready to practice for Amazon?

Start free →