Low-Level Design rounds show up from SDE-2 onward at Walmart, and cache-design prompts (LRU/LFU) reappear often enough to be worth practicing from scratch. Interviewers expect you to drive requirement clarification yourself and to be ready to defend any design pattern you reach for, not just name it.
Design a system for a restaurant that handles both table reservations and the order lifecycle from placement to serving. It should allocate tables to reservations, track an order from placed through preparing to served, and keep the booking and serving concerns cleanly separated so new order types can be added later without reworking the reservation flow.
- Clarify requirements yourself before naming any class — what counts as a valid reservation, how table allocation should behave under contention, and how many staff roles the system needs to model.
- Think through what happens when a reservation and a walk-in compete for the same table at the same time.
- Be ready to justify any design pattern you reach for (an allocation strategy, an order-lifecycle state machine) rather than just naming it, and to talk through how you'd implement it in a framework like Spring Boot.
More LLD prompts Walmart has asked recently
The class design, entity list, design-pattern reasoning and follow-up discussion for these — plus the full worked solution above — are part of the Placement-Ready PYQ Kit.
1 more LLD prompts with full class designs in the full Placement-Ready PYQ Kit