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.
176 results across 1 active filter
Page 5 of 8
Tests user-observable urgent, pending, success, failure, interruption, and out-of-order behavior without scheduler coupling.
Uses route groups for organization and layout boundaries while accounting for URL collisions and full reloads across roots.
Designs optimistic identity, pending state, reconciliation, rollback, and overlapping mutation behavior.
Explains upload UX, API boundaries, validation, progress, storage, scanning, failure handling, and safe download behavior.
Applies an immediate reversible mutation, blocks overlapping writes, and restores the previous state on failure.
Explains debounce, cancellation, stale-response protection, loading indicators, and backend query safety for search UI.
Maps a stable ProblemDetails validation contract to fields and a fallback form-level error.
Explains field-level and form-level error mapping from API responses into a usable frontend form experience.
Explains when filters, sorting, pagination, and selection belong in search parameters and how to keep navigation predictable.
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.
Diagnoses incompatible cached HTML and immutable assets across CDN, browser, service-worker, and rollout boundaries.
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.