Technical screening questions
Ask for one example per question and listen for specifics.
- What is the difference between a Subject and a BehaviorSubject? A good answer: BehaviorSubject holds a current value and replays it to new subscribers.
- How do you avoid memory leaks with subscriptions? A good answer: async pipe, takeUntil or unsubscribing in ngOnDestroy.
- What are change detection strategies? A good answer: Default vs OnPush and when OnPush helps.
- How do you structure lazy-loaded modules? A good answer: Feature modules, route-level lazy loading and shared modules.
- How do you upgrade across major Angular versions? A good answer: ng update, reading breaking changes and testing in steps.
Quick screening questions
Use these when you have only a few minutes.
- Which Angular version are you on and how did you upgrade?
- How do you manage subscriptions to avoid memory leaks?
- When do you use NgRx versus services?
What separates the levels
Match the level to the requirement before you submit.
- Junior: builds components from specs.
- Mid: owns modules, state and tests.
- Senior: defines architecture and upgrade strategy.
Red flags
Any of these is a reason to probe further.
- AngularJS experience presented as Angular.
- Cannot explain RxJS operators.
- Never upgraded a version.
Tools you should hear mentioned
An Angular developer with real experience usually names several of these without prompting.
- Angular CLI
- RxJS
- TypeScript
- NgRx
- Angular Material
- Jasmine or Jest
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should an Angular developer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.