Loading
Pick a focused question that fits your time, stack, and interview goal.
19 results across 1 active filter
Page 1 of 1
Explains URL-backed filters, API query parameters, pagination, sorting, empty states, and shareable list views.
Explains admin list/edit/delete workflows with capability checks, audit events, confirmation, validation, and recovery.
Explains permission-aware navigation, guarded routes, server authorization, stale capabilities, and safe 401/403 handling.
Explains when optimistic UI is worth it, when to wait for server confirmation, and how to recover from rejected mutations.
Explains a practical debugging path across browser, Next.js layer, API, logs, database, and deployment changes.
Explains how to design DTOs, response shapes, UI needs, API compatibility, and frontend/backend ownership for a feature.
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 stale edit detection, row versioning, conflict UI, refresh behavior, and safe update contracts.
Explains upload UX, API boundaries, validation, progress, storage, scanning, failure handling, and safe download behavior.
Explains debounce, cancellation, stale-response protection, loading indicators, and backend query safety for search UI.
Explains refetching, targeted invalidation, stale data, optimistic updates, server truth, and user feedback after mutations.
Explains field-level and form-level error mapping from API responses into a usable frontend form experience.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Explains compatible full-stack deployment, backend enforcement, staged rollout, telemetry, safe disablement, rollback decisions, and flag cleanup.
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 how to choose an E2E flow, control test data, avoid brittleness, and cover frontend/API integration risk.