Design a restaurant reservation system

Q: Design a restaurant reservation system

This question evaluates skills in system architecture and engineering, including data modeling, API design, concurrency control to prevent double-booking, availability and scheduling logic, scalability under traffic spikes, and operational concerns like auditability and low-latency queries.

Q: How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

Q: What difficulty level is this interview question?

This is a easy difficulty System Design question, commonly asked during Onsite rounds at C3 AI.

Q: What role is this question designed for?

This question is commonly asked for Software Engineer candidates at C3 AI during technical interviews.

Question

Problem

Design a restaurant reservation system similar to common booking products.

The system should allow customers to search availability and book tables at a restaurant, and allow the restaurant to manage tables and reservations.

Core requirements

Customer-facing

View a restaurant’s availability for a given date/time and party size.
Create a reservation (name/contact, party size, desired time, special notes).
Modify/cancel a reservation.
Receive confirmation and reminders (email/SMS/push).

Restaurant-facing

CRUD restaurants, operating hours, blackout dates/holidays.
Configure table inventory (table IDs, capacities, combinable tables).
View upcoming reservations; mark no-shows/seated/completed.

Non-functional requirements

Prevent double-booking (correctness is critical).
Low latency for availability lookup (e.g., p95 < 200–300ms).
Handle spikes (e.g., lunch/dinner hours, popular restaurants).
Auditability (who changed/cancelled what) and idempotent APIs.

Assumptions (state clearly)

Multi-restaurant platform (many restaurants).
Reservations are time-bound (e.g., 90-minute default duration, configurable).
Timezone-aware scheduling.

What to cover in your design

Data model (tables/reservations/locks/slots).
APIs and main flows (search availability → book → confirm → remind).
Concurrency control strategy to avoid double-booking.
Scaling approach and caching strategy.
Edge cases: cancellations, no-shows, walk-ins, table combinations, overbooking/waitlist.