Interview questions

Angular Interview Questions

20 Angular interview questions with model answers: components, signals, change detection, zoneless, RxJS, DI, routing and forms. For both sides.

Angular Interview Questions

What's here

20 Angular interview questions, grouped into 4 areas: components and templates, reactivity and change detection, architecture: di, routing, forms and http and performance, testing and scenarios. Each one comes with why it is worth asking and what a strong answer contains, so the same question can be scored the same way by different interviewers.

  • Ask which Angular version the candidate works with today; standalone components, signals and zoneless change detection depend on it.
  • Give a short component with a subscription leak or a missing track expression and ask what is wrong.
  • Use the type-ahead task to test RxJS fluency in a realistic way.
For hiring teams

Cohesyve finds, contacts and tests Angular candidates on the real work, then ranks them for these interviews. 14-day free trial for 10 candidates, not charged until it ends.

Preparing for this interview yourself? Practise it free →

These Angular interview questions cover what front-end interviews test on modern Angular: standalone components, templates and the built-in control flow, signals, change detection with and without zone.js, RxJS, dependency injection, routing, forms and testing, plus how Angular differs from AngularJS. Candidates can use the 'what to look for' notes as model answers; interviewers can use them as a scoring guide.

Components and Templates

The building blocks of an Angular application.

  1. 1

    What is the difference between Angular and AngularJS?

    Why ask it

    Still asked, especially where legacy code exists.

    What to look for

    AngularJS (1.x) is the original JavaScript framework built around scopes and controllers; its official support ended in January 2022. Angular (2 and later) is a rewrite in TypeScript built around components, dependency injection and a compiler. Migrating between them is a rewrite or a gradual hybrid, not an upgrade.
  2. 2

    What is a standalone component, and how does it relate to NgModules?

    Why ask it

    Checks whether the candidate knows current Angular.

    What to look for

    Components are standalone by default from Angular 19: they declare their own imports and can be used directly in other components' imports. Before 19 the default was false and components were declared in NgModules. Candidates should be able to work in both styles.
  3. 3

    Explain the types of data binding in Angular templates.

    Why ask it

    Everyday Angular template knowledge.

    What to look for

    Interpolation with double curly braces, property binding with square brackets, event binding with parentheses, and two-way binding with the banana-in-a-box syntax, which combines the two. Good answers mention input and output properties for component communication.
  4. 4

    Which lifecycle hooks do you use most, and for what?

    Why ask it

    Shows practical experience.

    What to look for

    ngOnInit for initial setup that needs inputs, ngOnChanges for reacting to input changes, ngAfterViewInit for work that needs the rendered view, and ngOnDestroy for cleanup. Strong candidates note that signals and DestroyRef reduce the need for some hooks.
  5. 5

    How does the built-in control flow (@if, @for, @switch) work, and why does @for use track?

    Why ask it

    The modern template syntax.

    What to look for

    @if renders content conditionally with optional @else blocks; @for loops over any iterable with variables such as $index and an optional @empty block; @switch compares with strict equality and has no fallthrough. The track expression ties each item to its DOM nodes so Angular updates only what changed; use a unique ID rather than the object reference.
For hiring teams

Before the Angular interviews, see who can do the work

Cohesyve finds and contacts Angular candidates from your job description and tests each one on an AI job simulation of the role, so these questions go to a ranked shortlist. 14-day free trial for 10 candidates, not charged until it ends.

Reactivity and Change Detection

How Angular knows when to update the screen, which is where most performance questions come from.

  1. 6

    What are signals, and how do signal, computed and effect differ?

    Why ask it

    Signals are central to modern Angular.

    What to look for

    A signal wraps a value and notifies consumers when it changes; you read it by calling it and update a writable signal with set or update. computed derives a read-only value from other signals, lazily and cached. effect runs side effects when signals it reads change, and should be used sparingly, for syncing with non-reactive APIs.
  2. 7

    How does change detection work, and what is zoneless Angular?

    Why ask it

    Explains performance behaviour and recent changes.

    What to look for

    zone.js patches browser APIs to learn when async events happen and then runs change detection, often more than needed because it cannot tell whether state changed. Zoneless change detection relies on signals and explicit notifications instead, and it is the default for new apps from Angular 21. On Angular 20 it is opt-in with provideZonelessChangeDetection.
  3. 8

    What does the OnPush change detection strategy do?

    Why ask it

    A standard performance tool.

    What to look for

    An OnPush component is checked only when its inputs change by reference, an event fires inside it, an async pipe emits, or a signal it reads changes. It pushes teams towards immutable data and makes large component trees cheaper to check.
  4. 9

    Observables versus promises: what is the difference, and which RxJS operators do you use most?

    Why ask it

    RxJS is still widely used in Angular codebases.

    What to look for

    A promise resolves once and starts immediately; an observable can emit many values, is lazy until subscribed and can be cancelled. Common operators: map, filter, switchMap (cancel previous inner requests), mergeMap, debounceTime, distinctUntilChanged, catchError and takeUntil.
  5. 10

    When would you use signals and when RxJS?

    Why ask it

    Tests current architectural judgement.

    What to look for

    Signals suit synchronous UI state and derived values; RxJS suits streams of events over time, such as debounced input, websockets and complex async coordination. Interop helpers convert between them. A thoughtful answer avoids forcing everything into one model.

Architecture: DI, Routing, Forms and HTTP

