roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for NgRx interviews on Angular app state, from the Redux-style global Store to the signal-based SignalStore. Covers selectors, effects, entities and testing, plus the RxJS beneath them.
133 of 133 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 133 new. 0 cut, outside your plan.
NgRx questions usually arrive inside the Angular part of a frontend loop, as a stretch of the framework conversation or as the review of a take-home that already uses a store. Few interviewers ask what a reducer is. They hand you a scenario and ask where it breaks: a booking save whose outcome never arrives because the user clicked again, a login effect that stops answering after one wrong password, a per-customer view that recomputes on every dispatched action, a component that cannot call `patchState` on a store it injected. Each of those has one mechanism behind it, and naming it is what the interviewer is listening for. The save was cancelled by `switchMap` where `concatMap` belonged; `catchError` sat on the outer `actions$` pipe, so the first error completed the effect; an input selector that filters returns a new array on every call, so the memo compares a new reference each time; SignalStore keeps its state protected outside the store unless it is declared otherwise. From middle level up the questions widen to judgement: whether the app needs a store library at all, when a feature belongs in the global Store and when in a SignalStore, and how a team keeps its actions describing events rather than commands.
No NgRx API appears in the first stretch. The [store model](/topics/fe-ui-frameworks-concepts-state-stores-subscription) any library shares, [immutable updates](/topics/fe-ui-frameworks-concepts-state-equality-immutability) and [memoized derivation](/topics/fe-ui-frameworks-concepts-state-derived-values-memo) are the ideas NgRx's reducers and selectors encode, and [observable data services](/topics/fe-angular-rxjs-signals-data-services) are what an Angular team uses before it reaches for a store, so they set up the question of when one is warranted. RxJS follows because the classic Store is a stream: selecting from it, reacting to actions in an effect and recovering from a failed request are all operator work. [Flattening operators](/topics/fe-rxjs-pipeable-operators-flattening) and [error handling](/topics/fe-rxjs-error-retry) carry the most weight there. The Angular stretch then supplies what the newer half of the library is built from: [writable and computed signals](/topics/fe-angular-signals-writable-computed), the [bridges between signals and observables](/topics/fe-angular-rxjs-signals-interop) that `selectSignal` and `rxMethod` rely on, and the [injector scope](/topics/fe-angular-dependency-injection-service-scope) that decides how long a store lives. Only then does NgRx itself start, and the global Store follows the path of one action. It is [defined and dispatched](/topics/fe-ngrx-store-actions), a [reducer](/topics/fe-ngrx-reducers) turns it into new state, [selectors](/topics/fe-ngrx-selectors) hand that state to the view, and [effects](/topics/fe-ngrx-effects) handle the work a pure reducer cannot do, such as an HTTP call. The [entity adapter and ComponentStore](/topics/fe-ngrx-entity-component-store) close that stretch: one shapes collections inside the Store, the other keeps state local to a component. The [SignalStore](/topics/fe-ngrx-signal-store) comes after, with its [extensions](/topics/fe-ngrx-signal-store-extensions) for shared features, entities and the Events plugin; by then you can compare it with the Store you have just learned instead of meeting both at once. Testing closes the plan, where [marble tests](/topics/fe-rxjs-marble-testing) and NgRx's own [mock store and mock actions](/topics/fe-ngrx-testing) put the earlier mechanisms under proof.
Short on time before an Angular interview that lists NgRx? Raise importance to must know, narrow level to the seniority of the role, and put most of the hours into reducers, selectors and effects, where the scenario questions cluster. Candidates who already write NgRx every day can skim the opening concepts and go straight to the effects questions on operator choice and error recovery, then to SignalStore, which many codebases are adopting beside an older global Store. A senior candidate should be ready to argue the choice between the two for a given feature, and the conventions that keep either one readable on a large team. The plan treats Angular itself only where NgRx leans on it. Change detection, routing, forms, the HTTP client and NGXS, the store library teams weigh against NgRx, are in the [Angular roadmap](/roadmaps/angular).
NgRx questions usually arrive inside the Angular part of a frontend loop, as a stretch of the framework conversation or as the review of a take-home that already uses a store. Few interviewers ask what a reducer is. They hand you a scenario and ask where it breaks: a booking save whose outcome never arrives because the user clicked again, a login effect that stops answering after one wrong password, a per-customer view that recomputes on every dispatched action, a component that cannot call patchState on a store it injected.
Each of those has one mechanism behind it, and naming it is what the interviewer is listening for. The save was cancelled by switchMap where concatMap belonged; catchError sat on the outer actions$ pipe, so the first error completed the effect; an input selector that filters returns a new array on every call, so the memo compares a new reference each time; SignalStore keeps its state protected outside the store unless it is declared otherwise. From middle level up the questions widen to judgement: whether the app needs a store library at all, when a feature belongs in the global Store and when in a SignalStore, and how a team keeps its actions describing events rather than commands.
No NgRx API appears in the first stretch. The store model any library shares, immutable updates and memoized derivation are the ideas NgRx's reducers and selectors encode, and observable data services are what an Angular team uses before it reaches for a store, so they set up the question of when one is warranted.
RxJS follows because the classic Store is a stream: selecting from it, reacting to actions in an effect and recovering from a failed request are all operator work. Flattening operators and error handling carry the most weight there. The Angular stretch then supplies what the newer half of the library is built from: writable and computed signals, the bridges between signals and observables that selectSignal and rxMethod rely on, and the injector scope that decides how long a store lives.
Only then does NgRx itself start, and the global Store follows the path of one action. It is defined and dispatched, a reducer turns it into new state, selectors hand that state to the view, and effects handle the work a pure reducer cannot do, such as an HTTP call. The entity adapter and ComponentStore close that stretch: one shapes collections inside the Store, the other keeps state local to a component. The SignalStore comes after, with its extensions for shared features, entities and the Events plugin; by then you can compare it with the Store you have just learned instead of meeting both at once. Testing closes the plan, where marble tests and NgRx's own mock store and mock actions put the earlier mechanisms under proof.
Short on time before an Angular interview that lists NgRx? Raise importance to must know, narrow level to the seniority of the role, and put most of the hours into reducers, selectors and effects, where the scenario questions cluster. Candidates who already write NgRx every day can skim the opening concepts and go straight to the effects questions on operator choice and error recovery, then to SignalStore, which many codebases are adopting beside an older global Store. A senior candidate should be ready to argue the choice between the two for a given feature, and the conventions that keep either one readable on a large team.
The plan treats Angular itself only where NgRx leans on it. Change detection, routing, forms, the HTTP client and NGXS, the store library teams weigh against NgRx, are in the Angular roadmap.