Any system design. 7 building blocks.

Free, five emails, five days. Be prepared for system design interviews in the AI Era.

Five emails, one a day, then my newsletter. Free. Unsubscribe anytime.

Can you relate?

  • You are asked to design Instagram, and your first thought is MongoDB or Redis, before you know what the system has to do.
  • You have read how Uber or Netflix is built and could not say why it is arranged that way.
  • Your interview is coming up, and you are not sure what to study first.

If any of these sound like you, you're in the right place.

Hi, I'm Kay Ashaolu

I am a lecturer at UC Berkeley, and I have taught 600+ students there.

I made this course to share the pattern that changed how I think about software, and the 7-question cheat sheet I wish someone had given me years ago.

By day 5 you will be able to:

  • Break any system design into its building blocks
  • Choose storage by how it behaves, not by product name
  • Ask 7 questions that give you the skeleton of any design

What students say

“I find your teaching very valuable and needed for me to get back into the job market.”
Course Student

System design questions are open-ended

When someone says "design Instagram," it is easy to start with technology: MongoDB, Redis, Kubernetes. That is like asking what color to paint the walls before you have designed the house.

You cannot memorize every architecture an interviewer might name. You need a way to start that works on all of them.

But your approach doesn't need to be open-ended

Every system you use is built from the same 7 building blocks. Two do work: a Service that answers requests, and a Worker that handles slow jobs in the background. Five hold data: a relational database, a key-value store, a file store, a queue, and a vector database. Instagram, Netflix and Uber are the same blocks, arranged differently.

  • Service
  • Worker
  • Relational database
  • Key-value store
  • File store
  • Queue
  • Vector database

Ask what the system has to do before you name a technology, because the same blocks show up whatever the tech stack.

The free 5-day course teaches the blocks over five emails, one a day. Day 5 hands you a 7-question cheat sheet: one question for each block, such as "What work can happen later?" Answer them in order and you have the skeleton of any system design.

Get day 1 today

Enter your email below to get day 1 of the 5-day course.

Five emails, one a day, then my newsletter. Free. Unsubscribe anytime.

What lands in your inbox

  1. Day 1: See Instagram, Netflix and Uber as the same 7 building blocks, arranged differently
  2. Day 2: Split a design into what answers the user now and what runs in the background, with the Service and the Worker
  3. Day 3: Pick storage by how it behaves, not by product name: relational, key-value, or file store
  4. Day 4: Use a queue to say "done later," so users never wait on slow work and traffic spikes do not crash your system
  5. Day 5: Ask 7 questions, one per building block, and get the skeleton of any system design