Design a web search engine
Crawl the web, build an index and return the most relevant pages for any query in a fraction of a second, like Google Search.
Functional requirements
- Search the web by keywords
- Rank results by relevance and quality
- Fresh results for breaking news
Non-functional requirements
- Results in under 300 ms
- An index covering billions of pages
- Always available
Scale
- 50B indexed pages
- 100K queries per second
- The index is rebuilt continuously
How you’ll be scored
10 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 web search engine”, that starts with: Search the web by keywords; Rank results by relevance and quality; Fresh results for breaking news. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (50B indexed pages; 100K queries per second; The index is rebuilt continuously) 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: Results in under 300 ms; An index covering billions of pages; Always available. 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 inverted index, ranking and crawling 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.