roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Answer Next.js interview questions from a real understanding of how it renders, routes and caches. Covers the App Router APIs, server components and actions, caching and data flow, and shipping to production.
399 of 399 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 399 new. 0 cut, outside your plan.
Next.js questions arrive inside frontend and full-stack loops rather than as a separate round: in the framework conversation, in a take-home built on it, and in frontend system design when the question is how a product page should render. Nearly every question is about place and time: where a piece of code runs, and when its output was produced. Why does reading cookies() in the root layout turn every page beneath it dynamic? Why can a Server Component not hand an onClick handler to a Client Component? Why does a list still show the old row after a Server Action saved the new one, and would revalidatePath or revalidateTag fix it? Why does a date formatted on the server raise a hydration error in the browser?
Lower in the level range, interviewers check that conventions are understood, not recited: that 'use client' marks a boundary in the module graph, and that the modules it pulls in still render to HTML on the server first. Toward senior level, interviewers bring an incident instead. An API key prefixed NEXT_PUBLIC_ was inlined into the client bundle. An admin page was guarded only by middleware reading a cookie, while the Server Action behind its form, reachable as a plain POST request, checked nothing. Caching defaults have shifted between major versions, so a strong answer also says which version it describes.
Before any Next.js API, the first module sets out rendering modes in general: prerendering at build time, rendering per request, regeneration in the background, streaming and what hydration costs, then the mismatches that follow when server HTML and the first client render disagree. Next.js is one set of answers to those choices, so the choices come first. The Next.js module then maps them onto files and directives, and its own guide sets the order inside it: the route tree and the server/client split before rendering and caching, with Server Actions, middleware and deployment built on top.
With the API in hand, the plan steps back out into two framework-neutral modules that serve as the diagnosis layer. Routing & Data Flow covers what a nested layout keeps alive between navigations and, on the data side, where each cache sits and how one write must invalidate every tier holding the old value, which is the vocabulary for naming the stale copy. Server & Edge is about execution placement: what gets serialized into the page payload, which environment values reach the client, and what moving code to the edge gives up.
The plan then turns to what the browser receives. Styling runs from CSS Modules through Tailwind to CSS-in-JS, where libraries that inject styles at render time run into Server Components. Page Speed measures the outcome: Core Web Vitals tie a rendering choice to LCP and hydration work to INP, and the script loading strategy decides how much of that a third-party tag can undo. The close is deployment, with failures that only exist in production: what a static export gives up, a regeneration cache several instances have to share, and version skew when a tab loaded from the previous release talks to the new one.
Coming from React without Next.js, read the first module as the prerequisite for the second; switching study order to by topics keeps them in that sequence. If your Next.js dates from the Pages Router, do not skip that first module either: `getStaticProps` and `getServerSideProps` chose between modes it describes, and the App Router reaches the same modes by other means, such as a fetch option, a segment setting or a call to `cookies()`. With only days left, give the Next.js module the first hours, then narrow importance to must know before you move past it, and the framework-neutral modules shrink to the core an interviewer expects you to hold. Senior candidates get more from Server & Edge and the deployment module, where the incident questions come from; deploy one small app twice, with a form that writes through a Server Action, and watch what an open tab does when the server changes under it. The plan assumes React rather than teaching it: hooks, state, effects and how a component re-renders in the browser are not in it, and a Next.js interview leans on all of them. The [React roadmap](/roadmaps/react) covers that ground; if the loop also tests the language, layout and the DOM beneath any framework, the [Frontend Developer roadmap](/roadmaps/frontend) is the wider plan.
Coming from React without Next.js, read the first module as the prerequisite for the second; switching study order to by topics keeps them in that sequence. If your Next.js dates from the Pages Router, do not skip that first module either: getStaticProps and getServerSideProps chose between modes it describes, and the App Router reaches the same modes by other means, such as a fetch option, a segment setting or a call to cookies(). With only days left, give the Next.js module the first hours, then narrow importance to must know before you move past it, and the framework-neutral modules shrink to the core an interviewer expects you to hold. Senior candidates get more from Server & Edge and the deployment module, where the incident questions come from; deploy one small app twice, with a form that writes through a Server Action, and watch what an open tab does when the server changes under it.
The plan assumes React rather than teaching it: hooks, state, effects and how a component re-renders in the browser are not in it, and a Next.js interview leans on all of them. The React roadmap covers that ground; if the loop also tests the language, layout and the DOM beneath any framework, the Frontend Developer roadmap is the wider plan.