Concept questionMedium~7 minAngular DI, Routing, Forms & HTTP / 2 of 10

Interview question

When do you need an InjectionToken in Angular?

Uses runtime tokens for configuration and abstractions while distinguishing provider recipes and instance identity.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I use an InjectionToken for configuration, functions, interface-shaped abstractions, or other values that do not have a class token at runtime. useValue supplies an existing value, useFactory computes one, useClass asks Angular to create the specified class, and useExisting aliases another provider. The token object itself is the identity; its description string is only for debugging.

Full answer below

Practice focus

InjectionToken, `useValue`, `useFactory`, `useExisting`, `useClass`, interfaces, and runtime identity.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
TypeScript interfaces disappear at runtime, so Angular needs a real runtime token to resolve non-class dependencies.
I use an InjectionToken for configuration, functions, interface-shaped abstractions, or other values that do not have a class token at runtime. useValue supplies an existing value, useFactory computes one, useClass asks Angular to create the specified class, and useExisting aliases another provider. The token object itself is the identity; its description string is only for debugging.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
For example, an API configuration token can carry a typed base URL and timeout without importing environment globals throughout the application. I use useExisting when old and new tokens must resolve to the same instance; useClass would create a separate one. Factory providers fit runtime composition but should keep dependencies and side effects visible. Multi-providers are useful when several independent registrations contribute to one extension point.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I define tokens in a stable boundary package so libraries and applications share the exact same object reference. Defaults can be tree-shakable when provided through supported token or injectable configuration, while application configuration can override them intentionally. Configuration is validated near startup because TypeScript does not validate deployment values. Tests assert alias identity, override behavior, factory dependencies, and multi-provider ordering wherever order affects behavior.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Trying to inject a TypeScript interface directly.
Using useClass when the intent is to alias an existing instance.
Treating the token's description string as its identity.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Two packages create separate tokens with the same description.
Deployment configuration reaches features without validation.
A provider recipe creates duplicate stateful instances.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

Why can Angular not inject an interface?
How do useExisting and useClass differ?
When are multi-providers useful?

Continue the section

Next in Angular DI, Routing, Forms & HTTP: Lazy loading and preloading

Step 3 of 10

How would you design lazy loading and preloading in Angular routing?

Practice route

Read core answer Review checklist Follow-up prompts Track progress

Finished this drill?

Practice freely. Sign in only when you want to save completion, confidence, notes, or bookmarks.

New to Aporeon? Create account

Drill details

Human editorial direction

Aporeon is shaped by Aleksandar Tomovski, a software developer with experience on both sides of technical interviews. Content is reviewed for accuracy, natural spoken delivery, useful depth, and honest trade-offs.

About the creator Editorial standards

Was this drill useful?

Help improve the interview library.

Found this answer useful?

Say thanks with a standalone, one-time $5 contribution. No account required.

No subscription or perks.Choose another amount

Opening drill

Concept questionMedium~7 minAngular DI, Routing, Forms & HTTP / 2 of 10

Interview question

When do you need an InjectionToken in Angular?

Uses runtime tokens for configuration and abstractions while distinguishing provider recipes and instance identity.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

InjectionToken, `useValue`, `useFactory`, `useExisting`, `useClass`, interfaces, and runtime identity.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
TypeScript interfaces disappear at runtime, so Angular needs a real runtime token to resolve non-class dependencies.
I use an InjectionToken for configuration, functions, interface-shaped abstractions, or other values that do not have a class token at runtime. useValue supplies an existing value, useFactory computes one, useClass asks Angular to create the specified class, and useExisting aliases another provider. The token object itself is the identity; its description string is only for debugging.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
For example, an API configuration token can carry a typed base URL and timeout without importing environment globals throughout the application. I use useExisting when old and new tokens must resolve to the same instance; useClass would create a separate one. Factory providers fit runtime composition but should keep dependencies and side effects visible. Multi-providers are useful when several independent registrations contribute to one extension point.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I define tokens in a stable boundary package so libraries and applications share the exact same object reference. Defaults can be tree-shakable when provided through supported token or injectable configuration, while application configuration can override them intentionally. Configuration is validated near startup because TypeScript does not validate deployment values. Tests assert alias identity, override behavior, factory dependencies, and multi-provider ordering wherever order affects behavior.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Trying to inject a TypeScript interface directly.
Using useClass when the intent is to alias an existing instance.
Treating the token's description string as its identity.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Two packages create separate tokens with the same description.
Deployment configuration reaches features without validation.
A provider recipe creates duplicate stateful instances.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

Why can Angular not inject an interface?
How do useExisting and useClass differ?
When are multi-providers useful?

Continue the section

Next in Angular DI, Routing, Forms & HTTP: Lazy loading and preloading

Step 3 of 10

How would you design lazy loading and preloading in Angular routing?

When do you need an InjectionToken in Angular?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue the section

When do you need an InjectionToken in Angular?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue the section