Interview Leaks · Primly Community

Amazon SDE2 system design interview 2026: what they actually asked me last month

backend_bekah · 6 replies

Just finished my Amazon loop last month and wanted to put something useful out here since I couldn't find anything recent before my own prep.

The role was SDE2 in Seattle, AWS team. Total of five rounds: two coding, one system design, one bar raiser, one behavioral that was basically a second bar raiser.

System design round was the most intense. They asked me to design a notification delivery system at scale, think hundreds of millions of pushes per day across mobile, email, and in-app. Interviewer wanted to dig into fan-out strategies pretty quickly. They didn't care much about the database schema upfront. They wanted me to start with the queue architecture and work outward.

Things they pushed on hard: how do you handle device token staleness, what's your retry strategy if downstream delivery fails, how do you avoid thundering herd if you're sending to a million users at the same time. I drew a lot on Kafka + SQS hybrid approaches. They seemed to like that I was explicit about tradeoffs instead of just naming tech.

Coding rounds were both medium-hard on Leetcode scale. One graph problem (shortest path variant, not just BFS), one on intervals. I didn't see a single easy problem the whole loop.

Bar raiser was purely behavioral, but hard. They went deep on a time I disagreed with a technical decision and the outcome. The follow-up questions kept drilling: what did you do next, what would you do differently, why didn't you escalate. Classic LP probing.

Comp offer came in around $195k base, RSUs around $240k total over four years. This was for a mid-cost-of-living location so Seattle numbers might be a bit higher.

Timeline: recruiter screen on March 18, loop on April 3, offer April 14. Faster than I expected honestly.

If anyone has specific questions about the SD round I'm happy to go deeper.

6 replies

ml_mike

This matches what a friend described from his loop in Q1. The bar raiser behavioral was the part that surprised him too, he thought he was going into a technical discussion. Did your bar raiser interviewer introduce themselves as a bar raiser upfront or did you only find out after?

backend_bekah

Recruiter told me ahead of time that one of my five rounds would be a bar raiser but didn't say which. I figured it out during the round because the interviewer was from a completely different org and kept asking about Amazonian-scale situations I'd never personally been in. If you haven't done one before, just know they're trying to find the ceiling of your experience, not trip you up.

ds_dmitri

The thundering herd question is a classic. Did they expect you to go all the way into jitter/exponential backoff in the notification context or was that overkill for the time you had?

visa_vik

Thanks for the timeline. I'm currently in the process and my recruiter said 'within two weeks of the loop' for the offer, but it's been 10 days and I'm losing my mind a little. Did you get any updates between the loop and the offer, or just silence then the call?

backend_bekah

Pure silence then a call from the recruiter. I emailed once at day 8 just to say I was still excited about the role and ask if there was anything else they needed from me. Recruiter responded same day and said they were finishing debrief. Offer came two days later. I think the proactive email helped keep me top of mind.

careerveteran

Good debrief. The interval problem in a coding round at SDE2 is really common across big tech, worth having clean O(n log n) solutions ready. The design question sounds like they're testing classic distributed messaging patterns. Good thing you called out Kafka tradeoffs explicitly. Interviewers at Amazon get bored when candidates just list tech names.