A guide to hiring a Next.js developer
Next.js is a framework for building websites and web apps. It is made by Vercel and built on React, and it adds the parts that a plain React project leaves to you: pages that are rendered on the server, routing from your folder layout, small server endpoints and tools for images, fonts and metadata. A Next.js developer uses all of that to ship sites that load quickly and can be found in search. If speed, search traffic or a smooth mix of server and browser code matter to your product, ask for Next.js experience by name.
What the job covers day to day
Building screens is only part of it. A Next.js developer decides where each page is produced, wires in data from an API or a CMS and makes sure a change by an editor shows up on the site without a full rebuild. Time also goes to reviews, bug fixes and package updates, plus the jobs a visitor never sees, such as caching rules, redirects, error pages and a safe way to release each change.
Rendering: static, server and incremental
This is the heart of Next.js. A page can be built once ahead of time, built fresh on every request, or built ahead and refreshed now and then. Static pages are very quick and cheap to host, but they can go out of date. Server pages are always current, but cost more to run. An experienced developer picks per page, based on how often the content changes and who sees it. Ask a candidate to explain the choice for a blog post, a product page and a user dashboard. The answers show whether they know the framework or only copy from it.
The App Router and server components
Newer Next.js projects use the App Router, which organizes pages as nested layouts and lets some components run only on the server. That keeps the code sent to the browser small. It also brings new rules about what can run where, and mistakes here lead to confusing errors or slow pages. A good developer knows where to put the line between server and browser code, and can also work in older projects that still use the Pages Router.
Next.js beside React
Next.js and React are close, but they are not the same job. React is the library for building the interface. Next.js adds the structure around it. Our React developers focus on components, state and the user interface inside an app. A Next.js developer works one level up, on routing, rendering, data and delivery. Plenty of people do both, and you can say so in your brief.
Data fetching and caching
Most pages show data from somewhere else, such as a database, a store or a CMS. Next.js lets you fetch it on the server and keep a copy so that the next visitor is served quickly. The hard part is knowing when the copy is out of date. A careful developer sets clear refresh rules, avoids loading the same data many times and can explain why a page showed old content. Cache bugs are some of the trickiest in this stack, so ask for a story about one.
API routes and server code
Next.js lets you write small server endpoints inside the same project. They suit forms, webhooks, sign-in callbacks and glue between services. For larger back-end work, such as queues, heavy jobs or a shared API for several apps, a separate service is often tidier. Our Node.js developers build those, and a good Next.js developer will tell you when a job has outgrown the front end project.
TypeScript and code quality
Most Next.js teams write TypeScript, because types catch mistakes in props, API data and route parameters before they reach a user. A developer who works well in this stack writes small components, names things clearly and adds tests for the logic that matters. If you want to build a wider typed team, see our TypeScript developers.
SEO and speed
Next.js is popular for sites that depend on search because the HTML a crawler receives already holds the content. That still does not happen on its own. Someone has to set titles and descriptions for each page, add canonical links, build a sitemap, keep redirects tidy and add structured data. Speed needs the same care: sized images, fewer scripts and fonts that do not shift the layout. A strong developer checks real-user data and not only a lab test, and will not promise a score.
Hosting and deploys
Many teams host Next.js on Vercel, the company that makes it, because it is simple to set up. You can also run it on your own servers with a Node.js process or in a Docker container, and some features behave a little differently there. Ask a candidate where they have deployed before, how they set environment values and how a release is rolled back if something breaks. Keep the hosting account in your company name.
When Next.js is a good fit
- You run a shop, a blog or a marketing site that needs to load fast and rank in search.
- You have a React app that is slow to show its first screen or poor at being found.
- You want one project that holds both the pages and the small server code behind them.
- You use a headless CMS and want editors to publish without a developer.
A tool that lives entirely behind a login may be fine with plain React. A developer who says that out loud is giving you honest advice.
Interview questions worth asking
- When would you pick a static page, and when server rendering?
- A product page shows an old price after an update. Where do you look first?
- How do you decide what stays in server code and what goes to the browser?
- How would you move one route of a React app to Next.js without breaking the rest?
- How do you check that a change made a page faster for real visitors?
Good answers come with a reason and a past project behind them. If someone can list every feature but cannot say why a page was slow, keep looking.
Try a small paid job
Hand every finalist the same piece of your real work: a new route that loads data and sets its own title, say, or a look at a page that feels slow. Pay them for it. Then compare the code, the questions each person raised and how plainly they explained the result.
Setting up for the long run
Settle the routine in week one: who reviews a pull request, how a release reaches the live site and who answers when the site goes down. One page that explains the folder layout, where data comes from and how to run the tests will save the next person many hours.
Mistakes to avoid
- Rendering every page on the server when most could be static.
- Caching data with no plan for when it should refresh.
- Sending large amounts of code to the browser that never needed to be there.
- Judging by the technology names on a resume, when no live site backs them up.
Related help: our full stack developers cover the server side in more depth, and our JavaScript developers suit work that is not tied to one framework.















