Did the Airbnb L5 loop in April 2026 and the system design rounds were... not what I expected coming from other FAANG loops.
First, there are two system design rounds in the onsite. One is the classic 45-minute "design X" format. The second one they call an "architecture review" but functionally it's the same thing just scoped to a domain area they think you'll be working in. For me it was platform/infra adjacent, so I got something in the distributed caching space.
What they care about: They want you to think end-to-end, not just data model + API. Availability tradeoffs, what breaks at 100x scale, how you'd know something is wrong. They push hard on consistency vs. availability tradeoffs. Be ready to defend a choice. I said eventual consistency for a guest-messaging scenario and got grilled for 10 minutes on edge cases. Airbnb's actual infra is pretty interesting (Kubernetes + their own service mesh tooling), so interviewers sometimes ask clarifying questions that reveal genuine curiosity about how you'd approach something they're actually thinking about.
What I didn't expect: The interviewer interrupted me with real pushback fairly early. Not hostile, but they weren't waiting for me to finish a beautiful monologue. Interactive from minute 5. They did NOT ask me to draw a database schema first. I started there (force of habit from other companies) and they redirected toward behavior and failure modes faster than I expected.
Rough timing: 10 min clarifying questions and scoping 25 min design + live pushback 10 min deep dive on one component they picked
For context: I have 9 years in platform/infra, this was targeting L5 SWE (not infra-specific leveling, Airbnb doesn't bifurcate that way at L5). Offer came in around $310k total comp for the SF role.
Happy to answer specific questions. The round is hard but it's a pretty good interview actually, tests real thinking.