Question 1

How do you structure a large Angular monorepo app?

Accepted Answer

Feature folders with routes, shared UI lib, core singleton services, and clear public APIs. Use Nx or workspace libs. Avoid deep cross-feature imports. Lazy load features. Keep domain logic out of dumb components.

Question 2

Smart vs presentational components in Angular?

Accepted Answer

Smart containers fetch/orchestrate; presentational receive inputs and emit outputs. Presentational components are easier to test and reuse. Don't put HttpClient in every leaf component.

Question 3

When do you introduce a state library (NgRx, SignalStore) vs services?

Accepted Answer

Complex shared workflows, time-travel/debug needs, or many writers → store; simple feature state → signal services. Avoid premature NgRx. Signal-based stores often suffice. Consistency matters more than brand of store.

Question 4

How should API models differ from view models?

Accepted Answer

Map DTOs to UI-friendly models in an anti-corruption layer; don't bind raw API shapes everywhere. Protects UI from backend churn. Centralize adapters. Validate at boundaries.

Question 5

Design auth + feature modules for an enterprise Angular app.

Accepted Answer

Core auth service, interceptor, guards; features lazy-loaded; shared UI; environment config tokens. Centralize permissions. Prefer canMatch for role routes. Keep secrets off the client.

Question 6

What is the facade pattern in Angular feature design?

Accepted Answer

A facade service exposes a narrow API over multiple stores/APIs so components stay simple. Helps hide NgRx complexity. Don't create facades that become god objects—keep per feature.

Architecture Angular Interview Questions

Other Angular interview topics