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.
47 results across 1 active filter
Page 2 of 2
Explains refetching, targeted invalidation, stale data, optimistic updates, server truth, and user feedback after mutations.
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.
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.
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 route handlers as a frontend server boundary for cookies, API adaptation, auth, and backend calls.
Explains how Suspense boundaries stream useful page regions while coordinating loading, errors, and data ownership.
Explains how to choose an E2E flow, control test data, avoid brittleness, and cover frontend/API integration risk.