Most developers say they “know” Angular. But real understanding starts here: • Why does ngOnChanges() execute before ngOnInit()? • Why does setTimeout(0) still wait in JavaScript? • If Observables in RxJS are lazy, how does the async pipe work? • Why were Signals introduced when RxJS already exists? These aren’t syntax questions. They test: ✔ Execution flow ✔ Change detection ✔ Browser internals ✔ Reactive thinking Most developers learn features. Top developers understand how things actually work under the hood. That difference decides: – Who clears interviews – Who gets stuck at mid-level – Who moves toward senior roles I share deep Angular & frontend interview breakdowns — practical, real, and experience-driven. If you’re serious about becoming top 10% frontend developer, stay connected. #Angular #Frontend #JavaScript #InterviewPreparation #Signals #RxJS
Absolutely! Understanding change detection, async pipe behavior, and RxJS execution flow is what separates senior Angular developers from the rest critical for scalable apps
If we use @Input() property to get some data from Parent Component it is mandatory to use ngOnChanges(), it executes once while app loads, it has SimpleChanges Object that validate this Input data before component starts but if ngOnInit() ran first, the data from parent will be undefined. So to get and use that parent data properly we need to use ngOnChanges() method. ngOnInit() will work well when we need to do some logics of this @Input() data and to call API because at this time componet is initialised or started.