How Angular applications are structured and how data flows through them.

  1. 11

    How does dependency injection work in Angular?

    Why ask it

    DI is fundamental to Angular's design.

    What to look for

    Classes declare dependencies through the inject function or constructor parameters, and injectors provide instances. providedIn: 'root' creates an app-wide singleton and allows tree-shaking; providers on a component or route create scoped instances. Hierarchical injectors explain why two components may get different instances.
  2. 12

    How would you share state between components that are not parent and child?

    Why ask it

    A common design question.

    What to look for

    A service holding state, exposed as signals or observables, injected where needed. For larger apps, a state management library may help. Avoid deep input and output chains and global mutable objects.
  3. 13

    How do lazy loading and route guards work?

    Why ask it

    Routing affects performance and security.

    What to look for

    Lazy loading loads a route's components only when the user navigates there (loadComponent or loadChildren), shrinking the initial bundle. Guards decide whether navigation can happen, for example checking authentication; resolvers fetch data before a route activates. Guards are a UX layer, and the server must still enforce access.
  4. 14

    Template-driven forms or reactive forms: when do you use each?

    Why ask it

    Forms are central to most business apps.

    What to look for

    Template-driven forms are quick for simple forms with logic in the template. Reactive forms define the model in code with FormControl and FormGroup, which makes validation, dynamic fields and testing easier for complex forms. Good answers mention custom and async validators.
  5. 15

    What are HTTP interceptors used for?

    Why ask it

    A practical HttpClient question.

    What to look for

    Interceptors process every request and response: adding auth headers, handling errors centrally, logging, retrying and showing loading state. Modern Angular supports functional interceptors registered with provideHttpClient.

Performance, Testing and Scenarios

Engineering judgement and practical problem solving.

  1. 16

    An Angular page feels slow. How would you investigate?

    Why ask it

    Tests a measured approach to performance.

    What to look for

    Profile with Angular DevTools and browser tools to find excessive change detection or heavy rendering. Fixes: OnPush or signals, track in @for, lazy loading, deferring heavy content, avoiding function calls in templates that do expensive work, and virtual scrolling for long lists.
  2. 17

    How do you avoid memory leaks from subscriptions?

    Why ask it

    A common Angular bug.

    What to look for

    Use the async pipe, which subscribes and unsubscribes automatically; use takeUntilDestroyed or DestroyRef for manual subscriptions; prefer signals where they fit. HttpClient requests complete on their own, but long-lived streams do not.
  3. 18

    How do you test Angular components and services?

    Why ask it

    Testing habits show quality.

    What to look for

    Unit tests for services with injected fakes; component tests with TestBed that render the template and interact as a user would; HTTP testing utilities to mock requests; end-to-end tests for critical journeys. Test behaviour, not private implementation.
  4. 19

    How would you migrate a large app from NgModules to standalone components?

    Why ask it

    A common real-world task in 2026.

    What to look for

    Migrate incrementally, using the official schematics where they help, convert leaf components first, keep the app building and tests passing at each step, and update routing to lazy-load standalone components. Mixed codebases are fine during the transition.
  5. 20

    Build a type-ahead search that calls an API. Which tools would you use?

    Why ask it

    A realistic task combining RxJS and UX.

    What to look for

    A form control's value changes piped through debounceTime, distinctUntilChanged and switchMap so stale requests are cancelled, with catchError for failures; loading and empty states; and accessible keyboard handling. A signals-based version with explicit debouncing is also acceptable.

Running the interview well

  • 1Ask which Angular version the candidate works with today; standalone components, signals and zoneless change detection depend on it.
  • 2Give a short component with a subscription leak or a missing track expression and ask what is wrong.
  • 3Use the type-ahead task to test RxJS fluency in a realistic way.
  • 4Do not mark down candidates from older Angular codebases if they understand the concepts and can explain the newer equivalents.
  • 5For senior roles, discuss state management, migrations and performance on large apps.
  • 6Check TypeScript and JavaScript fundamentals alongside Angular knowledge.

Common questions

What Angular topics are asked most in interviews?

Components and templates, data binding, lifecycle hooks, dependency injection, services, routing and lazy loading, forms, RxJS, change detection, and increasingly signals and standalone components.

How should I prepare for an Angular interview?

Build a small app with routing, a reactive form, HTTP calls and tests, using standalone components and signals. Practise explaining change detection and how you would fix a slow page.

Are AngularJS interview questions still asked?

Only where companies maintain legacy AngularJS apps. AngularJS support ended in January 2022, so expect questions on scopes, controllers and directives mainly in migration roles.

Do I need to know RxJS for Angular interviews?

Yes, at least the basics. Many codebases rely on observables for HTTP, forms and events. Know subscribing, the async pipe and common operators such as switchMap and debounceTime.

What are signals in Angular?

Reactive values that notify Angular when they change, so it can update exactly the parts of the UI that depend on them. They come with computed values and effects, and underpin zoneless change detection.

Is Angular still used in 2026?

Yes, particularly for large business and enterprise applications. Interviewers value candidates who know the modern features as well as the established patterns found in existing codebases.

For hiring teams

Save these questions for the Angular candidates who can do the work

Cohesyve takes your Angular job description, finds candidates, reaches out to them and runs an AI job simulation of the real work, then returns a ranked shortlist.

1,500+

assessments completed

50%

faster time-to-hire

5 min

from JD to assessment

14-day free trial · 10 candidates · Not charged until the trial ends

For job seekers

Preparing for an Angular interview yourself? Practise on an AI job simulation of the role. 3-day free trial, cancel anytime.

Practise an Angular interview free →

See Cohesyve in action

Free 30-min walkthrough

See it on your role