roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for Angular interviews on the current framework: standalone components, signals, zoneless change detection, RxJS and NgRx. Covers DI, routing, forms, SSR and AnalogJS, testing and the CLI.
704 of 704 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 704 new. 0 cut, outside your plan.
A loop given over entirely to Angular is unusual. Teams whose product already runs on it hold a framework conversation inside the frontend loop, after the JavaScript and browser fundamentals; some loops swap that conversation for a take-home that extends a small Angular app, and the reviewer reads it for the same things a conversation would probe. The framework has changed shape more than once, so many questions straddle two eras: here is a component with `@Input` decorators, `*ngIf` and an NgModule, so what does the standalone, signal-based version look like, and what changes at runtime once zone.js is gone? Diagnoses carry the rest. An `OnPush` child ignores an item pushed into its parent's array. An `ExpressionChangedAfterItHasBeenCheckedError` appears only in development. A type-ahead shows results for an older query because its stream was flattened with `mergeMap` rather than `switchMap`. A service has two instances because a lazy route provided it again. What lifts a correct answer to a strong one is placement: the injector an instance came from, the moment change detection will next visit the view, the owner of a subscription's end. Senior conversations add trade-offs with a cost attached, such as an NgRx store against signal-based services, or a staged move off NgModules and zone.js.
The plan opens on what a view declares: [component authoring](/topics/fe-angular-components-templates), [the template language](/topics/fe-angular-templates) that binds it, and the directives that add behavior to an element and the pipes that transform a value before the template shows it. [Signals](/topics/fe-angular-signals) come before [change detection](/topics/fe-angular-change-detection) on purpose: without zone.js, a change to a signal the template read is one of the few things that schedules a check, so the old scheduler and its replacement compare best once the signal graph is familiar. Observables come after signals rather than before them. [RxJS](/topics/fe-rxjs) is taught first on its own terms, apart from the framework, then through [its Angular patterns](/topics/fe-angular-rxjs-signals), whose bridges between a signal and an observable join this stretch to the previous one. [NgRx](/topics/fe-ngrx) builds on both models at once, from an action-and-reducer store that is RxJS throughout to its signal-based store, with NGXS beside it. The plan then turns from state to structure. [Dependency injection](/topics/fe-angular-dependency-injection) and [bootstrapping](/topics/fe-angular-app-structure) explain where an instance and an application's configuration come from, and they sit right before the router, forms and HTTP because that layer is built on them: [route guards](/topics/fe-angular-modules-routing-guards) and interceptors are plain functions that call `inject()`. [Angular Material and the CDK](/topics/fe-angular-material) come straight after forms: a Material form field wraps the controls just covered and decides from their state when an error shows, and a dialog hands data to the component it opens through an injection token, so both lean on what precedes them. Delivery follows. [SSR and prerendering](/topics/fe-angular-ssr) and AnalogJS come before [load and render speed](/topics/fe-angular-performance), since deferrable views and incremental hydration are two halves of one question. Security, localization and animation are concerns any feature may touch. The last stretch is the code's life outside the running app, from the [testing toolkit](/topics/fe-angular-testing) and the [compiler](/topics/fe-angular-compiler) to the CLI, and it ends on [upgrades](/topics/fe-angular-upgrades), placed last because a multi-major migration draws on every module above it.
Where to begin depends on which Angular you already know. If you last shipped it with NgModules, decorators and zone.js, start at Reactivity and read the [modernization migrations](/topics/fe-angular-upgrades-modernization) early, because the questions that expose you are about the current idiom. From React, components and signals map onto what you know while injector hierarchies and observables do not; take the hub guide's order instead of the page's, components and templates and then signals with dependency injection, and RxJS straight after. In the last week, must know is the only part of importance worth keeping, and the first three modules plus dependency injection deserve most of the hours, since most framework conversations stay inside them; study order can stay as it is. A few months out, pick by topics under study order, write one small feature the way Angular looked a few majors ago, and carry it forward with the framework's own migration schematics: the diff answers many of the straddling questions above. The plan assumes the language and platform beneath the framework. TypeScript appears only where Angular leans on it, and the JavaScript, CSS and browser questions that open most frontend loops are not here. The [Frontend Developer roadmap](/roadmaps/frontend) prepares for that round, and the [TypeScript roadmap](/roadmaps/typescript) for the language itself.
A loop given over entirely to Angular is unusual. Teams whose product already runs on it hold a framework conversation inside the frontend loop, after the JavaScript and browser fundamentals; some loops swap that conversation for a take-home that extends a small Angular app, and the reviewer reads it for the same things a conversation would probe.
The framework has changed shape more than once, so many questions straddle two eras: here is a component with @Input decorators, *ngIf and an NgModule, so what does the standalone, signal-based version look like, and what changes at runtime once zone.js is gone? Diagnoses carry the rest. An OnPush child ignores an item pushed into its parent's array. An ExpressionChangedAfterItHasBeenCheckedError appears only in development. A type-ahead shows results for an older query because its stream was flattened with mergeMap rather than switchMap. A service has two instances because a lazy route provided it again.
What lifts a correct answer to a strong one is placement: the injector an instance came from, the moment change detection will next visit the view, the owner of a subscription's end. Senior conversations add trade-offs with a cost attached, such as an NgRx store against signal-based services, or a staged move off NgModules and zone.js.
The plan opens on what a view declares: component authoring, the template language that binds it, and the directives that add behavior to an element and the pipes that transform a value before the template shows it. Signals come before change detection on purpose: without zone.js, a change to a signal the template read is one of the few things that schedules a check, so the old scheduler and its replacement compare best once the signal graph is familiar.
Observables come after signals rather than before them. RxJS is taught first on its own terms, apart from the framework, then through its Angular patterns, whose bridges between a signal and an observable join this stretch to the previous one. NgRx builds on both models at once, from an action-and-reducer store that is RxJS throughout to its signal-based store, with NGXS beside it.
The plan then turns from state to structure. Dependency injection and bootstrapping explain where an instance and an application's configuration come from, and they sit right before the router, forms and HTTP because that layer is built on them: route guards and interceptors are plain functions that call inject(). Angular Material and the CDK come straight after forms: a Material form field wraps the controls just covered and decides from their state when an error shows, and a dialog hands data to the component it opens through an injection token, so both lean on what precedes them.
Delivery follows. SSR and prerendering and AnalogJS come before load and render speed, since deferrable views and incremental hydration are two halves of one question. Security, localization and animation are concerns any feature may touch. The last stretch is the code's life outside the running app, from the testing toolkit and the compiler to the CLI, and it ends on upgrades, placed last because a multi-major migration draws on every module above it.
Where to begin depends on which Angular you already know. If you last shipped it with NgModules, decorators and zone.js, start at Reactivity and read the modernization migrations early, because the questions that expose you are about the current idiom. From React, components and signals map onto what you know while injector hierarchies and observables do not; take the hub guide's order instead of the page's, components and templates and then signals with dependency injection, and RxJS straight after.
In the last week, must know is the only part of importance worth keeping, and the first three modules plus dependency injection deserve most of the hours, since most framework conversations stay inside them; study order can stay as it is. A few months out, pick by topics under study order, write one small feature the way Angular looked a few majors ago, and carry it forward with the framework's own migration schematics: the diff answers many of the straddling questions above.
The plan assumes the language and platform beneath the framework. TypeScript appears only where Angular leans on it, and the JavaScript, CSS and browser questions that open most frontend loops are not here. The Frontend Developer roadmap prepares for that round, and the TypeScript roadmap for the language itself.