0
Challenge · 48Interview Gauntlet

Rendering strategy & system design

Architectureused in ~88% of apps

Senior interviews don't ask you to write a component — they hand you a feature and ask 'how does this render, where does the data live, and what happens under load?' Pick SSG when the answer is per-user, or SSR when it's static, and you'll either melt your database or serve everyone the same stale page. This is the decision tree that separates an architect from a coder.

Core idea. Every route gets ONE question: does this content change per-user, on a schedule, or basically never? Per-user → dynamic (SSR) or a static shell with a dynamic hole (PPR). On a schedule → cached + revalidated (ISR / use cache + cacheLife). Never → fully static (SSG). The whole system design follows from answering that per-route and choosing where each piece of logic lives.
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