Mention Angular CDK Component Harnesses. They provide a stable API to interact with component setups in tests, making your tests highly resilient to future DOM structural changes.
for complex asynchronous data streams (like web sockets or complex search debouncing) and for local UI state and synchronous derived data. 2. Change Detection Optimization (The "Jank" Killer)
"This dropped unnecessary change detection passes by over 85%, reducing CPU utilization on lower-end devices from 90% down to a stable 12%." decoded frontend angular interview hacking
Keep components clean. Leverage @defer and takeUntilDestroyed to protect runtime performance.
"Do you use change detection by default, or do you rely on the default strategy?" Mention Angular CDK Component Harnesses
Reply “Angular drills” and I’ll send them (or search inside this doc for them).
: Explain how Ahead-of-Time compilation helps catch template errors early, which is crucial for complex search UIs. "Do you use change detection by default, or
Interview Tip: Emphasize that OnPush relies on . If you mutate a property inside an object passed as an @Input() , the object reference remains the same, and OnPush will not trigger a view update. Manual Change Detection Control
You just demonstrated you understand the runtime implications, not just the syntax.