Mock Interviewer

Ask Coach

Ask Coach
Clarify requirements before you design — kept separate from your stage notes.

Tap a question to start, or type your own below.

Vaccine Booking System Design

Visual Problem Diagram

Vaccine Booking System Design architecture diagram

Scenario

Picture a vaccination clinic that opens its booking calendar at eight in the morning, with exactly one chair left at nine o'clock tomorrow. Two people, each on their own phone, both see "1 left" and both tap Confirm in the same second. If the website simply believes what each phone saw, it promises that one chair to both of them, and two families arrive at the clinic expecting the same appointment. A vaccine booking system is the website that finds nearby clinics, decides who is allowed to book, and gives every open time to exactly one person. The hard part is doing that while millions of people arrive at once and the rules about who may book can change overnight.

Stuck on where to start? Ask Coach

Clarify this problem here, or open Pathway Coach if you want a prep plan first.

Free Coach trial
How should I start prep?

This problem asks you to design a vaccine booking system, the website where a person looks up vaccination clinics near them, sees which times are still open, and books one of those times. Later they can book the next dose for a later day, move the appointment, or cancel it, and the site sends a reminder before the visit. The site also has to decide, on its own, whether a person is currently allowed to book, because vaccines are usually released to one group of people at a time, such as an age range or a region.

In the interview you need to explain four things. First, how a huge crowd waits its turn when times are released, instead of everyone refreshing at once. Second, how only one person wins the very last open time. Third, how the server decides who is allowed to book and can later say why someone was turned down. Fourth, how the second dose stays tied to the first visit. The wording of the reminder message matters least, so mention it briefly and move on.

Constraints

Functional

The system must show open times by clinic, let a person book, move, or cancel a slot, decide on the server whether that person is currently allowed to book, and send a reminder before the visit. A waitlist for cancelled slots is optional.

Non-functional

People are let in fairly when times open, so the fastest refresh is not the whole contest. A slot is never booked twice. The site stays up about 99.9% of the time. The pages stay usable on a slow phone and with assistive tools.

Scale

Millions of people and thousands of clinic sites. When times open, traffic flashes to about 100,000 requests a second. Most of the day is browsing times, so that open burst is the rate that dominates the design.

Stages ahead

1Requirement Analysis
2API Design
3High-Level Design
4HLD Extensions
5Trade-offs

Not ready to design yet?

Try the free Coach trial — ask how to prep, what to practice first, or how InterviewCrafted works. Sign in when you want to start this problem.

Try Coach free

Log in to start practicing

Preview the problem below. Sign in to start your timed session, save progress, and use the AI coach.

Want full access now? View Pro pricing