Angular interviews often cycle through the same pillars: dependency injection, change detection, components vs modules/standalone, signals vs Observables, forms, routing/guards, and RxJS basics.
How to answer well
- State trade-offs, not buzzwords—“OnPush when inputs are stable and we measure render cost”
- Compare briefly with React/Vue only when asked—focus on Angular mechanics
- Mention real constraints: legacy NgModule apps vs greenfield standalone
Quick revision list
- Draw DI: injector tree +
providedIn: 'root' - Explain
bootstrapApplicationandapp-root - Reactive vs template-driven forms
- CanActivate guard purpose
- When signals beat manual subscriptions in templates
Self-check
- Which topic in this track felt weakest—revisit that lesson.
- Practice a 60-second “What is Angular?” answer out loud.
Challenge
Interview drill
- Write three bullet answers in comments: DI, change detection, standalone bootstrap.
printOutputone of them.
Done when: terminal shows your chosen one-liner answer.
Interview: Practice explaining DI, change detection strategies, and when signals replace manual subscriptions.
Interview prep
- Must-know Angular interview topics?
DI, change detection, standalone bootstrap, signals vs observables, reactive forms, guards, and RxJS basics.