Framework Pack · Mid to Senior
Vue Developer Interview Pack
The reactivity system, Composition API, SFC patterns, Vuex/Pinia and router.
Vue's reactivity and Composition API, with the state-management and performance questions.
- Questions
- 360
- Topics
- 20
- Pages
- 330pages
- 360 questions, every one with a model answer
- Reactivity + Composition cheat sheet
- Pinia patterns
- Performance & SSR
Get the Vue Developer Interview Pack — $9
One-off. Delivered as a PDF by email the moment payment clears.
Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
- Reactivity fundamentals, refs and reactive objects
- Reactivity in depth, effects and scopes
- Computed values, watchers and flush timing
- The Composition API, setup and script setup
- Single-file components and the template compiler
- The rendering mechanism, virtual DOM and patching
- Props, events and provide and inject
- Slots, scoped slots and template references
- Designing component APIs that age well
- Lifecycle hooks and keeping components alive
- Teleport, KeepAlive, Suspense and transitions
- Custom directives, plugins and application setup
- List rendering, keys and large collections
- Writing composables that hold up in a team
- State management with Pinia
- Vue Router, guards and lazy routes
- TypeScript in Vue components
- Testing Vue components and composables
- Performance, rendering cost and build size
- Server-side rendering, hydration and mismatch
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
- ref wraps a single value and needs a .value in script while unwrapping itself in templates.
- A getter that runs inside a tracking context records every reactive property it touches, and only those.
- A computed value is lazy and cached: the derivation runs on first read and again only when a dependency changes.
- setup runs once per component instance, before the template is created, and is where reactive state is declared.
- A single-file component is a packaging format; the build step compiles the template ahead of the browser.
- A reactive write marks the component's render effect dirty and queues it; the scheduler flushes once per tick.
Questions this pack covers
- Why does reading something in a template count as registering a dependency?
- When is a ref the better choice than a reactive object in script?
- How does Vue work out which properties an effect actually depends on?
- Why do several writes in one tick produce a single effect run rather than several?
- What makes a computed value behave differently from a method in a template?
- Why does a computed value not need a dependency array?
- What does setup run that the Options API does not?
- Why is a top-level binding in script setup visible to the template without being returned?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
About this pack
- How many questions?
- 360, spread across 20 topics, written out in full across 330 pages.
- Do the answers just list keywords?
- No. Each answer is written as prose, because that is what you have to reproduce when someone asks you the question.
- How do I get it?
- Pay once and the PDF arrives by email immediately, with a signed download link.
- Can I get it refunded?
- Yes, if it is not what you expected. See the refund policy.
