이 에피소드에 관해
System design interviews are partly arbitrary. Interviewing.io analyzed 1,000+ mock interviews. 80% of candidates score inconsistently across them. Same person, different day, different result. Even strong candidates (3-of-4 average) fail 22% of the time. Almost one in four.
But the same data says preparation matters more than you think. Because consistency is the edge.
The 6-phase framework that fits exactly into 45 minutes: Requirements (5min). Core Entities (2min). API Design (5min). Data Flow (~5min). High-Level Design (10-15min). Deep Dives (10min). Every major guide — HelloInterview, ByteByteGo, DesignGurus, Interviewing.io — converges on this. The framework isn't structure, it's a time budget. Time is the resource most candidates waste.
Four evaluation dimensions: problem navigation, solution design, technical excellence, communication.
Level calibration. Junior: "can they learn?" Mid: "can they build?" Senior: "can they own?" — drives conversation unprompted, brings up consistent hashing, gossip protocols, hot-key mitigation. Staff: "can they lead?" — at staff the system is almost secondary, the question is about the organization. Flagging uncertainties as a strength: "I don't know yet, I'd need to investigate."
Top 3 questions on every list: URL shortener (ID generation, 99% read traffic), chat (WebSockets vs long polling, message ordering across time zones), news feed (fan-out-on-write vs fan-out-on-read).
Five numbers to memorize: 1M/day = 12 QPS. Peak = 10X average. Memory is 100X faster than SSD. One server = 1,000+ QPS. Three nines = 8 hours downtime/year.
Seven failure modes: jumping to architecture, over-engineering, not finishing, ignoring trade-offs, monologuing, name-dropping without depth (the Kafka trap), ignoring operations.
And the 80/20 rule. DesignGurus: 80% of interviews use only 20% of core concepts — seven building blocks: servers, databases, caches, message queues, load balancers, blob storage, CDNs.
Plus three predictions for where this is heading (AI-assisted interviews coming within 2 years, top 3 questions won't change for years, 80/20 holds). And the line that ties it together: consistency beats brilliance in an interview. Every single time.
RELATED EPISODES
How Netflix, Uber, and YouTube Handle Scale — real production examples for the building blocks
Behavioral Interviews: What Big Tech Actually Evaluates — companion interview episode
Platform Engineering Goes AI-Native — what comes after microservices
How LLM Inference Actually Works — the infrastructure layer questions on AI-system design
CHAPTERS
00:00 Cold open — the 22% failure rate for strong candidates
03:20 Phase 1 — Requirements (5 min, the most important 5 minutes)
08:23 Phases 2-6 — Core Entities, API Design, Data Flow, High-Level Design, Deep Dives
12:30 Four evaluation dimensions — problem nav, solution design, technical excellence, communication
18:04 Level calibration — junior 'learn', mid 'build', senior 'own', staff 'lead'
20:57 Staff level — when the system is secondary and the organization is the question
22:50 Top 3 questions — URL shortener, chat, news feed
23:25 URL shortener — ID generation, 99% read traffic, the gap between real systems and interviews
24:30 Chat system — WebSockets vs long polling, message ordering across time zones
32:10 Back-of-envelope — 5 numbers every candidate must memorize
36:35 Seven failure modes — jumping to architecture, over-engineering, name-dropping
45:11 Three predictions + the 80/20 rule + consistency beats brilliance
SOURCES
HelloInterview — 28-problem catalog + 6-phase framework
ByteByteGo — system design framework comparison
DesignGurus — 80/20 rule + 7 mistakes
Interviewing.io — 1,000+ mock-interview analysis (22% failure / 80% inconsistency)
System Design Handbook + IGotAnOffer — cross-reference set
Designing Data-Intensive Applications — Martin Kleppmann
System Design Primer (GitHub) — free fundamentals reference
