They track dependencies automatically using a producer-consumer graph.

private destroy$ = new Subject<void>();

The legacy standard pattern. You maintain a destroy$ subject and trigger it inside ngOnDestroy . The Shift to Angular Signals

Angular 16+ introduced Signals, and later versions pushed the framework toward a completely Zoneless future. This is highly relevant in modern interviews.

Be ready to discuss the shift toward standalone components and why you might still use NgModules in legacy or specific architectural patterns.

The @defer block allows developers to lazily load components, directives, and pipes based on specific runtime triggers. This drastically optimizes initial page load metrics like Largest Contentful Paint (LCP).

“Zone.js monkey-patches async APIs. If a third-party lib updates outside Angular, you’d use runOutsideAngular() and manually trigger change detection.”

Whether the role targets or hands-on feature development

| Concept | Quick hack | |---------|-------------| | ng-template vs ng-container | ng-container doesn’t create DOM element; ng-template needs ngTemplateOutlet | | ngDoCheck | Rarely use — performance killer | | APP_INITIALIZER | Run code before app loads (config, auth) | | Injector | Manual DI for dynamic components | | @ViewChild static flag | static: true for ngOnInit, false for AfterViewInit | | Renderer2 | Safe DOM manipulation (better than ElementRef.nativeElement ) |

Signals are exceptional for local, component-level state and lightweight global synchronization. NgRx shines in massive enterprise setups requiring strict state predictability, action tracking, time-travel debugging, and audit trails.

reduces the check cycles by only triggering when input references change or an event occurs within the component. The Performance Trio: Aim to mention the combination of