Scenario Questions
S1. The page is slow when a list has 10,000 rows. What do you do?
- Use virtual scrolling (
cdk-virtual-scroll-viewport) or pagination - Use
trackwith a unique id - Use OnPush and signals
- Move filtering to the server if possible
- Profile with Angular DevTools
S2. Users see old data after saving. Why?
- The local state was not updated after the API call
- Cached response (check
shareReplayor the HTTP cache) - Fix: update the signal or call
resource.reload()after success
S3. Search sends a request for every keystroke. Fix it.
debounceTime waits for typing to pause, distinctUntilChanged skips repeats and switchMap cancels the old request.
S4. Two components must share a cart. How?
A root-provided service with signals (CartStore). Both inject it. No parent-child link is needed.
S5. A user opens a protected link while logged out. What should happen?
The guard redirects to /login?returnUrl=.... After login, navigate to the saved returnUrl.
S6. A token expires while the user works.
The interceptor sees 401, refreshes the token once (shared among parallel requests), retries the failed request, and logs out only if the refresh fails.
S7. Your first page takes too long to load.
- Run
ng buildand inspect bundle sizes - Lazy load routes,
@deferheavy widgets - Optimize images with
NgOptimizedImage - Use SSR or prerender for public pages
- Enable compression and caching on the server
S8. A memory leak makes the app slower over time.
Look for subscriptions never unsubscribed, listeners added with addEventListener, intervals and dynamic components not destroyed. Use takeUntilDestroyed, async pipe and DestroyRef.
Live Coding Tasks
Task 1: Reusable toggle button component
Task 2: Custom pipe that shortens text
Task 3: Fetch users and show loading, error, empty
Task 4: Form with password confirmation
Create a FormGroup with password and confirm, add a group validator that returns { passwordMismatch: true } when they differ, and show the message when the confirm field is touched.
Task 5: Debounced input directive
Portfolio Checklist
- 3 or 4 finished projects on GitHub with a clear README and live link
- One project with login, guards and role-based pages
- One project using a real API with search, paging and error handling
- Tests for at least services and key components
- Clean commit history, linting and consistent formatting
- Deployed with CI on GitHub Actions
Resume Tips
- List the Angular version and tools: TypeScript, RxJS, signals, Angular Material, NgRx, Jest/Vitest, Playwright
- Describe results: "reduced load time by 40% using lazy loading and @defer"
- Link your GitHub and live demos
- Keep it to one page for fresher roles
Learning Roadmap
| Stage | Learn | Build |
|---|---|---|
| 1. Foundations | HTML, CSS, JavaScript ES6+, Git | Static pages |
| 2. TypeScript | Types, interfaces, generics, classes | Small typed utilities |
| 3. Angular core | Components, templates, signals, services, routing | Todo app |
| 4. Data | Forms, HttpClient, RxJS, resources | Product catalog |
| 5. Real world | Auth, guards, interceptors, state, testing | Admin dashboard |
| 6. Advanced | Performance, SSR, zoneless, CI/CD | Deploy and optimize |
| 7. Extras | Angular Material, NgRx, Node or backend basics, Docker | Full-stack app |
Conclusion
Practice scenarios out loud, solve small coding tasks until they feel easy, build a few deployed projects and follow the roadmap step by step. Consistent practice is what gets you hired.

