Design Google Calendar
Create events, invite people, handle recurring meetings and send reminders, like Google Calendar.
Functional requirements
- Create single and recurring events
- Invite guests who can accept or decline
- Get reminders before events
Non-functional requirements
- Calendars load in under 300 ms
- Reminders arrive on time
- Edits sync to all devices quickly
Scale
- 500M users
- About 20 events per user per week
- Reminder spikes at the top of every hour
How you’ll be scored
11 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design Google Calendar”, that starts with: Create single and recurring events; Invite guests who can accept or decline; Get reminders before events. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (500M users; About 20 events per user per week; Reminder spikes at the top of every hour) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: Calendars load in under 300 ms; Reminders arrive on time; Edits sync to all devices quickly. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe scheduling, recurrence and notifications here. This is a medium problem, so interviewers expect you to weigh two reasonable options, such as consistency against latency, and to say why you picked one.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.