Interview Leaks · Primly Community

Amazon SDE2 system design interview questions they asked me last week (2026)

backend_bekah · 4 replies

Did my Amazon SDE2 onsite last Thursday. Posting while it's fresh because I couldn't find anything recent when I was prepping.

The loop was 4 rounds: 2 coding, 1 system design, 1 behavioral (LP round). All virtual, all on Chime. Interviewers were prompt-ish, one was clearly reading from a script.

System design round: Design a URL shortener. Classic, I know. But they went much deeper than the basic version. They pushed hard on: How you handle 10B shortened URLs at scale Your approach to analytics (click counts per URL, geolocation breakdowns) What happens when the redirect service goes down but the creation service stays up How you'd handle hot keys (viral links getting hammered)

I spent maybe 15 min on the high-level, then the last 30 were basically just the interviewer drilling edge cases. She knew the system design space well. Don't wing this round.

Coding rounds: One medium-ish graph problem (connected components variant) and one that was basically sliding window but they added a constraint halfway through that changed the complexity. Standard LeetCode medium territory, nothing wild.

LP round: All 14 leadership principles are fair game but they seem to cluster around Customer Obsession, Dive Deep, and Ownership for SDE2. I got "tell me about a time you disagreed with your manager" twice across different interviewers, so expect overlaps.

Timeline note: I finished the loop Thursday, recruiter said 5 business days for a decision. Actually heard back in 3. Either good or bad sign, not sure.

Level was SDE2 (L5 equivalent). NYC-based role, hybrid 3 days in office.

Happy to answer questions. What are people seeing in 2026 -- is the LP round getting harder or is it just me?

4 replies

market_realist

LP round getting harder, full stop. I did an Amazon loop in April and got grilled on Bias for Action specifically. The STAR format isn't enough anymore, they want specific metrics and the actual decision tree you ran. My stories from 2 years ago felt thin.

backend_bekah

Yeah the "Dive Deep" questions felt like they wanted me to recall exact numbers from projects. I had to use 'approximately' a few times and I think that cost me points. Noted for next time.

careerveteran

The hot-keys question on the URL shortener is a classic senior-signal probe. Consistent hashing with virtual nodes is the expected answer. If you know that cold, you look strong. Good they probed that far.

visa_vik

Did they ask about your visa status upfront or wait until after the loop? I always worry about that conversation with Amazon specifically.