ScaleCrafts

Design a Q&A site

Let people ask questions, post answers, vote on the best ones and find answers through search, like Stack Overflow.

Functional requirements

  • Ask a question with tags
  • Answer, comment and vote
  • Search questions by text and tag

Non-functional requirements

  • Question pages load in under 200 ms
  • Relevant search results in under 500 ms
  • Each user’s vote counts once

Scale

  • 50M questions
  • 100M page views per day, mostly from search engines
  • Reads outnumber writes 1,000 to 1

How you’ll be scored

12 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 a Q&A site”, that starts with: Ask a question with tags; Answer, comment and vote; Search questions by text and tag. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (50M questions; 100M page views per day, mostly from search engines; Reads outnumber writes 1,000 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: Question pages load in under 200 ms; Relevant search results in under 500 ms; Each user’s vote counts once. 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 search, voting and caching 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.

Related problems

Loading your workspace…