Design Gmail
Send, receive, store and search email for hundreds of millions of users, with spam filtering, like Gmail.
Functional requirements
- Send and receive email with attachments
- Organize mail with labels and threads
- Full-text search across all mail
Non-functional requirements
- Mail is never lost
- Inbox loads in under 500 ms
- Spam rarely reaches the inbox
Scale
- 1.5B users
- Tens of billions of incoming emails per day
- About 5 GB per mailbox
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 Gmail”, that starts with: Send and receive email with attachments; Organize mail with labels and threads; Full-text search across all mail. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (1.5B users; Tens of billions of incoming emails per day; About 5 GB per mailbox) 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: Mail is never lost; Inbox loads in under 500 ms; Spam rarely reaches the inbox. 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 storage, search and spam here. This is a hard problem, so interviewers expect depth: what breaks first at this scale, how each failure is contained, and which trade-offs you accepted on purpose.
- 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.