Loading
Pick a focused question that fits your time, stack, and interview goal.
14 results across 1 active filter
Page 1 of 1
Explains labels, keyboard behavior, focus, semantic HTML, errors, color contrast, and accessible custom controls.
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 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.
Builds a risk-based frontend test strategy across unit, component, integration, contract, and end-to-end boundaries.
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.
Connects JavaScript tasks and microtasks to rendering, responsiveness, and practical performance fixes.
Explains practical frontend performance work: measuring, render cost, memoization, bundle splitting, images, and hydration.
Uses profiler evidence to isolate expensive derived data and row rendering, then applies memoization without hiding correctness bugs.
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 how Suspense boundaries stream useful page regions while coordinating loading, errors, and data ownership.