Mock Interviewer

Ask Coach

Ask Coach
Clarify requirements before you design — kept separate from your stage notes.

Tap a question to start, or type your own below.

Airbnb System Design

Visual Problem Diagram

Airbnb System Design architecture diagram

Scenario

Super Bowl weekend in one city: every listing shows available until four guests pay simultaneously for the same dates—the host gets four confirmations and trust dies. Search must surface geo-relevant stays in < 200 ms while calendars and pricing change constantly. Double-booking prevention and search ranking are the interview core.

Design a vacation rental marketplace where guests search listings by location and dates, book stays, and pay hosts while hosts manage calendars and pricing. Trust collapses on double-booking and stale availability; search must be fast and geographically relevant.

You should support listing CRUD, geo search, availability calendars, booking with payment integration, and reviews. Be ready to explain overlap prevention, geo indexing, and hold/confirm flows under concurrent demand.

Constraints

Functional

Listings with photos, geo search and filters, availability calendar, book/cancel, payments integration, reviews

Non-functional

< 200 ms search p95, 99.99% booking path availability, no double-book on confirmed dates

Scale

150M users, millions of listings, peak holiday booking spikes per city, search QPS >> booking writes

Stages ahead

1Requirement Analysis
2API Design
3High-Level Design
4HLD Extensions
5Trade-offs

Log in to start practicing

Preview the problem below. Sign in to start your timed session, save progress, and use the AI coach.