Vue interviews mix framework mechanics with general frontend judgment. Be ready to explain reactivity, component communication, and when you would pick Vue vs React for a greenfield team.
Core topics
refvsreactive— when to use eachcomputedvswatch— derived data vs side effectsv-modelon components —modelValue+update:modelValue- Composition API vs Options API — same reactivity, different organization
- Pinia vs provide/inject — global store vs localized dependency injection
System design angle
Practice sketching a filter + list + detail screen with props/emits, then where you would introduce a composable or store. Interviewers care about trade-offs, not memorized API lists.
Self-check
- Explain reactivity in one sentence without saying “magic.”
- When would you choose Vue over React for a new SPA?
Challenge
Whiteboard communication
- Draw props-down / emits-up for a todo app on paper.
- Mark where you would add a composable for
useTodos.
Done when: you can explain data flow without opening the docs.
Interview: Practice explaining ref vs reactive and when computed beats a watcher—those two comparisons appear constantly in Vue screens.
Interview prep
- Must-know Vue interview topics?
Reactivity, props/emits, v-model on components, computed vs watch, Composition API vs Options API, Pinia vs local state—always explain trade-offs.