What to Expect in the Booking.com System Design Interview

The Booking.com system design interview is a 45 to 60 minute round for mid-level and senior engineers. You design a real travel system on a virtual whiteboard: hotel search, room availability, pricing, or the booking flow itself. Interviewers care most about correctness, because a double booking is a real customer disaster. Expect probing on consistency, global scale, and failure handling. Candidates report that clarifying questions at the start are expected, not optional.

A system design interview tests structure, not code. You gather requirements, sketch the parts, choose data stores, and defend every trade-off out loud.

The Question Types Booking.com Asks

• Search and discovery. Design hotel search with location, dates, and filters. This tests indexing, ranking, and caching under heavy read traffic.
• Availability and reservations. Design the booking flow so two users cannot book the same room. This tests consistency, which means all parts of the system agreeing on the data.
• Pricing. Design a system where prices change with demand and currency. This tests caching freshness and safe updates.
• Supporting systems. Candidates also report notification services, review systems, and payment flows.

Signature Walkthrough: Design Hotel Booking

The reservation question fits this company exactly, so prepare it first. Here is the high-level shape.

Requirements. Users search rooms by city and date range. They see live availability and price. A booking must never sell the same room twice. Traffic is read-heavy: many searches per completed booking. State these requirements back to the interviewer before drawing anything.

API and data model. Expose three main calls: search, check availability, and book. Store properties, rooms, rates, and bookings in separate tables. Model availability per room per night, because date ranges overlap.

Search path. Serve search from a search index, which is a data structure built for fast text and filter queries. Update the index from the main database through an events pipeline. Accept slightly stale search results, and say so as a deliberate choice.

The hard part: no double booking. The booking write needs strong consistency. Use a database transaction that checks availability and inserts the booking as one atomic step. Atomic means the step fully happens or fully does not. A common refinement is a short hold: the room is reserved for some minutes while the user pays, then released by an expiry job.

Payments. Make the payment step idempotent, meaning a retried request cannot charge twice. Use an idempotency key per booking attempt.

Global scale. Deploy in multiple regions for latency. Keep search replicated everywhere, but route each booking write to one owning region per property. This avoids write conflicts between regions.

Failure handling. If the pricing service is slow, show cached prices and re-verify at checkout. If a region fails, fail over reads first. State these plans without being asked.

A note on hot properties. A few popular hotels receive a large share of booking attempts. Mention this skew before the interviewer does. A per-property write path with short holds keeps one hot hotel from slowing the rest. This detail separates senior answers from average ones.

What Interviewers Probe

• Consistency boundaries. Know exactly where you need strong consistency (bookings, payments) and where eventual consistency is fine (search, reviews).
• Estimates. Expect questions on queries per second and storage size. Practice quick arithmetic out loud.
• The stale-search trade-off. A search result can be seconds old, but the booking check must be live. Naming this pairing is a strong senior signal.
• Degradation plans. Say what users see when a dependency fails. Silence on failure reads as junior.

How to Prepare

• Master the building blocks. Indexes, caches, queues, transactions, and sharding appear in every travel design. Grokking the System Design Interview teaches them with worked examples.
• Drill this exact domain. Practice hotel booking, then flight search, then a pricing service. Grokking the Advanced System Design Interview covers the harder consistency material.
• Practice talking while drawing. Run two timed mock sessions and narrate every choice.
• Prepare the rest of the loop. See What Is the Booking.com Interview Process Like? (Round by Round) for the other rounds, and Top Booking.com Behavioral Interview Questions (and How to Answer Them) for the values round.