System Design Interview Prep: Start From the Systems You've Already Built
Most system design guides start from zero, as if you've never shipped anything. If you've been building software for a while, you already know more than you think. Here's how to inventory the systems you've worked on, map them to the standard building blocks, skip what you've got covered and drill the gaps that actually matter.
By LearnHero7 min read
Ask an experienced engineer how they feel about the system design round and you'll often hear some version of "I'm not ready." Then ask them what they worked on last year, and they'll describe a service that handles real traffic, a cache they had to tune, a queue that backed up during an incident, or a migration that couldn't afford downtime.
That's system design. They've been doing it for years. They just haven't been practicing how to talk about it in 45 minutes on a whiteboard.
Most system design interview prep starts from zero: here's what a load balancer is, here's what a cache does, now design a URL shortener. If you're early in your career, that's fine. If you're a backend, frontend or infra engineer with real systems behind you, it wastes your best prep hours on things you already know. We think there's a better starting point: the systems you've already built.
Step 1: Inventory the systems you've worked on
Before you open a single prep guide, spend an hour writing down every system you've had a real hand in. Anything you've built, extended, debugged at 2 a.m. or migrated counts, not just what you designed from scratch.
For each one, jot down a few lines:
- What it did: one sentence, in plain words.
- Rough scale: requests, users, data size or team size. Ballpark is fine.
- What broke or got hard: the incident, the bottleneck, the tradeoff you argued about.
- What you decided, and why: the part that was yours.
Aim for four to six systems. Most engineers are surprised by how long the list gets once they stop filtering for "impressive." An internal tool that had to stay consistent across two databases is a great system design story. So is a frontend that had to stay usable on a flaky connection.
Step 2: Map them to the standard building blocks
Most interview prompts, whatever the product, lean on the same handful of building blocks. Our 4-week software engineering interview plan lists them, and the core set looks like this:
- Load balancing and horizontal scaling: spreading traffic across machines, and what happens when one disappears.
- Caching: where to cache, what to invalidate, and what goes wrong when the cache is stale or cold.
- Queues and async processing: taking work off the request path, retries, ordering and backpressure.
- Databases and consistency tradeoffs: SQL vs NoSQL, replication, partitioning, and what you give up for availability or speed.