Meeting Room Reservation Platform (Asked in Salesforce)

Posted
1 Dec 2025
526 reads

Summary

I was presented with a system design challenge to create a low-level platform for meeting room reservations, focusing on booking, availability, and management features.

How it went

During my interview, I was given a comprehensive system design problem: to architect a Meeting Room Reservation Platform. The goal was to enable employees to efficiently book meeting rooms, check their availability, and manage existing reservations within an organization. I had to consider core functionalities, various entities involved, and crucial operational aspects.

The discussion covered several key functional requirements, such as viewing available rooms, booking, cancellation, gracefully handling overlapping requests, and listing bookings for specific rooms or employees. We also touched upon the optional enhancement of supporting recurring meetings.

I then moved on to identifying the main entities: Employee, MeetingRoom, Booking, and TimeSlot, and defined the essential operations for the system. Important constraints like preventing double-booking, ensuring extensibility, and tackling concurrency issues (e.g., race conditions during simultaneous bookings) were also part of the design considerations. The interviewer expected me to define classes with proper responsibilities and address potential edge cases like invalid time ranges or unavailability of rooms.

Questions asked (1)

  1. 01

    Meeting Room Reservation Platform Design

    System Design · Hard

    Meeting Room Reservation Platform

    Design the low-level system for a Meeting Room Reservation Platform that allows employees in an organization to book rooms for meetings, check availability, and manage bookings. The system should support the following core features:

    Requirements:

    Functional Requirements:
    1. An employee can view all available meeting rooms for a given time interval.
    2. An employee can book a meeting room if it is free during the requested time.
    3. Ability to cancel an existing meeting.
    4. Handle overlapping meeting requests gracefully.
    5. Ability to list all meetings scheduled for a given room or employee.
    6. Support recurring meetings (optional enhancement).

    Entities Involved:

    • Employee
    • MeetingRoom
    • Booking
    • TimeSlot or Interval

    Operations:

    • bookRoom(employeeId, roomId, startTime, endTime)
    • getAvailableRooms(startTime, endTime)
    • cancelBooking(bookingId)
    • listBookingsForRoom(roomId)
    • listBookingsForEmployee(employeeId)

    Constraints to Consider:

    • No double-booking of the same room at overlapping times.
    • Extensibility for many rooms and bookings.
    • Concurrency: Handle race conditions where two users try to book the same room at the same time.

    Design Expectations:

    • Define classes with proper responsibilities.
    • Handle edge cases (invalid time range, no available rooms, overlapping bookings).

    Example Scenario:

    • Room A is booked from 10:00 AM to 11:00 AM.
    • User X tries to book Room A from 10:30 AM to 11:30 AM → Booking should fail due to overlap.
    • User Y books Room B from 10:30 AM to 11:30 AM → Booking successful.

    Entities/Domain Objects

    TimeSlot
    • startTime: LocalDateTime — start time of the interval
    • endTime: LocalDateTime — end time of the interval

    Key Methods:

    • overlaps(other: TimeSlot): boolean — checks if this time slot overlaps with another
    Employee
    • employeeId: String — unique identifier for the employee
    • name: String — employee's full name
    • email: String — employee's email address
    MeetingRoom
    • roomId: String — unique identifier for the room
    • name: String — name of the meeting room
    • capacity: int — maximum number of people the room can accommodate
    • location: String — physical location of the room (e.g., "Floor 1")
    BookingStatus (Enum)
    • ACTIVE — booking is active and confirmed
    • CANCELLED — booking has been cancelled
    • COMPLETED — booking time has passed
    Booking
    • bookingId: String — unique identifier for the booking (auto-generated)
    • employeeId: String — ID of the employee who made the booking
    • roomId: String — ID of the booked meeting room
    • timeSlot: TimeSlot — time interval for the booking
    • createdAt: LocalDateTime — timestamp when booking was created
    • status: BookingStatus — current status of the booking (ACTIVE, CANCELLED, COMPLETED)

    Key Methods:

    • overlaps(timeSlot: TimeSlot): boolean — checks if booking overlaps with given time slot (only for active bookings)
    • isActive(): boolean — returns true if booking status is ACTIVE
    • isCancelled(): boolean — returns true if booking status is CANCELLED

    Service/ Repository layer

    • BookingService
    • EmployeeService
    • MeetingRoomService

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Salesforce recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!