roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for Vue 3 interviews by explaining how the framework works, not only how to use it. Covers reactivity, components, rendering, SSR and testing, plus Vue Router, Pinia, Nuxt and forms.
507 of 507 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 507 new. 0 cut, outside your plan.
Vue is tested inside frontend and full-stack interviews at teams that build on it, rather than in a separate loop. Expect it in the technical conversation after a JavaScript screen, and in a practical task: a component written live or taken home, such as a search field that debounces its requests, read afterwards for where the state lives and what crosses the props-and-events boundary. From senior level up, a design discussion adds the larger choices, such as server rendering against a client-only app, or moving a Vue 2 codebase forward without freezing feature work.
Most technical questions come down to what the reactivity system tracks. Why does a value destructured out of a reactive object stop updating the template? Why does watch refuse state.count as a source but accept () => state.count? Why does code that reads the DOM right after a state change still see the old value until nextTick resolves?
Levels are told apart by following one question down. Asked why a list did not re-render, an early-career candidate offers the fix that worked. A stronger one explains that Vue 3 records reads through proxies and batches updates until the next tick, so the fix follows from the mechanism. At senior and principal level the same question comes back as an incident: a hydration mismatch from a timestamp rendered on the server, or state declared at module scope that leaked one user's data into another's server render.
The first module is the framework itself, ordered from the surface down and then outward. After single-file components, the reactivity system comes early, since almost every topic after it assumes you know what it tracks, with the Composition API built directly on top. The Options API arrives only after the component contract, on purpose: the plan treats the composition style as the default and the older one as something met in existing code. From the rendering mechanism onward the module asks what happens after a change, which sets up bundle tuning and server-side rendering; it closes on types, tests and the move from Vue 2, the concerns of a codebase that already exists.
Each library module then leans on part of that core. Vue Router maps URLs onto components, its guards raise the timing questions and its lazy routes are bundle splitting applied per page. Pinia follows because a store is reactive state with a module boundary around it, and its server-side section repeats the core's server-rendering rule that state is created once per request; VueUse shows the Composition API's patterns packaged by someone else.
Nuxt waits until routing, stores and server rendering are all in place, because it assembles exactly those, adding data fetching that runs on the server and hands its result to the client instead of requesting it twice. VitePress is the case where every page is generated ahead of time. The plan then narrows to single libraries: VeeValidate for forms, and Tailwind, where source detection explains why a class name assembled from a string at runtime does not reach the stylesheet.
Tooling closes the plan. Vue Testing Library takes a stricter line than the core module's component testing, since its tests see only what a user would. Vite comes last because you have used its dev server all along; the module explains it, from serving source as native ES modules to the separate production build, which is why a bug can appear in the build and not in development.
The core module is where a short runway goes when Vue is the posting's main framework. Filtering importance down to must know thins it to the reactivity, template and component-contract questions a framework round is built from, and study order needs no change. Come back for Router and Pinia once your answers about `watch` and `computed` survive a second "why". A React developer joining a Vue team has habits to unlearn more than facts to learn: immutable updates and dependency arrays carry over badly to a system that tracks mutation by itself, and study order set to by topics brings reactivity ahead of everything that assumes it. Someone who wrote Vue 2 is fluent in the Options API and unsure what changed underneath, so reactivity and the migration topic come first, starting with why `Vue.set` is gone now that property access goes through a proxy. Senior candidates gain most from rendering, server rendering and Nuxt's rendering modes, where design talk about a slow page is settled. The plan is Vue and its ecosystem. It does not teach the JavaScript language underneath, the browser platform, accessibility, or CSS beyond the Tailwind it carries, yet a Vue round usually sits inside a loop that asks about all of them. That wider loop is what the [Frontend Developer roadmap](/roadmaps/frontend) prepares for.
The core module is where a short runway goes when Vue is the posting's main framework. Filtering importance down to must know thins it to the reactivity, template and component-contract questions a framework round is built from, and study order needs no change. Come back for Router and Pinia once your answers about watch and computed survive a second "why".
A React developer joining a Vue team has habits to unlearn more than facts to learn: immutable updates and dependency arrays carry over badly to a system that tracks mutation by itself, and study order set to by topics brings reactivity ahead of everything that assumes it. Someone who wrote Vue 2 is fluent in the Options API and unsure what changed underneath, so reactivity and the migration topic come first, starting with why Vue.set is gone now that property access goes through a proxy. Senior candidates gain most from rendering, server rendering and Nuxt's rendering modes, where design talk about a slow page is settled.
The plan is Vue and its ecosystem. It does not teach the JavaScript language underneath, the browser platform, accessibility, or CSS beyond the Tailwind it carries, yet a Vue round usually sits inside a loop that asks about all of them. That wider loop is what the Frontend Developer roadmap prepares for.