Who should hire a Nuxt developer, and for what?
Hire one when a Vue product needs pages that search engines and slow phones handle well, or when a Nuxt 2 site has run out of road. Nuxt is the Vue framework that adds routing by file, server rendering, a server layer and deployment presets. The current line is Nuxt 4, and Nuxt 5 is in development. Our engineers work on that line and on the migrations that lead to it.
What do we vet in a Nuxt engineer?
Knowing Vue is the entry ticket. The Nuxt specific questions are where candidates separate.
- Rendering modes per route. Server rendering, static prerendering, client only and incremental caching can be mixed through route rules. We ask a candidate to assign a mode to a marketing page, a logged in dashboard and a product listing, and to defend each choice.
- Data fetching.
useFetchanduseAsyncDatawith stable keys, what is shared between calls, and how to avoid fetching twice on server and client. - Hydration mismatches. Code that reads
window, random values or dates during render is the classic cause. A good candidate finds it by reading the warning. - Nitro. Server routes, middleware, caching and the deploy target. Many Nuxt projects need a small API layer, and the developer should be comfortable writing it.
- Modules and config. Choosing a maintained module versus writing ten lines of code, and keeping
nuxt.configreadable. - Payload size. What lands in the serialised state, and why a large CMS response can slow every page.
How does Nuxt fit with a headless CMS?
This is the most common pairing we staff. Editors work in a headless CMS, and Nuxt renders the pages with the right cache rules. The trap is previews and invalidation: editors expect to see a draft at once and a publish to reach the live site quickly. We test candidates on how they would wire both. If you are still choosing between Vue and React frameworks for this, Next.js vs Nuxt sets out the differences.
What are the first tasks on a Nuxt project?
| Starting point | Typical first tasks |
|---|---|
| Nuxt 2 site | Decide between Nuxt Bridge and a direct rebuild, replace Vuex and old modules, move to the Vue 3 tooling |
| Nuxt 3 site | Move to the app/ directory layout, adjust data fetching defaults, run the migration codemods |
| Slow Nuxt site | Check route rules, payload size and cache headers before touching components |
| New build on a CMS | Set up content models, preview mode, image handling and the deploy target |
A Nuxt 2 migration is not a version bump. Modules written for Nuxt 2 often have no equivalent, and the build and deploy setup changes with Nitro. We scope this after looking at the code, not before.
How can you engage Nuxt developers?
- Dedicated developer. One engineer inside your team, reviewed through your pull request process.
- Team extension. A Nuxt developer joins alongside your Vue people. Read about IT staff augmentation for the mechanics.
- Scoped project. A migration or a CMS driven rebuild, owned by one team. Our Nuxt.js development services page covers delivery, and a dedicated team suits longer programmes.
You meet the developer before anything begins, and work starts after a short intro call where we agree the stack, the overlap with your time zone and the first milestone. For Vue only roles see hire Vue developers, and the full list of frontend roles is at hire frontend developers.
