Next.js ⚡ Recently updatedUpdated on Jun 30, 2026 — this content may still be evolving.
Next.js: Mock Interview (45 Minutes)
Section 1: Warm-up (5 min)
- “Tell me about your Next.js project.”
- “App Router or Pages Router — why?”
- “How did you deploy it?”
Section 2: Rendering (12 min)
- “Explain SSR, SSG, CSR, and ISR.”
- Follow-up: “When would you pick each?”
- “What’s hydration?”
- “Blog vs dashboard — different rendering?”
- Scenario: “E-commerce with 5000 products, prices change hourly.”
- Expected: ISR with revalidate
Section 3: App Router (10 min)
- “Server Components vs Client Components?”
- “How fetch data in App Router?”
- “What is
layout.tsx?” - “Dynamic route
[id]— how access the id?”
Section 4: Live Discussion / Pseudo-code (10 min)
Pick ONE:
Option A: Route design
“Design folder structure for: home, blog list, blog post, dashboard (auth), API for comments.”
Option B: Rendering choice
“Given these 4 pages [marketing, blog, profile, admin], assign SSR/SSG/ISR/CSR and justify.”
Option C: Middleware
“Write pseudocode for middleware that redirects unauthenticated users from /dashboard to /login.”
Section 5: Performance & SEO (5 min)
- “Why
next/image?” - “How set page title and meta description?”
- “What is
loading.tsx?”
Section 6: Project (3 min)
- “For each route in your app — what rendering strategy and why?”
- “What would you change if you rebuilt it?”
Rubric
| Area | 1 | 3 | 5 |
|---|---|---|---|
| Rendering | Defines only | Picks correctly | Tradeoffs: SEO, TTFB, cost |
| App Router | Confuses with Pages | Server vs Client | Layouts, caching, RSC patterns |
| Routing | Unclear | File-based basics | Dynamic, groups, middleware |
| Practical | No project | Deployed once | Per-route rendering decisions |
Debrief
Re-read rendering-patterns.md decision flowchart. Re-answer Section 2 without notes.
Homework: Label every route in your project with its rendering strategy in a comment or doc.