Hire Vue developers
Our senior Vue developers build production apps in Vue 3 and Nuxt. Each one is tested on reactivity, state management and the Composition API, because that's where AI-generated code breaks first and where the gap between a good engineer and a poor one shows.
01
Composition API code is now easy to generate badly
AI tools produce plausible-looking composables that mishandle reactivity or leak watchers. Engineers need to read generated code critically before they ship it.
02
Nuxt's file-based routing confuses AI assistants
Agents often mix up server routes, middleware order and the data-fetching lifecycle in Nuxt 3. Developers who understand the framework underneath produce far fewer regressions than those who prompt their way through it.
03
State management decisions carry more weight now
Pinia and the Composition API give engineers more ways to structure shared state, and AI often picks the wrong one for the context. A senior developer spots the mismatch before it scales into a refactor.
How we assess Vue developers
Every engineer works through a fundamentals assessment with AI tools switched off and a second assessment with their own agents running. For Vue developers, these criteria carry the most weight.
- Technical understanding
In the first assessment, the engineer works through a real Vue 3 codebase without AI tools, so we can see whether they understand reactivity and the Composition API or are just pattern-matching.
- AI output verification
In the second assessment, the engineer builds a Nuxt feature with their own agents, and we check whether they catch the state and routing errors the AI introduces before committing the code.
- Debugging
Vue's reactivity warnings are easy to dismiss, so we check whether the engineer traces a broken reactive chain to its root cause or wraps it in a workaround.
Hiring with Miyagami
- One senior engineer, full-time, at a fixed monthly fee
- Employment, payroll and compliance included, no recruitment fee
Timeline
- Three-month minimum
- Wrong fit: we replace at our cost
How to review AI-generated code
Reviewing AI-generated code changes some of what reviewers look for and keeps the rest. This entry covers both, plus the specific failure modes to check for.
How do you test software you didn't design
Standard coverage metrics mislead when you test software you didn't design. This entry explains what engineers should do instead when reviewing AI-generated code.
What is a coding agent
A coding agent is an AI system that writes, edits, runs and debugs code autonomously across multiple steps, without a human directing each action.
Questions about hiring Vue developers
How senior are these Vue developers?
They have 6+ years' experience on average and have shipped and maintained production systems in Vue.js. Every one has passed both assessments, and you see both scorecards before you meet them.
How do you test Vue and Nuxt specifically?
The first assessment puts the developer in a Vue 3 codebase with no AI tools and covers state, composables and debugging. The second assessment repeats a similar task in Nuxt with their own AI agents running, so we see whether they verify the output or just accept it.
How quickly can a Vue developer start?
You get a shortlist within five working days of your brief, and most engagements reach a first commit within three weeks of that. Engagements are full-time with a three-month minimum.
What does a Vue developer from Miyagami cost?
You pay a fixed monthly fee of €5,600 to €8,000 per full-time engineer, with employment, payroll and compliance included and no recruitment fee. The pricing page compares it with the all-in cost of a senior local hire in your country. Engagements are full-time with a three-month minimum, and if a placement doesn't work out, we replace them at our cost.
Do they work in our tools and codebase?
They work in your tools and codebase. They join your repositories, communication channels and sprint process as full-time members of your team. We don't sit between you and the engineer day to day.
Get a shortlist within five working days
You share the roles and the stack in a short form or a thirty-minute call. Within five working days you get named senior engineers to review, each with both scorecards.
Certified