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.
67 results across 1 active filter
Page 1 of 3
Explains labels, keyboard behavior, focus, semantic HTML, errors, color contrast, and accessible custom controls.
Explains when to derive values during render instead of storing duplicate state that can drift.
Explains URL-backed filters, API query parameters, pagination, sorting, empty states, and shareable list views.
Implements labeled fields, client validation, error summaries, focus recovery, and pending submission state.
Explains admin list/edit/delete workflows with capability checks, audit events, confirmation, validation, and recovery.
Builds a route-level Next.js failure UI with safe reporting, retry, and an escape route while keeping expected errors out of the boundary.
Explains permission-aware navigation, guarded routes, server authorization, stale capabilities, and safe 401/403 handling.
Models file validation, progress, cancellation, failure, and retry without losing the selected file.
Explains caching and revalidation choices for static, dynamic, user-specific, and frequently changing data.
Explains when optimistic UI is worth it, when to wait for server confirmation, and how to recover from rejected mutations.
Places state according to who owns it, how long it must live, and whether the URL or server is the source of truth.
Explains cleanup for subscriptions, timers, event listeners, and aborting stale fetches.
Explains loading, error, empty, success, refetch, stale data, and request lifecycle in client-rendered React.
Explains controlled inputs, uncontrolled inputs, validation, refs, and when each form approach fits.
Combines debounce cleanup, AbortController, and request identity to prevent stale search results.
Explains a practical debugging path across browser, Next.js layer, API, logs, database, and deployment changes.
Explains why server HTML and client render can disagree, how to debug it, and how to avoid mismatch-prone code.
Explains a constraint-first approach to responsive layout, intrinsic sizing, overflow, and content resilience.
Explains how to design DTOs, response shapes, UI needs, API compatibility, and frontend/backend ownership for a feature.
Builds a risk-based frontend test strategy across unit, component, integration, contract, and end-to-end boundaries.
Explains how client-side validation, server-side validation, DTOs, domain rules, and user feedback work together.
Explains practical UI states for data fetching, empty results, partial failure, retry, and accessible recovery.
Explains list/detail API boundaries, route state, prefetching, selected item behavior, and avoiding over-fetching.
Explains how to split components around ownership, reuse, readability, state, and API-like prop contracts.