Design a parking garage reservation system
Let drivers find and reserve spots in parking garages ahead of time and pay for them.
Functional requirements
- Search garages with free spots for a time window
- Reserve a spot and get a confirmation
- Cancel a reservation; garage staff see occupancy
Non-functional requirements
- A spot is never double-booked
- Search responds in under 300 ms
- Payments are recorded exactly once
Scale
- 5,000 garages, 1M spots
- 200K reservations per day
- Traffic peaks before events and holidays
How you’ll be scored
9 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design a parking garage reservation system”, that starts with: Search garages with free spots for a time window; Reserve a spot and get a confirmation; Cancel a reservation; garage staff see occupancy. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (5,000 garages, 1M spots; 200K reservations per day; Traffic peaks before events and holidays) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: A spot is never double-booked; Search responds in under 300 ms; Payments are recorded exactly once. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe reservations, consistency and sql here. This is an easy problem, so interviewers expect the fundamentals done cleanly: a clear request path, the right kind of data store, and a reason for each component.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.