Tell me about an Angular application you have worked on. How was it structured and what would you change?

Note: Angular interviews lean heavily on architecture, because Angular is chosen precisely for large applications. Talk about structure, not features.

Cover these:

• Scale and shape. Roughly how many components, routes, and developers. An application with three developers and one with thirty have completely different problems.
• How it was organised. Feature modules or standalone components, a shared or core module, lazy-loaded routes, and where state lived — services with RxJS subjects, NgRx, or component state.
• The hardest problem. Good ones: initial bundle size, change detection performance on a large table, a state management approach that grew unmanageable, or migrating across major versions.
• What you would change. This is where you show judgement. Common honest answers are that NgRx was too much for the problem, or that shared modules turned into a dumping ground.