C3.ai·Software Engineer·Onsite - System Design / Architecture
Jun 2026
System design round at C3.ai focused entirely on building a restaurant reservation platform. The scope was pretty wide and they kept pushing into deeper territory whenever I thought I'd covered something.
- Design the data model for a restaurant reservation system. What entities do you need and how do they relate?
- Walk me through the booking API. What endpoints do you expose for searching availability, holding a slot, confirming, canceling, and modifying a reservation?
- Two users try to book the same slot at the same time. How do you handle concurrent reservations without double-booking?
- How would you handle no-shows and implement a waitlist for popular restaurants?
- How do you onboard a new partner restaurant onto the platform? What does that flow look like technically and operationally?
- The system is read-heavy and some restaurants get way more traffic than others. How do you scale for that?
“I started with Users and Restaurants and felt good, but then stalled a bit when trying to model the difference between a Slot and a Reservation.”