01Owns
Routing and layouts
Designs the app directory: nested layouts, route groups, loading and error boundaries, parallel or intercepted routes where they genuinely help.
Hire · Frontend
Hire Next.js Developers
Senior Next.js developers who join your team to own routing, rendering and caching across an App Router codebase. Each has completed a paid assignment covering server and client boundaries, revalidation, server actions and pages that must rank and load fast.
Checked on App Router, not just pages
Senior and lead engineers only
Works in your repo and deploy flow
On your team
What a Next.js developer owns on your team.
02Owns
Rendering mode per route
Decides which routes are static, which revalidate on a timer or tag, and which must render per request, and documents why.
03Owns
Caching and revalidation
Understands what fetch, route segment config and revalidateTag or revalidatePath actually cache, and fixes pages that show stale or inconsistent data.
04Owns
Server actions and mutations
Writes server actions with validated input, authorisation checks and revalidation after writes, and keeps secrets off the client.
05Owns
Search-critical pages
Owns the metadata API, canonical URLs, sitemaps, structured data and Core Web Vitals for pages where organic traffic pays the bills.
Next.js expertise is mostly about the server
Many developers list Next.js because they have used it as a React starter. The App Router changed that. A true specialist thinks first about where code runs: on the server at build time, on the server per request, or in the browser. Ask a candidate to place three features from your product into those buckets and justify each.
Caching is the clearest signal. The defaults have shifted between major versions, and a developer who can explain what your current version caches, and how to invalidate it after a write, will save you from the most common production bug in Next.js apps: data that looks out of date.
Vetting
Skills we test before a Next.js developer joins.
01Tested
Server and client components
Keeps use client at the leaves, passes serialisable props across the boundary and avoids shipping server-only libraries to the browser.
02Tested
Data fetching on the server
Fetches in server components close to where data is used, deduplicates requests and streams slow parts with Suspense.
03Tested
Middleware and edge
Uses middleware for redirects, locale detection and auth gating, and knows the limits of the edge runtime compared with Node.
04Tested
Images, fonts and scripts
Applies next/image sizing, next/font self-hosting and next/script strategies to protect LCP and CLS.
05Tested
Deployment targets
Comfortable on Vercel and on self-hosted Node or Docker, including what ISR and image optimisation need when you host it yourself.
06Tested
Upgrades between majors
Reads release notes and codemods, plans a pages-to-app migration route by route, and tests caching behaviour after each upgrade.
Work sample
How the Next.js developer work sample runs.
- 01Step 1
Fix a stale product page
The candidate gets a route that keeps showing old prices after an admin update. They find the caching cause and fix it with the right revalidation, explaining the choice.
- 02Step 2
Build a route with a mutation
They add a listing route with streaming, a server action that writes through a stub data layer, input validation and revalidation, plus a test. Paid, and capped at a few hours.
- 03Step 3
Audit a landing page
Given a slow, client-heavy marketing page, they list what should move to the server, how to fix image and font loading, and what metadata is missing.
- 04Step 4
Explain rendering to marketing
On a brief call with your marketing lead, they describe whether a given page is static, dynamic or revalidated, and when an edit in the CMS will actually go live.
Levels
Next.js Developers: what changes at each level.
01Level 1
Senior
Ships routes, server actions and page-level SEO within an existing App Router structure and reviews colleagues’ pull requests.
02Level 2
Lead
Sets the caching policy, folder conventions, data-access layer and testing approach for the whole Next.js codebase.
03Level 3
Web platform architect
Leads the pages-to-app router migration, chooses hosting and CDN strategy, and owns performance and SEO budgets across many routes.
Picking between senior, lead and architect
With a settled App Router codebase and a clear caching approach, a senior engineer adds capacity. If your team is unsure why pages are dynamic or stale, hire a lead to set the rules. An architect earns their place during a router migration, a hosting change or when many teams publish into one Next.js platform.
Other options
When to hire someone other than a Next.js developer.
01Consider
A client-only single-page app
If there is no server rendering or SEO concern, a React developer focused on components and state is a better match.
Open register02Consider
A content site run by editors
If editors need a familiar CMS and themes more than custom rendering, consider WordPress developers.
Open register03Consider
Mostly API and database work
If the Next.js app is thin and the real load is in backend services, hire Node.js developers.
Open registerWhen SEO is the job description
If organic search drives revenue, the Next.js hire is effectively your technical SEO engineer. They should generate metadata per route, keep canonical URLs consistent across locales and parameters, and protect Core Web Vitals when marketing adds scripts. Test this in the hiring process with a real page from your site.
A sensible start for a new Next.js hire
Ask them to produce a short map of every route with its rendering mode and cache settings in the first fortnight. Most teams have never written this down, and it usually exposes routes that are dynamic by accident. Follow it with one measurable improvement, such as moving a heavy page to static generation.
FAQ
Questions to resolve before the build.
01Can they still maintain a Pages Router project?
Yes. Plenty of production sites still run on the pages directory. Every developer we put forward can work there, and a lead can plan an incremental move to the App Router since both routers can coexist in one project.
02Will a Next.js developer improve our search rankings?
They own the technical side: rendering crawlable HTML, metadata, canonical tags, sitemaps and page speed. Rankings also depend on content and links, which sit outside their role.
03Do we have to host on Vercel?
No. Our developers have run Next.js on self-managed Node servers and containers as well. They will explain what you need to configure for incremental static regeneration and image optimisation outside Vercel.
Works alongside
Roles a Next.js developer works best alongside.
01Pair with
React developers
For component-heavy interactive areas such as dashboards and editors that sit inside the Next.js shell.
Open register02Pair with
DevOps engineers
When you self-host Next.js and need container builds, CDN rules, cache storage and preview environments.
Open register03Pair with
UI/UX designers
For landing page layouts and templates that need to convert as well as rank.
Open registerProduct delivery
Need the whole product built instead?
Primary sources
References behind this page
Dated official documentation, standards, and research that support the factual claims on this page.
- 01Next.js documentation: Caching
How Next.js caches data, routes and fetch results, and how to revalidate them.
- 02web.dev: Web Vitals
Google’s explanation of LCP, INP and CLS.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Turn the brief into an accepted product scope.
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.