InterviewLegend

Design a Hotel Booking System

Signature problem
Alex Chen45 min readAdded 314 real interview reports

A hotel booking site sells rooms it doesn't own. Hotels tell it how many rooms they have free on each night and at what price. Guests search a place and a set of dates, see the hotels with a room free on every night of the stay, and book one. The site has to make sure two guests never get the last room, and that it never sells a room the hotel already sold somewhere else. This prompt comes up often in Rippling's design rounds, at SDE-2, senior and staff levels, and sometimes as the first design screen. Reported versions focus on searching rooms by date and location, on reserving them, and on taking in availability from third-party hotels. Some add a twist. The hotel may be listed on other booking sites too, or the interviewer wants the design to handle a ten-room guesthouse and a large chain at the same time.

The Rippling angle
Rippling's version is a marketplace for inventory it doesn't own. Availability comes from the hotels' own systems, and one room can be on sale in several places at once. The grade leans on the data model, so write real tables with keys and constraints plus the SQL that books a room. Sharding can wait until someone asks.

RipplingPremium lesson · System design round

The Rippling design, worked end to end.

  1. The API and data modelSystem design · Signature problem
  2. The design, drawn out2 diagrams
  3. 5 deep divesWith the tradeoffs
Get the Rippling questions

$49 a year · all 107 companies · instant access

314 Rippling interview reports · guide updated

Rippling interview guide

Know what Rippling asks before you walk in.

30 coding · 5 system design · 28 behavioral questions

Get Premium$49 a year · Instant access
Or start freeNo card.

Get their questions first.

Had your Rippling interview?How we research

InterviewLegend is independent and not affiliated with or endorsed by any company it covers.