Post
How to Practise System Design: A 4-Week Plan
A practical 4-week plan for system design practice: what to do each week, how to run a solo practice session, how to judge your own answer, and when to add mock interviews.
By Codemia • November 13, 2026
6 min read
Most engineers prepare for system design interviews the way they would prepare for an exam: read a book, watch some videos, maybe skim a few worked answers. Then they sit down in the interview, get handed "design a ride-sharing app", and discover that knowing what a load balancer is does not tell you where to start.
System design is a performance skill. You need to produce a design out loud, in 45 minutes, while someone asks you why. The only way to get good at that is to do it many times. This article is a four week plan for doing exactly that, with about one to two hours a day.
Engineers with a system design round coming up in roughly a month, who already write backend code and have heard of caches, queues and databases. If those words are new, read a beginner guide such as System Design Explained on the Codemia blog first, then start here.
What practice actually means
Reading a worked answer to "design Twitter" feels productive. It is not practice, for the same reason that watching someone solve a LeetCode problem does not teach you to solve it. Practice has three parts:
- You produce the design yourself, from a blank page, before you look at any answer.
- You do it under interview conditions: a timer, a fixed structure, and ideally speaking out loud.
- You get feedback on what you missed, and then you redo the problem later.
Everything in the plan below is built around repeating that loop.
The solo practice session
Most of your practice will be on your own, so it pays to make each session look like a real interview. Use this structure, with a 45 minute timer:
| Time | Step | What to produce |
| 0 to 5 min | Requirements | 3 to 5 functional requirements, and the non-functional ones that matter (scale, latency, consistency, availability) |
| 5 to 10 min | Estimates | Requests per second, storage per year, read to write ratio. Rough numbers, written down |
| 10 to 15 min | API and data model | The main endpoints, the main tables or documents, and which field you will look things up by |
| 15 to 30 min | High level design | A diagram: clients, load balancer, services, databases, caches, queues. Walk one request through it |
| 30 to 45 min | Deep dives | Pick the two hardest parts and go deep: the hot path, the bottleneck, a failure case |
Write or draw as you go, and say your reasoning out loud even when you are alone. It feels strange at first, but the interview grades what you say, not what you think.
How to judge your own answer
When the timer ends, compare your design against an editorial solution or a grading rubric. The questions to ask:
- Did I clarify scope before designing? Interviewers mark down candidates who start drawing boxes in the first minute.
- Did my numbers change any decision? Estimates only matter if they lead somewhere. "40,000 writes per second, so one database will not hold, so we shard by user ID" is the kind of line that scores.
- Is there a single point of failure? Look at every box on your diagram and ask what happens when it dies.
- Did I name trade-offs? For every major choice (SQL or NoSQL, push or pull, strong or eventual consistency) say what you gave up.
- Did I cover the key points for this problem? Every problem has two or three things an interviewer is waiting for: seat holds for Ticketmaster, fan-out for a news feed, conflict resolution for Google Docs. Missing them costs more than any amount of polish.
Write down the points you missed in a running list. That list becomes your study plan for the next few days.
Week 1: learn the shape of an answer
Goal: get comfortable with the structure above, on problems that have one central idea.
- Days 1 and 2: if your fundamentals are rusty, review the building blocks (our beginner's guide to system design covers them in one read): load balancers, caching, database replication and sharding, message queues, CDNs. A free course such as System Design Fundamentals covers them in order.
- Days 3 to 7: one easy problem per day, under the timer. Good starting points: a URL shortener, Pastebin, a parking lot, a nested comments system and a video view counter.
By the end of the week you should be able to reach a reasonable high level design in 30 minutes without stalling on what to do next.
Week 2: breadth
Goal: see the common patterns once each. Pick one medium problem per day, each from a different area:
- A feed: Twitter teaches fan-out on write versus fan-out on read.
- Rate and contention: an API rate limiter or a flash sale.
- Real time: Facebook Messenger or live comments.
- Money: a digital wallet, where correctness matters more than scale.
- Background work: a task scheduler or a webhook notification service.
- Media: YouTube or Netflix.
- Search: typeahead suggestion.
Keep adding to your list of missed points. By the end of week 2 you will notice the same misses coming back, which tells you what to study.
Week 3: depth
Goal: get good at the last 15 minutes of the interview, where senior candidates are separated from the rest.
- Spend two days on the topics that keep showing up in your missed-points list. Read about them properly, not just a summary.
- Do four or five hard problems, such as Ticketmaster, Dropbox, Google Docs and the Uber backend. Spend less time on the high level design and more on two deep dives each.
- Redo two problems from week 1 or 2 that went badly, without looking at your first attempt.
Start speaking every session out loud this week if you have not already.
Week 4: rehearse with someone else
Goal: get used to being interrupted, questioned and pushed off your plan.
- At least two mock interviews. A peer mock is free and closest in feel to the real thing. An AI interviewer is available at any hour and grades you consistently. A paid coach gives the most experienced feedback. See our comparison of mock interview options for which fits when.
- Hard problems under a strict timer on the other days.
- Two days before the interview, stop adding new material. Review your missed-points list and redo one problem you are confident in, so you go in having just done well.
If you have less than four weeks
- Two weeks: compress weeks 1 and 2 into one week (an easy and a medium problem per day), then do week 4.
- One week: five medium or hard problems relevant to your target company, plus one or two mock interviews. Skip the fundamentals review unless you are truly rusty.
Common mistakes
- Reading solutions before trying. It is the most common way to feel prepared and not be.
- Practising only the famous problems. Interviewers rotate questions. Breadth across areas matters more than knowing Twitter perfectly.
- Skipping estimates. Many candidates skip them to save time, then cannot justify why they need a cache or a shard.
- Never practising out loud. Writing a good design and explaining one are different skills.
Start practising
Pick the first problem and set a timer today. The Codemia system design catalogue has 120+ problems with an editor, a whiteboard and AI grading against each problem's key points. For a ranked list to work through, see system design practice problems, from easy to hard.