Low-Level Design rounds show up mainly from the SDE-2 loop onward. Amazon interviewers expect you to drive requirement clarification yourself before touching a class diagram, then justify every design pattern choice rather than just naming one.
Design a system that lets employees book a meeting room for a time slot. It should prevent double-booking of overlapping reservations, let users search for available rooms by capacity and time, and support cancelling or modifying an existing booking.
Requirements to clarify first
- Who can book, and can bookings recur weekly or is every booking a one-off?
- What exactly counts as a conflict — do back-to-back bookings with zero gap overlap, or is a buffer required between meetings?
- Scale: is this a single office with a few hundred rooms, or a global company with rooms across time zones?
More LLD prompts Amazon 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.
3 more LLD prompts with full class designs in the full Placement-Ready PYQ Kit

