Grokking the Modern Frontend System Design Interview
Learn to design the frontend of a large web app: rendering, the API a screen needs, client state, real-time updates, performance, accessibility and security.

Course Overview
Frontend system design is the design of the part of a product that runs in the browser: how the page is delivered, how it gets its data, how it responds to the user, and how it stays fast and safe on hardware the team does not choose. On a mid-range phone, most of the wait before a page is usable happens in the browser, through connections, downloads, running code, and drawing, which is why faster servers rarely fix a slow page. The concept chapters follow one web application, Basket, the web app of an online grocery store, through rendering and the main thread, the API a screen needs, client state and caching, real-time updates, offline support and collaboration, performance and Core Web Vitals, accessibility, internationalization, browser security, monitoring, testing, and the architecture that lets many teams work on one frontend. Numbers are either stated assumptions with the arithmetic shown or measurements from a browser lab that runs Chrome on a slow mobile profile. The case-study chapters then apply all of it to UI components, such as an autocomplete, a data table, and a date picker, and to full products, such as a news feed, a chat app, an AI chat interface, a collaborative document editor, and live ride tracking. Each case study ends with the follow-up questions an interviewer is likely to ask and what senior and staff answers add. A closing playbook shows how to run the 45 minutes and how answers differ by level, and every chapter ends with an adaptive quiz.
What you'll learn in Grokking Modern Frontend System Design Interview
- Explain where a page spends its time on a slow phone, and why a faster server rarely fixes it.
- Find long tasks on the main thread and keep every tap and key press responsive.
- Pick polling, server-sent events, or WebSockets for live data, and handle retries and timeouts.
- Decide where state lives, normalize client data, and roll back optimistic updates that fail.
- Meet Core Web Vitals by shipping less JavaScript, virtualizing long lists, and loading assets in the right order.
- Store authentication tokens safely, monitor errors in production, and test a frontend at the right levels.
- Design common UI components and full products, and answer the follow-up questions they raise.
- Choose between client rendering, server rendering, static generation, streaming, and server components.
- Design the API a screen needs, including pagination with cursors and a backend for frontend.
- Use HTTP caching and a CDN so repeat visits and shared pages load quickly.
- Build offline-first features and real-time collaboration with OT or CRDTs.
- Design accessible, localized interfaces and defend them against XSS with a Content Security Policy.
- Scale a frontend across teams with design systems, micro frontends, feature flags, and server-driven UI.
- Run a 45-minute frontend design interview and give an answer that matches your level.
Course Content
Talking to the Server
REST GraphQL and Backend for Frontend
Designing the API for a Screen
Pagination with Offsets and Cursors
Exercise: Merge Pages Without Duplicates
Polling Server Sent Events and WebSockets
Retries Timeouts and Failed Requests
Exercise: Retry Delays with Backoff
HTTP Caching and CDNs
Exercise: Classify a Cached Response
Quiz: Talking to the Server
Accessibility, Internationalization and Security
Frontend Architecture at Scale
The Interview Playbook
What people say about our courses






About the Author

Arslan Ahmad
Industry Expertise & Leadership
Arslan Ahmad is the lead author of Grokking the Modern Frontend System Design Interview. As the founder of Design Gurus and a former FAANG hiring manager, he has worked at industry giants like Facebook (now Meta) and Microsoft.
He has conducted hundreds of system design interviews, giving him unique insight into what top tech companies look for in candidates.
The course also incorporates expertise from senior engineers at Google, Meta, Amazon, Microsoft, and Uber, ensuring you learn system design best practices from professionals who have built and scaled real-world systems.
500+
Interviews Conducted
10k+
Students Taught
Related Courses
$148
$75
$75
FAQs
What is a frontend system design interview?
It is an interview round where you design the part of a product that runs in the browser: how the page is delivered and rendered, how it gets and caches its data, how it stays fast on a slow phone, and how it stays accessible and secure. The interviewer usually treats the servers as given and asks for the API the screen needs.
How is it different from a backend system design interview?
A backend round asks about many users at once: servers, databases, caches, queues, and scaling. A frontend round asks about one user on one screen: rendering, the main thread, client state, the network between the browser and the API, Core Web Vitals, accessibility, and browser security. This course teaches the frontend round and treats the backend as a system that already works.
Who is this course for?
It is written for mid-level and senior engineers who build web applications and are preparing for frontend or full-stack design rounds. It also suits backend engineers who need to reason about the browser side of a product.
What should I know before starting?
You should be comfortable with HTML, CSS, and JavaScript and have built at least one web application. Experience with React helps, because some examples use it, but every pattern is explained first in general terms and then with a library as one example.
Do I need to know React or Next.js?
No. The course names a general pattern first, such as streaming or hydration, and then shows how one framework implements it. React and Next.js appear where they are the clearest example, so the ideas carry over to other frameworks.
Which UI components and products does the course design?
The component designs are an autocomplete, a data table, an image carousel, a date picker, an accessible modal and dropdown, and a rich text input with mentions. The product case studies are a news feed, a masonry photo grid, a video streaming site, an online store checkout, a travel search with a map, a chat app, an AI chat interface, a collaborative document editor, a kanban board, a live analytics dashboard, a calendar app, and live ride tracking.
How does the course show what a senior or staff answer looks like?
Every case study ends with the follow-up questions an interviewer is likely to ask and a section on what senior and staff answers add. The playbook chapter then compares answers by level and grades three answers to the same question, so you can see the difference in depth, trade-offs, and scope.
Are the performance numbers real?
Every number is either a stated assumption with the arithmetic shown, or a measurement from a browser lab that runs headless Chrome with a slow mobile network and a CPU slowed four times. Lessons say which kind each number is, so you can repeat the reasoning with your own figures.
Is there any practice, or is it only reading?
Every lesson ends with practice questions and folded answers, and every chapter ends with an adaptive quiz. Graded coding exercises in JavaScript or Java follow the lessons on pagination, retries, caching, collaborative editing, virtual lists, INP, debouncing, and masonry layout. A final exam covers the whole course.
How long does the course take?
The lessons take about 13 hours to read. The practice questions, coding exercises, quizzes, and final exam add about 12 more, so plan on about 25 hours. If your interview is close, read the first chapter, the rendering and performance chapters, and the playbook first, then work through the case studies closest to the role.