Vue

Vue interviews focus on single-file components, declarative templates, and a reactivity system that tracks dependencies automatically. Strong answers connect API style (Composition vs Options) to logic organization, not syntax trivia.

Subtopics: Composition API, Options API, reactivity primitives, Vue Router, and Pinia for shared state.

On interviews: explain when to use `ref` versus `reactive`, how computed and watchers participate in the graph, and how routing state differs from domain state in Pinia.

Common pitfalls: mutating reactive objects without understanding proxies, storing route params in global stores unnecessarily, and mixing Options and Composition without a team convention.

Checklist:

• Know SFC structure: template, script, style.
• Name reactivity primitives and their unwrap rules.
• Separate navigation state from app state.
• Justify API style for team maintainability.