Grokking the Modern Frontend System Design Interview
Vote

0% completed

​

Course Introduction

Who This Course Is For

Basket, the App Behind the Concept Chapters

How the Lessons Work

The Chapters

Course Introduction
Course Introduction

A product list page asks its server for 30 products, and the server answers in 80 milliseconds. On a mid-range phone with a slow mobile connection, the shopper still waits about 3.7 seconds before the first product appears. Almost all of that wait happens on the shopper's side: in connections, downloads, running code and drawing the page.

That part of a product is designed with its own questions. Where is the page rendered? Which requests does each screen send, and what does the client keep? How does the page stay quick on a slow phone and usable with a keyboard and a screen reader? How does it stay correct in several languages, and safe from scripts it did not write?

This course teaches those questions and the design choices that answer them, with numbers you can check.

Who This Course Is For

The course is written for mid-level and senior engineers who build web applications, most of them with React. You should be comfortable with HTML, CSS, JavaScript and one component framework. You do not need to have designed a large frontend before.

By the end, you will be able to take a product question and state its requirements in numbers. You will be able to choose a rendering strategy for each page. You will be able to design the API that the screens need, the client state, and the real-time channel. You will also be able to defend the performance, accessibility and security choices with arithmetic or a measurement.

The course covers the part of a product that runs in the browser. The databases, queues and servers behind the API are treated as given. Building a component live in code is also outside its scope. The component chapter designs the API and the behavior of each component, with code only where it explains a point. React is the default framework in examples, and the ideas hold for other frameworks.

Basket, the App Behind the Concept Chapters

Basket is the web app of an online grocery store, and chapters 1 to 7 use it as their running example. It has 4,000 products shown 30 per page, a search box with suggestions, product pages, a cart, a checkout, live order tracking, and an account page.

Basket was chosen because one store needs nearly every topic in the course. Product pages must load fast and be readable by search engines. The search box must answer while the shopper types. The cart must stay correct across tabs and survive a lost connection. Checkout must take payment safely, and order tracking needs updates from the server while the page is open. Each lesson shows only the part of Basket that its topic needs.

Chapters 8 to 10 are case studies, and each one uses its own product: a news feed, a video site, a chat app, a document editor, and more.

How the Lessons Work

Concept lessons teach one subject each, with definitions, the mechanism, worked numbers and a comparison table. Each one ends its teaching with a short section called Using This in an Interview, which gives a sentence or two to say and two follow-up questions that often come next.

Case-study lessons design one component or one product from requirements to optimizations. They also give the follow-up questions a design usually meets, with an answer to each, and describe what a senior or staff-level answer adds to a mid-level one.

Every number is one of two things. Either it is a stated assumption with its arithmetic shown, or it is a measurement from the course's browser lab, quoted from the output of the run. An assumption reads like this: "Suppose the bundle is 400 KB. At 200 KB per second, that is 2 seconds." Lab measurements come from headless Chrome 150 on a desktop with an AMD Ryzen 7 5800X processor. The CPU is slowed four times to approximate a mid-range phone, and each lesson says when a number was measured.

Practice and assessment. Every lesson closes with Key Takeaways and four or five practice questions with folded answers. Try each question before you open its answer. Chapters 1 to 10 each end with a quiz, and the course ends with a final exam that covers every chapter.

The Chapters

#ChapterWhat you will be able to do
1What Frontend System Design CoversSeparate frontend design from backend design, name the parts of a web client, write requirements in numbers, estimate a page, and follow a five-step method
2Rendering and the BrowserExplain how a browser draws a page and choose between client, server, static and streaming rendering for each page
3Talking to the ServerShape the API for a screen, paginate, pick a real-time channel, handle failed requests, and set HTTP caching
4Data and StateDecide where each kind of state lives, cache server data, update the screen before the server confirms, and work offline
5PerformanceSet Core Web Vitals targets, ship less JavaScript, load images and fonts well, handle long lists, and measure real users
6Accessibility, Internationalization and SecurityBuild for keyboards and screen readers, support many languages, prevent script injection, handle login tokens, and monitor errors
7Frontend Architecture at ScaleDesign a shared component library, split a frontend between teams, release safely with flags, and let the server describe screens
8Designing UI ComponentsDesign an autocomplete, a data table, an image carousel, a date picker, an accessible modal and dropdown, and a rich text input with mentions
9Case Studies: Feeds, Media and CommerceDesign a news feed, a photo grid, a video site, a checkout, and a travel search with a map
10Case Studies: Real Time and CollaborationDesign a chat app, an AI chat interface, a shared document editor, a kanban board, a live dashboard, a calendar, and ride tracking
11The Interview PlaybookRun a 45 minute design, tell how answers differ by level, and grade answers against clear criteria

The chapters are meant to be read in order. Chapters 1 to 7 build the ideas, and chapter 8 applies them to single components. Chapters 9 and 10 apply them to whole products, and chapter 11 turns them into a plan for the interview itself.

The course begins with the 3.7 second wait at the top of this page and the question of where it goes. The first lesson, Frontend System Design vs Backend System Design, answers it and draws the line between the two kinds of design.

Reading Progress

0%


Vote for new content

On This Page

Who This Course Is For

Basket, the App Behind the Concept Chapters

How the Lessons Work

The Chapters