Skip to content
Tutorials Center
My learning

Topics

Lesson 65 of 65 ยท Practice and Interviews

System Design Practice Questions

Twelve system design practice prompts with requirement hints, key challenges and checklists, plus a Python self-scoring tool to review your answers like an interviewer.

Reading solutions teaches you little compared with designing something yourself. This lesson gives you twelve practice prompts. For each there are clarifying questions to ask, the hardest parts to focus on, and a pointer to related lessons. Set a 45-minute timer, follow the interview framework, and talk aloud or write your answer. Then compare against the hints and score yourself.

How to practice

  1. Pick a prompt. Do not read the hints yet.
  2. Run the six steps with a timer: requirements, estimates, API and data, high-level design, deep dive, trade-offs.
  3. Draw the diagram on paper or whiteboard (or a quick mermaid sketch).
  4. Read the hints and mark what you missed.
  5. A week later, redo the same prompt from scratch.

Twelve prompts

1. Design a paste service (like Pastebin)

Users paste text and get a short link; links may expire; content is read often.

  • Ask: maximum size, expiry, private pastes, analytics.
  • Focus: ID generation, object storage for the content versus metadata, caching, cleanup of expired data.
  • Related: Design a URL Shortener.

2. Design an API rate limiter

Limit clients per key and per IP across a fleet of gateways.

  • Focus: algorithm choice, shared counters, race conditions, behaviour when the store fails, response headers.
  • Related: Design a Rate Limiter.

3. Design a chat application with group chats

  • Focus: connection handling, message ordering and IDs, offline delivery, group fan-out, presence, storage.
  • Related: Design a Chat System.

4. Design a social media timeline

  • Focus: fan-out on write versus read, celebrities, ranking, cache design, pagination.
  • Related: Design a News Feed.

5. Design a distributed key-value store

  • Focus: partitioning, replication, quorums, conflict resolution, failure detection, hinted handoff.
  • Related: Design a Key-Value Store.

6. Design a notification service

  • Focus: multiple channels, queues and priorities, preferences, idempotency, retries and dead letters, bursts.
  • Related: Design a Notification System.

7. Design a web crawler for 1 billion pages a month

  • Focus: URL frontier, politeness, duplicate detection, spider traps, re-crawl policy.
  • Related: Design a Web Crawler.

8. Design a video platform

9. Design an online ticket booking system (movies or concerts)

Seats are limited; thousands of users may fight for the same seat.

  • Ask: seat selection or general admission, hold time, payment, refunds.
  • Focus: preventing double booking (locks or atomic reservation with a hold that expires), flash-sale traffic spikes with a waiting room, payments and idempotency, consistency of seat maps.
  • Related: Design a Payment System.

10. Design a distributed job scheduler

Run jobs at specific times or intervals across many workers.

  • Focus: storing schedules, picking due jobs without duplicates, leader election or partitioned scanners, retries and idempotency, long-running jobs and heartbeats, monitoring missed runs.

11. Design a collaborative document editor

Several people edit the same document at once.

  • Focus: conflict resolution (operational transformation or CRDTs), connections through WebSockets, cursor presence, snapshots plus operation log, offline edits.

12. Design a food delivery or ride-hailing platform

A scoring sheet

Interviewers use a rubric. Use the same one on yourself. Give each area 0 to 4 points and note where you were weakest.

Python Score your own answer like an interviewer

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Replace the numbers with your own scores. Two weak areas at a time is plenty to work on.

A reusable checklist

Run through these once your design is on the board. Each question catches a typical gap.

Python Design review checklist generator

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Practice habits that work

  • Time-box: a real interview is 45 minutes; practice at that speed.
  • Talk aloud or record yourself. Silent practice hides gaps in explanation.
  • Practice with a partner who plays the interviewer and pushes with "what if this fails?".
  • Redo old problems after a week; the second attempt is where learning sticks.
  • Study real architectures: engineering blogs describe how large systems actually evolved, including their mistakes.
  • Learn the building blocks (caches, queues, sharding, replication, load balancers) well enough to explain them to a beginner; every case study reuses them.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the best way to use a practice prompt?

    Active attempts with feedback build skill; reading solutions builds only familiarity.
  2. 2. For a ticket booking system, what is the key correctness problem?

    Use atomic reservation with expiring holds, and handle payment idempotently.
  3. 3. Which deep-dive topic fits a collaborative editor?

    Concurrent edits must merge deterministically without losing changes.
  4. 4. After finishing a practice answer, what should you do with the rubric?

    Focused practice on weak spots gives the fastest improvement.

Summary

  • Practice with a timer, the six-step framework and a written or drawn answer.
  • Twelve prompts cover storage, messaging, feeds, media, crawling, scheduling, booking and collaboration.
  • Score yourself with a rubric, then practice your two weakest areas.
  • Revisit prompts after a week, and learn the shared building blocks deeply.

Next: back to the System Design course