What do you get when you hire Nuxt.js developers from Alpina Tech?
You get a Nuxt engineer who has shipped server rendered Vue apps and who joins your repository, your reviews and your release schedule. Most requests we take fall into three groups: a new build on Nuxt 4, a Nuxt 2 app that has to move to the current line, or a slow Nuxt site that needs its rendering and caching sorted out. You meet the developer before work begins and decide whether they join. You can take one engineer, a small team or a scoped project.
Nuxt is the Vue framework that adds file based routing, server rendering, a server layer called Nitro and deploy presets for most hosts. The current release line is Nuxt 4, with Nuxt 5 in development. Our engineers work on that line and on the migrations that lead to it.
Which Nuxt 4 and Vue 3 skills does the job need?
Vue 3 is the base, and Nuxt changes how you use it. A composable that works fine in a Vue single page app can leak state between users once it runs on the server. These are the Nuxt specific habits we look for:
- Composition API on the server. Shared state goes through
useStateor a store, never a module levelref, because a module level variable on the server is shared by every request. - Pinia with SSR. The store is filled on the server, serialised into the payload and picked up on the client. Developers should know what that costs in page weight and how to keep stores small.
- Auto imports and the
app/directory. Nuxt 4 moved application code intoapp/. A good engineer knows what Nuxt imports for them and keeps explicit imports where they make code easier to read. - TypeScript across the stack. Typed server routes, typed
useFetchresponses and anuxt.configthat type checks. - Layers and modules. Nuxt layers let several sites share components and config. We use them for multi brand setups and expect candidates to know when a layer is cleaner than a copied folder.
- Testing.
@nuxt/test-utilswith Vitest, so composables and server routes run in a real Nuxt environment instead of a mocked one.
For pure Vue roles with no server rendering, the Vue developers page is the better fit.
SSR, SSG or hybrid rendering: how should a Nuxt site render?
Picking the rendering mode for each route is most of the performance and SEO work on a Nuxt project. Route rules in nuxt.config let one app mix modes, so the choice is per page:
| Page type | Usual mode | Why |
|---|---|---|
| Marketing and landing pages | Prerendered (SSG) | Built once, served from the CDN, fastest first load |
| Blog or CMS content | ISR or SWR caching | Fresh after a publish without rebuilding the site |
| Product listings and search | Server rendered (SSR) | Content changes often and must be indexable |
| Account area and dashboards | Client only | No SEO value, avoids server cost |
The common mistake is server rendering everything and then adding caches until it holds up. Our developers start from the route list and assign a mode to each group first.
What do we vet in a Nuxt engineer?
Knowing Vue gets a candidate through the door. The Nuxt specific questions are where people separate.
- Rendering modes per route. 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 over ten lines of your own code, or the other way round, and keeping
nuxt.configreadable. - Payload size. What lands in the serialised state, and why a large CMS response can slow every page.
How do Nuxt developers handle SEO?
Search visibility is a common reason teams pick Nuxt over a plain Vue app, so we expect the developer to own the technical side of it. That means useSeoMeta and useHead for titles, descriptions and Open Graph tags per route, canonical URLs that survive query strings, a sitemap generated from the real route list, and structured data where the page type calls for it. Core Web Vitals come next: @nuxt/image for responsive images, fonts loaded without layout shift, and third party scripts kept off the critical path. A developer who has only built dashboards will miss most of this, which is why we ask about it on the interview.
How does Nuxt fit with a headless CMS?
This is the pairing we staff most. 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.
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.
How does hiring a Nuxt developer work?
- Intro call. You tell us the Nuxt version you run, the hosting target, the CMS or API behind it and the outcome you want.
- Matching. We put forward engineers whose past Nuxt work matches that setup, such as a Nuxt 2 migration or a Nitro API.
- Interview. You talk to the developer directly and ask the questions that matter to your team.
- Start. We agree the time zone overlap and the first milestone, and the developer starts in your repository.
Pricing follows the developer’s level and the share of architecture in the role. You get a quote once we know the project. The full list of frontend roles is at hire frontend developers.