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.
65 results across 1 active filter
Page 2 of 3
Chooses tag and path invalidation based on data identity, consistency requirements, and affected route surfaces.
Chooses runtime from dependency, data locality, feature, latency, and deployment constraints instead of fashion.
Combines a canonical detail page with an intercepted modal, Parallel Route slot, browser history, and accessible dismissal.
Builds titles, descriptions, canonicals, Open Graph data, and not-found behavior from the same canonical page record.
Combines server and client instrumentation, OpenTelemetry, post-response work, correlation, and privacy-aware signals.
Uses semantic forms, action state, pending feedback, server validation, focus behavior, and progressive enhancement.
Treats actions as public mutation endpoints with server validation, fresh authorization, idempotency, transactions, and safe errors.
Uses route groups for organization and layout boundaries while accounting for URL collisions and full reloads across roots.
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.
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.
Explains token storage, cookies, XSS, CSRF, and why browser UI never replaces server authorization.
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.