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 4 of 7
Balances route ownership, initial bundle cost, likely navigation, authorization, and measurable user experience.
Repairs unstable Hook order caused by branches, early returns, callbacks, loops, or exception paths.
Uses repeatable navigation, heap evidence, retained-object paths, and ownership checks to find subscriptions, listeners, and DOM retained past teardown.
Moves from a reproducible user interaction to render evidence, root cause, proportional repair, and field validation.
Places each risk at the cheapest reliable test boundary and keeps a small set of browser journeys for integration confidence.
Builds titles, descriptions, canonicals, Open Graph data, and not-found behavior from the same canonical page record.
Combines safe bindings, AOT, dependency discipline, CSP, Trusted Types, and reporting without treating one control as a complete defense.
Combines server and client instrumentation, OpenTelemetry, post-response work, correlation, and privacy-aware signals.
Owns a third-party widget through a DOM ref, effect lifecycle, minimal updates, and complete teardown.
Models pending, validation, success, retry, and authoritative server outcomes around a React 19 form Action.
Uses semantic forms, action state, pending feedback, server validation, focus behavior, and progressive enhancement.
Splits meaningful code, keeps stable UI visible, preloads likely paths, and pairs loading with error recovery.
Uses supported version steps, ng update migrations, dependency compatibility, targeted cleanup, and staged production evidence.
Treats actions as public mutation endpoints with server validation, fresh authorization, idempotency, transactions, and safe errors.
Combines semantic queries, keyboard interaction, focus assertions, and automated checks while retaining manual assistive-technology review.
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.