Should I hire a Next.js developer or a general React developer?

If your product needs SEO, fast initial loads, or server-side rendering, hire a Next.js developer with App Router expertise. If you are building a pure SPA or design system where routing and server rendering are less critical, a strong React developer may suffice.

How do I verify a Next.js developer understands App Router?

Ask them to explain the difference between Server Components and Client Components, how data fetching works in each, and when to use caching versus dynamic rendering. Review their portfolio for App Router projects deployed to production.

What caching strategies should a senior Next.js developer know?

A senior Next.js developer should understand the fetch cache, router cache, and segment cache in App Router. They should know how to revalidate data on-demand, when to opt out of caching, and how caching impacts performance and data freshness.

What is the biggest red flag when interviewing Next.js developers?

The biggest red flag is having no App Router experience or treating Next.js as just React with routing while ignoring Server Components, caching, and Core Web Vitals. Other concerns include no production deployment experience and relying entirely on client-side rendering.

How to Hire a Next.js Developer in 2026 (Checklist for CTOs) | Yosuke Sakurai

Hiring a Next.js developer in 2026 is different from hiring a general React engineer. The App Router is now the standard, React Server Components have changed how data flows from server to client, and caching semantics can make or break performance at scale. Many candidates know React but have not shipped a production Next.js app with App Router, edge deployment, and real traffic. This checklist is designed for CTOs and engineering managers who need to identify senior Next.js engineers without wasting interview cycles.

Before You Write the Job Post

Define the scope before you draft the title. Three questions determine whether you need a Next.js specialist, a full-stack generalist, or a fractional lead:

Are you building a content-heavy marketing site that needs SEO and fast time-to-first-byte, or a dynamic SaaS dashboard?
Is the project greenfield with App Router, or a migration from Pages Router or a CRA-based SPA?
What does “done” look like in ninety days? A deployed marketing site, a design system with Server Components, or a full-stack SaaS MVP?

The answers determine whether you need a senior Next.js engineer, a fractional web lead, or a full-stack developer. For a breakdown of engagement models, see our web development services.

The Technical Checklist

Use this during resume screening and technical interviews to identify candidates who have shipped production Next.js apps, not just built side projects.

App Router and Server Components

Can they explain the trade-offs between Server Components and Client Components in a production App Router codebase?
Do they understand the new routing conventions, parallel routes, intercepting routes, and route groups?
Have they implemented loading states, error boundaries, and not-found pages using the App Router file conventions?

Data Fetching and Caching

Can they articulate Next.js caching semantics — fetch cache, router cache, and segment cache — and when to opt out?
Do they understand how to fetch data in Server Components versus Client Components, and the implications for waterfalls?
Have they used React Server Actions for mutations, and do they understand progressive enhancement?

Performance and Core Web Vitals

Can they explain how Next.js optimizes images, fonts, and scripts out of the box, and when to configure custom loaders?
Do they understand streaming SSR, partial prerendering (PPR), and how they improve LCP and TTFB?
Have they diagnosed and fixed performance issues using Lighthouse, Web Vitals, and the Next.js bundle analyzer?

Full-Stack Capabilities

Have they built API routes, route handlers, and middleware for authentication, rate limiting, or A/B testing?
Can they explain when to use edge functions versus Node.js runtime, and the constraints of each?
Do they understand how to integrate headless CMS platforms, databases, and third-party APIs securely?

Deployment and Infrastructure

Have they deployed production Next.js apps to Vercel, and do they understand preview deployments and rollback strategies?
Can they configure environment variables, build settings, and rewrites/redirects for multi-domain setups?
Do they understand ISR (Incremental Static Regeneration), on-demand revalidation, and static generation at build time?

Testing and Quality

Do they write unit tests for utilities and server logic, and component tests for Client Components?
Have they set up end-to-end tests with Playwright that verify routing, data fetching, and edge cases?
Can they explain how to test Server Components and server actions in a CI pipeline?

Red Flags to Watch For

These signals suggest a candidate may struggle in a production environment:

They have only used Next.js Pages Router and cannot articulate how App Router changes data fetching and caching.
They treat Next.js as “React with routing” and ignore Server Components, streaming, or caching semantics.
They have never deployed to production and do not understand how to read a Core Web Vitals report.
They rely on client-side data fetching for everything and do not understand the benefits of server rendering.

The Interview Structure That Works

A strong Next.js interview has three parts: architecture discussion, live coding with real-world constraints, and a retrospective on a past project. The architecture discussion reveals how they think about rendering strategies, data flow, and caching. The live coding session should involve a feature that requires server-side data fetching, client interactivity, and error handling — not a LeetCode algorithm. The retrospective reveals whether they own outcomes or just write code. Ask specifically about how they improved LCP on their last project, how they handled a caching bug, and how they debugged a production issue that only appeared at scale.

When to Consider a Fractional Lead Instead

If you need architecture decisions made in the next two weeks but your hiring pipeline is three months long, a fractional web lead can bridge the gap. You get senior-level code review, App Router setup, and deployment configuration without the full-time commitment. Many teams bring in a fractional lead for the first ninety days to establish patterns, then backfill with permanent hires who inherit a clean codebase and documented conventions. Learn more about hiring a Next.js developer on a fractional or project basis.

Related Guides

If you are hiring for a specific web technology, these focused checklists go deeper:

How to Hire a Next.js Developer — App Router, Server Components, and full-stack delivery
How to Hire a React Developer — Component architecture, hooks, and state management
How to Hire a TypeScript Developer — Type safety from frontend to backend
How to Hire a Web Developer — Full-stack web delivery and performance

Final Checklist: Quick Reference

Define project scope (marketing site, dashboard, or SaaS) before writing the job post.
Screen for production Next.js experience with App Router and Server Components.
Verify they understand caching semantics and have optimized real sites for performance.
Test their full-stack capabilities with API routes, middleware, and edge functions.
Ask about deployment experience and infrastructure knowledge.
Require evidence of unit tests, E2E tests, and CI/CD automation.
Watch for red flags: no App Router experience, ignoring Server Components, or no production deployment.
Consider a fractional web lead if you need immediate architecture decisions.