What out-of-the-box Angular features require manual setup in Vue or Svelte?

WHAT THIS TESTS: This question checks whether you understand framework philosophy and scope. Angular is described as opinionated and fully featured on angular.dev, so the interviewer wants to see if you know which capabilities ship as first-party modules versus which ones require external packages in Vue or Svelte. It also reveals whether you can discuss tradeoffs without descending into framework fanboyism.

A GOOD ANSWER COVERS: A strong response names four core areas in order. First, the router: Angular provides a first-party routing module with guards, resolvers, and lazy loading out of the box, whereas Vue typically uses Vue Router and Svelte relies on SvelteKit or separate routing libraries. Second, forms: Angular ships both template-driven and reactive forms with built-in validators, while Vue and Svelte generally integrate community form libraries or write custom validation logic. Third, dependency injection: Angular has a hierarchical DI system built into the framework, which Vue and Svelte lack as a core construct, relying instead on provide or inject patterns or context APIs. Fourth, Signals and change detection: Angular Signals are now a core reactivity primitive included from the start, whereas Vue has reactivity built in but via a different proxy-based system, and Svelte uses compile-time reactivity. A great candidate also notes that Angular's deferrable views and hydration are first-party features that demonstrate its platform approach.

COMMON WRONG ANSWERS: The biggest red flag is claiming Angular is just better without naming specific features. Another mistake is confusing the framework with third-party add-ons, such as attributing state management libraries like NgRx to Angular itself. Some candidates also incorrectly state that Vue or Svelte cannot do these things; the question is about what is included out of the box, not what is possible. Finally, omitting dependency injection entirely signals a shallow understanding of Angular's architecture.

LIKELY FOLLOW-UPS: An interviewer might ask when you would prefer a lighter framework despite missing these features. They could also ask how Angular's dependency injection compares to React Context or Vue's provide and inject. Another follow-up is how bundle size and tree shaking factor into the decision to use a fully featured framework.

ONE CONCRETE EXAMPLE: Imagine onboarding five new developers to a large enterprise application. With Angular, the team gets a single set of documentation and patterns for routing, form validation, and state updates via Signals without debating which npm package to use. In a Vue or Svelte project, the lead engineer would need to evaluate Vue Router versus another option, choose between VeeValidate or FormKit, and decide on a state management strategy, which adds decision fatigue but allows tighter bundle control.

Source: angular.dev