Loading
Pick a focused question that fits your time, stack, and interview goal.
52 results across 1 active filter
Page 1 of 3
Showing the Angular Frontend curriculum. Technology tags describe each drill's actual implementation context; shared drills can belong to more than one track.
Builds a debounced typeahead with latest-request semantics, local error recovery, explicit states, and lifecycle-safe subscription ownership.
Implements a reusable ControlValueAccessor with model-to-view updates, touch and disabled semantics, keyboard behavior, and validation-friendly accessibility.
Implements a functional interceptor that adds correlation metadata, records timing, and retries only explicitly safe transient requests.
Coordinates version-ready events, unsaved-work checks, deferred reload, failure reporting, and one prompt per version without unsafe in-place activation.
Builds writable and computed signal state for filtering and selection while preserving stable row identity and avoiding effect-driven derivation.
Builds an interaction-triggered deferrable view with a stable accessible placeholder and deterministic tests for placeholder, loading, error, and completion.
Repairs a stale view by bringing an external callback into explicit Angular state ownership without adding polling or global change detection.
Separates projected caller-owned content from a component's own view and explains when queries are justified.
Explains contextual sanitization and treats bypass APIs as narrow security-review decisions rather than general encoding helpers.
Connects environment and element injectors to instance lifetime, overrides, lazy routes, and accidental state isolation.
Explains the notification paths Angular relies on and designs components that do not depend on incidental global checks.
Chooses template-driven, typed reactive, or experimental Signal Forms based on workflow complexity and stability needs.
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.