Question 1

How do you structure a scalable Vue 3 app?

Accepted Answer

Feature modules with routes, composables, components; shared UI kit; Pinia domains. Colocate tests. Enforce public API boundaries between features.

Question 2

Container vs presentational components in Vue?

Accepted Answer

Containers fetch/orchestrate; presentational receive props/emit events and use slots. Improves reuse and testing. Don't be dogmatic for tiny views.

Question 3

When choose Nuxt vs plain Vite+Vue?

Accepted Answer

Nuxt for SSR/SSG, file routing, conventions; Vite+Vue for simple SPAs or custom setups. Nuxt accelerates product apps with SEO needs. Understand lock-in/conventions.

Question 4

Handling API clients cleanly?

Accepted Answer

Thin API module, typed DTOs, map to view models, central error handling. Composables/stores call API—not raw axios in every component.

Question 5

Microfrontends with Vue — considerations?

Accepted Answer

Shared design tokens, routing ownership, bundle duplication, team autonomy. Prefer modular monolith unless org constraints demand otherwise.

Question 6

Error handling strategy across the app?

Accepted Answer

Global error hooks, route-level boundaries, user-friendly toasts, logging pipeline. Don't swallow errors in composables silently.

Question 7

Design auth flow architecture in Vue.

Accepted Answer

Auth store, router guards, token refresh interceptor, secure storage choices. Keep tokens out of localStorage if threat model requires; prefer httpOnly cookies when feasible.

Question 8

Lead: migrating a Vue 2 app to Vue 3?

Accepted Answer

Build/tooling first, compat build if needed, replace filters/global API, Vuex→Pinia, test critical paths. Incremental migration beats big bang. Train the team on Composition API.

Architecture Vue.js Interview Questions

Other Vue.js interview topics