What out-of-the-box Angular features require manual setup in Vue or Svelte?
Tests whether you understand framework scope tradeoffs. A strong answer cites first-party routing, forms, dependency injection, and Signals, then contrasts them with Vue or Svelte's add-on ecosystem.
What's really being asked
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.
The full answer
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.
The mistakes people make
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.
What usually comes next
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.
A 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.
Interview question
Which built-in Angular module is specifically designed for handling user input and validation, a capability that Vue and Svelte projects typically address through external libraries such as VeeValidate or FormKit?
- a.Template-driven and reactive formsCorrect
- b.Signal-based change detection
- c.State management with NgRx
- d.Hierarchical dependency injection
Why? this is the answer
Angular ships template-driven and reactive forms with built-in validators as a first-party module, while Vue and Svelte generally rely on community libraries like VeeValidate or FormKit for equivalent functionality. NgRx is the most tempting distractor because it is a third-party state management library, not a built-in Angular feature.
Just read this? Test yourself on what you have been reading.
Read the original → angular.dev
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on angular — each one lists the topics its interview covers.
See open roles