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 Reservation System Design

Visual Problem Diagram

Airbnb Reservation System Design architecture diagram

Scenario

Picture two families who each want the same beach house for the same holiday weekend. Both open the listing, both see the nights as free, and both start typing their card details within a few seconds of each other. The house can only go to one family, so the booking system has to pick a winner and tell the other family the dates are gone before anyone is charged for a stay that cannot happen. The part of the system that does this is called a reservation system, and it is hard because browsing can be slightly out of date while the final booking must never be wrong. A host's calendar imported from another website makes it harder, because it can arrive late and disagree with a stay that is already confirmed.

Stuck on where to start? Ask Coach

Clarify this problem here, or open Pathway Coach if you want a prep plan first.

Free Coach trial
How should I start prep?

This problem asks you to design a reservation system for a short-term rental marketplace, which is the part of the product that decides who gets which nights at a house or apartment. Think of a website where hosts list their homes and guests pick dates, see a price, pay, and receive a confirmation. A host can block nights, and a host can bring in dates from a calendar that lives on another website. A guest who changes their mind can cancel and get money back according to the host's rules.

In the interview you need to explain five things. First, how two guests can both see the same nights as free while only one of them ends up owning those nights. Second, how the nights stay set aside for a few minutes while a guest is typing in card details, and how they come back if the guest never finishes. Third, how the price the guest was shown, with taxes and fees, stays the same until the card is charged. Fourth, how pressing Pay twice, or a network retry, never charges the card twice. Fifth, why a calendar imported from another site can never erase a stay that is already confirmed. Search ranking and reviews can stay thin.

Constraints

Functional

Each listing has a calendar of free and blocked nights. A guest can ask which dates are free. They can reserve a date range and then confirm it. They see a price before they pay. They can cancel and get money back. A host can import and export a calendar.

Non-functional

Only one confirmed stay may own each night of a listing. The price shown at the start of checkout does not change before payment finishes. A second attempt to pay or to refund does not move the money twice. The guest who loses hears it during checkout.

Scale

Millions of listings. Browsing which nights are free is the heavy read. Booking writes are fewer, but a holiday weekend or a viral house makes many guests race for the same nights. A host's outside calendar arrives late.

Stages ahead

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

Not ready to design yet?

Try the free Coach trial — ask how to prep, what to practice first, or how InterviewCrafted works. Sign in when you want to start this problem.

Try Coach free

Log in to start practicing

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

Want full access now? View Pro pricing