Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
162 results across 1 active filter
Page 3 of 7
Explains context propagation, value identity, provider scope, domain separation, and measured optimization.
Uses generics to preserve relationships between types and constraints to express the operations an implementation requires.
Explains the notification paths Angular relies on and designs components that do not depend on incidental global checks.
Explains named slots, retained active state, hard-navigation fallbacks, and the required default files in Next.js 16.
Explains DOM relocation, React-tree event propagation, accessible modal focus, and layering constraints.
Chooses template-driven, typed reactive, or experimental Signal Forms based on workflow complexity and stability needs.
Chooses interfaces or aliases based on object contracts, unions, composition, declaration merging, and team consistency.
Chooses tag and path invalidation based on data identity, consistency requirements, and affected route surfaces.
Chooses runtime from dependency, data locality, feature, latency, and deployment constraints instead of fashion.
Uses input availability, rendering completion, cleanup, and SSR safety to choose lifecycle work deliberately.
Uses ownership, inputs, outputs, rendering responsibility, and dependency scope to define maintainable standalone components.
Profiles real interactions to separate excessive change detection, expensive component work, layout cost, and network delay before optimizing.
Uses version-ready notifications, user-safe reloads, cache policy, and deployment compatibility instead of activating mixed versions in place.
Uses production build output, explicit budgets, dependency analysis, and meaningful lazy boundaries instead of arbitrary size cuts.
Keeps server and client output compatible while isolating browser APIs, user state, and post-render integration.
Uses latest-request semantics, cancellation, identity checks, and explicit state transitions for changing inputs.
Overrides dependencies at the provider boundary while preserving the same injection scope and contract used in production.
Uses HttpTestingController to verify request semantics and return controlled responses without calling a real server.
Uses a real route configuration and RouterTestingHarness to verify URLs, rendered components, redirects, guards, and failures.
Controls virtual time and completion order to prove debounce, switching, retries, and teardown without sleeping in tests.
Exercises signal-based component contracts through Angular bindings and waits for scheduled rendering before asserting.
Separates interruptible background rendering from time-based event or request suppression.
Combines a canonical detail page with an intercepted modal, Parallel Route slot, browser history, and accessible dismissal.
Places validation at the right form level and manages asynchronous checks without races or noisy requests.