Angular Interview Questions to Expect

Angular's API surface is large, and published question lists treat every decorator as equally likely to come up. They are not equally likely. This section covers the areas that actually decide most rounds, so your practice matches the real distribution. Four clusters dominate:

• Change detection: what triggers a check, how Zone.js patches async APIs, what OnPush changes, and how signals let Angular skip work.
• Dependency injection: hierarchical injectors, providedIn, injection tokens, and the inject() function against constructor parameters.
• RxJS: observables against promises, choosing the right operator, and cleaning up subscriptions before a component is destroyed.
• Component architecture: standalone components, inputs and outputs, content projection, and lifecycle hooks.

Version awareness matters more here than in most framework rounds, because Angular changed direction. Standalone components, the built-in control flow blocks @if and @for, deferrable views, and signals all arrived in recent major versions, so interviewers often ask what you would write today against what an older codebase uses. Knowing both, and why the framework moved, reads better than picking a side.

Deeper than operator names. The RxJS question that separates levels is which flattening operator fits: switchMap cancels the previous inner request and suits a typeahead, mergeMap runs everything in parallel, concatMap preserves order, and exhaustMap ignores new events while one is still in flight, which is why it suits a submit button. Interviewers then ask the leak question: what happens to a manual subscription when the component is destroyed, and why the async pipe or takeUntilDestroyed removes the problem.

Signals questions are newer and usually start from motivation rather than API. Expect to explain what a signal is, how computed derives from one, what an effect is for, and why signals give Angular a finer-grained way to know what changed than re-checking a component tree. A strong answer connects the two topics: signals and OnPush both reduce the work change detection does, but signals do it by tracking reads rather than by narrowing when a check runs.

Interviewers do not expect you to have shipped every recent feature. They expect you to say which version you last worked in and to reason clearly about the rest.

Most Angular loops include building something small while the interviewer watches. The recurring exercises are stable across companies:

• Call an API from a service and render the result with the async pipe.
• Build a typeahead search with debounceTime, distinctUntilChanged, and switchMap.
• Write a reactive form with a custom validator and visible error states.
• Pass data between a parent and child component, then lift it into a service.
• Add a route with a lazily loaded component and a guard.

A front-end engineer interviewing for a mid-level product role, for example, might build the typeahead, then get pushed on what happens when responses arrive out of order, how to show a loading state, and what should happen when the user clears the input. Those extensions are where the round is decided, so practice the follow-ups rather than the happy path. Adjacent sets that Angular rounds still open with, including plain JavaScript and TypeScript fundamentals, are in the question banks hub.

Reading a question list builds recognition, not recall, and the round tests recall while someone watches. The fix is reps in the round's real shape: build the standard exercises from an empty project, narrate the change detection and subscription decisions out loud while typing, and absorb interruptions without losing the thread. Running the set as a spoken rehearsal, one question at a time with follow-ups, is what mock interview practice is for.

One limit worth stating plainly: Angular live rounds nearly always run in a shared editor or with your screen visible, and anything on that screen is visible to the interviewer. An assistant belongs in preparation and in conversation-led rounds, not on a shared screen. Which formats allow what is covered in interview types.