To hire a Next.js developer: shortlist people with Next.js sites you can open in production, ask whether they build with the App Router and how they decide what gets cached, agree where the app will be hosted and who pays for it before work starts, and ask how they keep a project current, because Next.js changes quickly.
Next.js is a framework built on React, made by Vercel, and widely used for web products. That popularity cuts both ways: plenty of people list it, and the gap between someone who followed a tutorial and someone who has run a Next.js app in production for a year is wide. The general hiring process is in how to hire a freelance developer without Upwork or Fiverr. This post covers what is specific to Next.js.
Check that Next.js is the right tool first
Next.js is a good fit when you want one codebase for public pages that should rank in search (marketing pages, a blog, product pages) and a logged-in app behind them. It is also a natural choice if your team already writes React.
It is more than you need for a five-page brochure site, which a site builder handles fine. And if the product is a mobile app with a small admin panel, the panel is the least important part of the hire. Say what you are building in the brief, and a good candidate will tell you if Next.js is overkill.
Open their sites like a user and like Google
Ask for links to Next.js projects they built that are live today. Then:
- Load it on your phone over mobile data. Does content appear quickly, or do you stare at a blank screen and a spinner?
- Run it through PageSpeed Insights, Google's free tool. You do not need to understand every number. Big red scores on a simple marketing page are worth asking about.
- Share a page link in a chat app. Does a proper preview with a title and image appear? Someone who set that up thought about how pages get shared and found.
- Visit a page that does not exist. A designed "not found" page, rather than a default error, is a small sign of finished work.
- Log in, if you can. The app half of a Next.js project is where most of the hard work lives.
App Router or Pages Router
Next.js has two ways of structuring an app. The newer App Router is what create-next-app sets up by default and labels as recommended (Next.js installation docs, checked in October 2026). The older Pages Router is still supported, and many existing apps use it.
What to ask:
- For a new project: "Will you use the App Router, and have you shipped something with it?" You want a yes, with an example.
- For an existing Pages Router app: "Would you migrate this, and if so when?" The right answer is often "not now". A migration is a cost with no visible change for your users, so it should be justified by something specific.
Hosting is a decision, not a detail
Where a Next.js app runs affects what it costs and which features work. The Next.js documentation lists four routes (checked in October 2026):
| Deployment | What the docs say |
|---|---|
| A Node.js server | Supports all features. Runs on any provider that supports Node.js. |
| A Docker container | Supports all features. Runs anywhere containers run. |
| Static export | Limited. Features that need a server do not work. |
| A platform adapter | Varies. Vercel and Bun are listed as verified adapters; other platforms offer their own integrations with varying compatibility. |
Ask: "Where will this run, who pays the bill, and what happens to the bill if traffic grows ten times?"
A good developer has an opinion and can explain the trade-off: managed platforms are convenient and can get expensive with traffic, a server you run yourself is cheaper and needs looking after. There is no universally right answer. There is a wrong process, which is finding out at launch.
Caching is where Next.js bugs live
Next.js can cache pages and data aggressively, which is a large part of why it is fast. It is also the most common source of confusing bugs: a price that does not update, a page that shows yesterday's content, a user who sees stale data after saving.
Ask: "How do you decide what gets cached, and for how long? Tell me about a caching bug you fixed."
You do not need to follow every detail of the answer. You want to hear that they think about it deliberately, that they can describe a real problem they ran into, and how they found it. Someone who has never had a caching bug in Next.js has probably not run one in production for long.
Keeping up with a fast-moving framework
Next.js releases major versions regularly, and the documentation showed version 16 at the time of writing. Each major version can change defaults and require code changes.
Ask: "Have you upgraded a project across a major version? What broke?" Upgrading is real work, and an app left several versions behind becomes harder and riskier to update. Budget a little time for it each year, the same way you would for a mobile app.
Where to look
On Shipfolks you can browse Next.js developers who are open to work, each with live projects you can open first. If you have not sized the project yet, the project cost estimator gives a first estimate in developer-weeks, and how to write a project brief a developer can quote from covers what to send.