Mock Interviewer

Ask Coach

Ask Coach
Clarify requirements before you design — kept separate from your stage notes.

Tap a question to start, or type your own below.

Search Engine System Design

Visual Problem Diagram

Search Engine System Design architecture diagram

Scenario

Crawlers discover 10B pages but users expect Google-quality results in < 200 ms—the index cannot fit on one machine and PageRank cannot run on every query. The interview splits crawl/index, ranking, and serving with honest freshness vs cost tradeoffs.

Design a web search engine that crawls pages, builds an index, ranks results, and serves queries at low latency. Scale forces distributed indexing and two-phase query processing—retrieval then ranking.

You should support crawling, indexing, ranking, query serving, and snippets. Be ready to explain inverted indexes, sharding, and offline vs online ranking.

Constraints

Functional

Crawl web, build inverted index, rank, serve queries, snippets, autocomplete optional

Non-functional

< 200 ms p95 query, index billions of pages, high crawl throughput, degrade rank under load

Scale

10B+ pages, 100K QPS search peak, petabyte index, continuous crawl

Stages ahead

1Requirement Analysis
2API Design
3High-Level Design
4HLD Extensions
5Trade-offs

Log in to start practicing

Preview the problem below. Sign in to start your timed session, save progress, and use the AI coach.