0
Challenge · 104Interview Prep
System Design (Frontend)
Interviewused in ~60% of apps
The system-design round is where mid/senior offers are won or lost. Nobody is grading your CSS — they are watching whether you can take a vague prompt like "design a news feed" and reason out a component tree, decide where every piece of state lives, choose a data-fetching strategy, and name the tradeoffs. It is the clearest senior-vs-junior signal in the whole loop.
Core idea. Frontend system design is a structured conversation: clarify requirements, sketch the component tree and data flow, classify each piece of state (server cache vs client/UI vs URL) and place it at the right level, pick a data-fetching + caching approach, then defend the tradeoffs (performance, real-time, accessibility).
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
FEED COMPONENT TREE — where does each piece of state live?
<FeedApp>
<AppShell> — theme, current user
<FeedTabs> / <Feed> — active tab, posts
<PostCard> — likes, menu
<Composer> — draft
The list of feed posts
A post's like count + liked flag
Draft text in the compose box
Which post's '...' menu is open
Active feed tab (For You / Following)
Dark-mode + current-user identity
HOW DOES THE FEED LOAD ITS DATA?
Design the feed. For each piece of state, choose where it lives — then pick how the feed loads its data.
0/6 placed well
↑ play a little first, then dig in