When you hire Vue.js developers, a resume that says "five years of Vue" can mean five years of Vue 2 with the Options API and nothing else. Vue 2 reached end of life on December 31st, 2023, so that experience comes from a version that no longer gets patches. It doesn't tell you whether the person can build with the Composition API, manage state with Pinia, or ship a server-rendered Nuxt app.
This guide sits in our series Hire developers by tech stack: rates, vetting and interview guides. For Vue, most bad hires are decided before the interview, by a job spec that doesn't pin versions or rendering mode.
Why "Vue developer" hides three different hires
Most Vue job posts are really one of three roles.
The first is the Vue 3 single-page-app engineer. They build a client-rendered app on Vue 3 with Vite, TypeScript and Pinia, usually against an API somebody else owns. The second is the Nuxt full-stack engineer, who also owns server rendering, data fetching on the server and the hydration bugs that come with both. Nuxt describes itself as a framework to build full-stack web applications and websites with Vue.js, and it expects real server-side judgment from whoever uses it. The third is the Vue plus Laravel engineer, who works across a PHP backend and a Vue frontend, often with Inertia in between.
The step most job posts skip is naming the rendering mode. Write "SPA", "SSR" or "SSG" in the ad. A candidate who has only built SPAs will read "SSR" and either self-select out or ask sharp questions, and both outcomes save you an interview.
Vue 2 vs Vue 3 vs Nuxt versions in 2026: what to write in the job spec
Pin versions in the job spec. It costs one line and filters out mismatched resumes.
Vue 2 is finished. Commercial extended support exists through HeroDevs' Never-Ending Support, listed on the same Vue 2 page, but that's a paid patch service for legacy apps, not a reason to start anything new on Vue 2. Vue 3's current stable release is 3.5.43 (see the Vue core release list). Version 3.6 is still a release candidate (3.6.0-rc.9 was tagged the day after 3.5.43), so don't write "Vue 3.6" into a spec and don't screen for it.
Nuxt moves faster than most people expect. The current stable release is Nuxt 4.5.2, and the Nuxt roadmap states that Nuxt 3 reached end of life on 31 July 2026 and no longer receives bug fixes or security patches. It also estimates Nuxt 5 for Q4 2026. If your ad says "Nuxt 3", you're advertising an unsupported framework. Write "Nuxt 4" and ask about upgrade experience.
The migration angle is where this pays off. A candidate who has only maintained a Vue 2 app knows the old reactivity quirks, mixins and Vuex. A candidate who has done a 2-to-3 migration has met the reactivity change, replaced mixins with composables and moved a store to Pinia. Ask which one they are, and ask for the story.
Vue vs React: what it means for hiring pool and ramp-up
Expect a smaller specialist pool than React's, which makes job-spec clarity matter more. A React posting can be vague and still get applicants. A vague Vue posting gets Vue 2 resumes, generalist frontend engineers who've touched Vue once, and Nuxt candidates when you wanted an SPA.
There's no primary source we can cite for how long a React developer takes to become productive in Vue, so we won't give a number. It's a fair option to consider a strong React engineer for a Vue codebase, and our hiring guide for the larger React pool covers how to screen them. The transferable part is component thinking and state discipline. The part that needs checking is Vue's reactivity model, which behaves differently enough to produce bugs a React developer wouldn't expect.
Rates and cost
We aren't printing a Vue rate here. A sourced Vue-specific rate doesn't exist in any primary dataset we could cite, and vendor-published Vue figures come without a methodology. A number you can't trace is worse than no number.
What moves the price is more useful. Nuxt and server-rendering experience commands more than pure SPA work. Seniority moves it, obviously, but so does whether the candidate can own architecture decisions like state management and rendering mode rather than implement tickets. The engagement model matters too: contract, staff augmentation and permanent hires price differently.
How to vet a Vue developer
Four exercises cover most of what matters. Run the first three for every Vue hire and the fourth only for Nuxt roles. Give the candidate the code and ask for a written review, not a live fix.
1. Reactivity code-review exercise
Give the candidate a component that destructures a reactive() object into local variables, sets up a watcher without cleaning it up, and registers a listener in onMounted with no matching onUnmounted. The bugs are quiet. The destructured values stop updating, and the leaked listener keeps running after the component is gone.
A candidate who's worked in Vue 3 production spots the lost reactivity quickly and suggests toRefs or using ref() for the values that need to stay reactive. They'll also connect the leak to component lifecycle. A candidate whose experience is mostly Vue 2 tends to review the template and miss the script.
2. Composables vs mixins exercise
Show two components that share logic through a mixin, such as a fetch-and-loading pattern. Ask the candidate to extract it as a composable and explain why mixins fell out of favour.
The good answer is specific: mixins merge into the component implicitly, so property names can collide and it's hard to see where a value comes from. A composable is a plain function with explicit inputs and return values. Vague answers like "composables are newer" mean the candidate has read about the change without feeling the pain that caused it.
3. State management judgment
Describe an app of a given size and ask how they'd manage its state. A small feature might need only props and events, or provide/inject. A larger app with shared state across routes points to Pinia, the official store for Vue today.
Listen for judgment about scale, not a reflex answer. Flag any candidate who defaults to Vuex for a new build. Knowing Vuex is fine for maintaining old code. Choosing it for new code isn't.
4. Nuxt boundary check
Only for Nuxt roles. Give the candidate a page that fetches data on the server, reads window during render and produces a hydration mismatch. Ask what's wrong and how they'd fix it.
A senior Nuxt engineer knows where the server and client boundary sits, when useFetch is right and when a client-only fetch is, and why browser-only APIs belong behind client checks. Then ask which Nuxt version they'd start a project on today. The answer should be Nuxt 4, and they should know Nuxt 3 is no longer supported. If the role touches server routes, the backend skills worth testing, such as API design, auth and observability, are covered in our guide to hiring backend developers.
Vue interview questions that show real seniority
1. When would you use ref() and when reactive()?
Tests whether they know reactive() loses reactivity when destructured and can't be reassigned wholesale. Red flag: "they're basically the same."
2. Why did Vue 3 move to Proxy-based reactivity?
Tests understanding of how Object.defineProperty in Vue 2 couldn't detect added or deleted properties, and what Proxies changed. Red flag: describing Vue 3 as "Vue 2 but faster."
3. A component re-renders far too often. How do you find out why?
Tests real debugging habits. Good answers reach for the browser devtools and the Vue devtools, look at what reactive data the template touches, and check for objects created inline. Red flag: wrapping things in computed at random.
4. Options API or Composition API for a team of mixed experience?
Tests judgment over dogma. A strong answer accepts that Composition API is the direction of the ecosystem, then explains how to bring a mixed team along, for instance with conventions for composables. Red flag: a religious answer either way.
5. How would you migrate a Vue 2 component to Vue 3?
Tests whether they've done it. Listen for mixins becoming composables, Vuex becoming Pinia, and dependencies that don't support Vue 3. Red flag: "just run the migration build."
6. When would you not use Vue?
Tests honesty about tradeoffs. A good answer names a case where the team's existing skills, an ecosystem need, or a very small interactive widget makes another tool a better fit. Red flag: "always."
7. How do you type props and emits in a Vue 3 component?
Tests TypeScript fluency in Vue specifically, and TypeScript is widely used with Vue 3. Our TypeScript hiring guide goes further on the language side. Red flag: any everywhere.
Staff augmentation vs full-time for a Vue hire
Frontend work is often a product build rather than a permanent seat: a new customer portal, a dashboard rewrite, a Vue 2 to Vue 3 migration. That favours staff augmentation or a fixed-scope engagement over a permanent hire from day one. You can confirm whether the role needs a dedicated Vue specialist or can fold into a wider frontend team once the build settles. Migrations in particular are a bounded project with a clear end.
Data residency is worth raising before signing. HighCircl delivers from seven European countries (Poland, Hungary, Slovakia, Serbia, Slovenia, Romania and Spain), with GDPR-native delivery from its EU member states. Serbia isn't an EU member, so GDPR-native delivery applies to the other six.
Hiring timeline
We have no primary source for how long a direct Vue hire takes, so we won't quote one. The sourcing time also matters less than the spec. A job description that pins the Vue version, names the rendering mode and says whether Nuxt is involved shortens every part of the process, because the wrong candidates drop out before the first call.
HighCircl delivers a vetted shortlist of 3-5 engineers within 72 hours, with four-stage, engineer-led vetting and roughly 1 in 10 applicants passing, from seven European countries. The margin is 20% and capped, with no minimum hours. HighCircl's stack coverage is React, Node.js, Python, iOS, Android, Flutter, Go and DevOps.
FAQ
How much do Vue developers cost?
We don't publish a Vue-specific figure because no primary dataset gives one. Price moves with seniority, Nuxt and server-rendering experience, and the engagement model. Ask any vendor quoting a Vue rate where the number comes from and which country it covers.
Vue 2 or Vue 3 for a new hire?
Vue 3, and specify it in the job post. Vue 2 stopped receiving updates on December 31st, 2023. Hire Vue 2 specialists only to maintain or migrate a legacy app, and test them on Composition API and Pinia if the migration is part of the job.
Do I need a Nuxt developer or a Vue developer?
It depends on rendering. If your app is a client-rendered SPA behind a separate API, a Vue 3 engineer is enough. If you need server-side rendering, static generation or a full-stack Vue app, hire for Nuxt experience and screen the server and client boundary. Write "Nuxt 4" in the spec, since Nuxt 3 is end of life.
Is Vue harder to hire than React?
Often, because Vue 2 resumes are mixed in with Vue 3 ones and the spec has to do more filtering. Clear job specs help more than a bigger budget. A strong React engineer can be a fair candidate for a Vue role if you screen the reactivity model.
Should I hire through staff augmentation or full-time?
Staff augmentation fits a bounded build or a Vue 2 to 3 migration. Full-time fits a product with a long roadmap and a frontend that needs a permanent owner. Check where a vendor's engineers sit if the app touches EU customer data.