Design Pastebin
Let users paste text, get a short link and share it, like Pastebin or GitHub Gist.
Functional requirements
- Create a paste and get a unique link
- View a paste by its link
- Optional expiry time and unlisted pastes
Non-functional requirements
- Pastes load in under 100 ms at p99
- Stored pastes are never lost
- Links are hard to guess
Scale
- 5M new pastes per day
- Average paste is 10 KB, max 10 MB
- Reads outnumber writes 10 to 1
How you’ll be scored
9 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 Pastebin”, that starts with: Create a paste and get a unique link; View a paste by its link; Optional expiry time and unlisted pastes. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (5M new pastes per day; Average paste is 10 KB, max 10 MB; Reads outnumber writes 10 to 1) 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: Pastes load in under 100 ms at p99; Stored pastes are never lost; Links are hard to guess. 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 object storage, caching and read-heavy here. This is an easy problem, so interviewers expect the fundamentals done cleanly: a clear request path, the right kind of data store, and a reason for each component.
- 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.