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 5 of 7
Uses discriminated unions to represent valid UI states and make transitions exhaustive.
Guards a mutation immediately, exposes pending state, and restores the command after failure.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Builds a typed functional canDeactivate guard and editor contract that protects dirty work until a save has actually succeeded.
Explains token storage, cookies, XSS, CSRF, and why browser UI never replaces server authorization.
Uses fake time and HttpTestingController to complete requests out of order and prove latest-query state, recovery, and teardown.
Explains stale closures in callbacks, effects, timers, subscriptions, and how to fix them cleanly.
Uses profiler evidence to isolate expensive derived data and row rendering, then applies memoization without hiding correctness bugs.
Explains compatible full-stack deployment, backend enforcement, staged rollout, telemetry, safe disablement, rollback decisions, and flag cleanup.
Uses server-resolved capabilities for presentation while keeping the mutation endpoint authoritative.
Uses an explicit state model for initial loading, success, empty, recoverable error, and refetching.
Explains Next.js server/client component boundaries, interactivity, data access, serialization, and bundle impact.
Keeps data and secrets on the server while sending a small serializable model to an interactive client component.
Explains server rendering, client rendering, static rendering, freshness, SEO, personalization, and performance trade-offs.
Explains asynchronous-looking state updates, batching, functional setters, and avoiding stale values.
Wraps widget creation, listeners, observers, timers, and destruction in one lifecycle boundary and verifies repeated navigation does not accumulate resources.
Makes list filters shareable and back-button friendly while resetting pagination deliberately.
Tests validation, focus, pending state, and the save contract through accessible user interactions rather than component internals.
Tests one browser-to-database practice workflow with isolated fixtures, resilient locators, durable assertions, and reliable cleanup.
Tests input replacement, DOM events, computed rendering, and stable identity without forcing change detection around missing notifications.
Explains component tests that assert user-visible behavior instead of implementation details.
Explains tracing one user action across browser, frontend server, API, dependencies, logs, metrics, and safe diagnostics.
Explains when a Next.js route layer helps with cookies, tokens, aggregation, and UI-specific API adaptation.
Explains when a reducer clarifies related state transitions and when independent state remains simpler.