Angular interviews cover dependency injection, RxJS, change detection, and TypeScript — the framework is opinionated, so questions test whether you understand its machinery. Below are the most common with model answers. Senior: architecture, trade-offs, mentoring, and decision-making.
Nearest to where it is used: a signal in a component for local state, a service with signals for state shared by a feature, and a full store only when many features write the same state and you need traceable changes. Reaching for NgRx by default costs boilerplate on every screen; reaching for it too late costs a refactor when the bug is state getting out of sync.
Measure which phase is slow — initial load, change detection or a specific interaction — because the fixes are unrelated. For load: lazy routes, bundle analysis, and removing dependencies imported whole. For change detection: OnPush, trackBy on lists, and moving expensive work out of getters called on every check. A getter in a template runs far more often than people expect.
Use ng update on schedule rather than in a batch, since Angular ships migration schematics that only work version by version. Stay close to the framework's idioms — a custom abstraction over the router or forms is what breaks. Deprecations are announced a version ahead, so a codebase that upgrades every release rarely sees a breaking change at all.
By feature, each with its own routes, components and services, and a shared layer that features may use but which knows nothing about them. Enforce the direction with lint rules rather than convention, because convention loses. The test is whether a feature can be deleted in one commit; if not, its boundaries were never real.
It buys a first paint with content and a page a crawler can read without executing JavaScript. It costs a server that renders per request, a codebase that must not touch window during render, and hydration bugs where server and client disagree. For an authenticated dashboard it usually buys nothing, which makes it a per-route decision.
In a real interview you speak under pressure. Cam asks these same questions, scores every answer, and shows exactly what to fix.
Practice a Senior Angular Frontend interview →