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 1 of 3
Traces buffering through the production artifact, proxy chain, compression, cache, platform adapter, and version consistency.
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.
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 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.
Uses field data, lab evidence, and release correlation to diagnose LCP, INP, and CLS regressions without guessing.
Explains how React error boundaries, route errors, safe fallbacks, logging, and recovery work together.
Moves non-deterministic browser-only rendering behind a stable server snapshot and post-hydration update.
Explains practical frontend performance work: measuring, render cost, memoization, bundle splitting, images, and hydration.
Explains stale edit detection, row versioning, conflict UI, refresh behavior, and safe update contracts.
Places segment and global boundaries deliberately, separates expected errors, and makes retries observable and safe.
Explains named slots, retained active state, hard-navigation fallbacks, and the required default files in Next.js 16.