Booking.com system design interview questions
One question on this site is reported in Booking.com software engineer interviews. Each is a guided run through requirements, back-of-envelope numbers, an interactive design, user flows and deep dives with interviewer follow-ups. Patterns covered: inventory, reservations, locking, queueing, thundering-herd.
Attribution comes from public interview guides and candidate reports, not from Booking.com. It indicates where a question has been asked, nothing more.
Design Ticketmaster
Sell 60 000 seats in ten minutes to a million people at once: hold a seat while someone pays, never sell it twice, and keep the site up when demand is a hundred times supply.
How to prepare for a Booking.com system design interview
Large-company loops run 45 to 60 minutes, expect numbers, and spend most of the time on deep dives. Work each question above in practice mode until you can produce the requirements, the estimates and the flows without looking, then read the interview framework guide for how to structure the hour. The other questions on the site teach patterns that show up in Booking.com interviews under different names.
- Design a URL Shortenerkey-generation · caching · cdn
- Design Slackreal-time · websockets · fan-out
- Design a Payment Systemconsistency · idempotency · ledger
- Design a News Feedfan-out · ranking · caching
- Design YouTubetranscoding · cdn · adaptive-bitrate
- Design Google Mapsgeospatial · routing · graphs
- Design a Matchmaking Systemqueues · scheduling · latency
- Design Ubergeospatial · matching · streaming
- Design a Notification Systemfan-out · multi-channel · idempotency
- Design Google Docscrdt · operational-transform · websockets
- Design an LLM Inference Servicegpu-batching · streaming · scheduling
- Design a Distributed Cacheconsistent-hashing · eviction · replication
- Design a Web Crawlerfrontier · politeness · dedupe
- Design a Rate Limiteralgorithms · counters · redis
- Design Dropboxchunking · dedupe · sync
- Design Search Autocompletetries · ranking · caching
- Design an Ad Click Aggregatorstream-processing · windowing · exactly-once
- Design a Distributed Job Schedulerscheduling · leases · idempotency
- Design a Stock Exchangeorder-book · determinism · event-sourcing