Vue interview

Vue interview

Vue interview questions written from your nine Vue notes — reactivity and computed, watchers and the lifecycle, templates, component communication, composables, directives and plugins, built-in components and tooling, and performance, accessibility and security.

Written on 20 October 2026 from your Vue notes: the nine notes in the Vue docs folder and the Vue part of Important. The questions are the kind an interviewer asks about Vue: how it works and why you would choose one tool over another, at a middle depth. Questions on topics from your Important note carry the Important badge and come first in Smart order.

Know

PageCoversQuestions
ReactivityHow tracking works, ref versus reactive, destructuring, computed and its cache, shallowRef, nextTick, a writable computed7
Watchers and the lifecyclewatch versus watchEffect, deep watching, race conditions and cleanup, flush timing, the lifecycle and what Vue cleans up, the update cycle7
Templates and renderingv-if versus v-show, keys, v-if with v-for, template refs and defineExpose4
Component communicationThe options and when to use which, one-way data flow, component v-model, provide/inject, scoped slots, fallthrough attributes6
ReusabilityComposables and their shared-state trap, a useFetch composable, custom directives, plugins5
Built-ins and toolingKeepAlive, Teleport, Suspense, Vite and Rolldown, Vue Router, Pinia6
Performance, accessibility and securityMaking an app faster, long lists, accessibility in an SPA, XSS4
  • Drill them: Train, press Only next to Vue interview, Smart order. Or open a note and press Practise … from this note.
  • Rehearse: a mock interview with Vue interview selected, answering the open questions out loud.

Be able to say

Be able to say· Explain Vue's reactivity in one minute.

"State is wrapped so Vue can intercept reads and writes: reactive uses a Proxy, ref a getter and setter on .value. While a component renders, every reactive value it reads records the render as a dependency. When a value is written, Vue looks up who depends on it: computeds are marked dirty, watchers are queued, and the component's re-render is queued for a microtask, so many changes cause one render, and only the components that read the value update. That's also why the DOM isn't updated right after an assignment, and nextTick exists."

Your notes

Open in Notes

Nothing yet. Notes filed here show up on every page of this section.