Loading
Pick a focused question that fits your time, stack, and interview goal.
59 results across 1 active filter
Page 1 of 3
Explains labels, keyboard behavior, focus, semantic HTML, errors, color contrast, and accessible custom controls.
Debugs matched rules, cascade origin, importance, layers, specificity, source order, inheritance, and computed values.
Traces buffering through the production artifact, proxy chain, compression, cache, platform adapter, and version consistency.
Diagnoses forced synchronous layout from interleaved geometry reads and style writes, then batches work and reduces its scope.
Traces synchronous throws and promise rejections through chains, awaits, missing returns, and detached work.
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.
Places segment and global boundaries deliberately, separates expected errors, and makes retries observable and safe.
Explains DOM and CSSOM construction, style, layout, paint, and compositing as a practical performance model.
Explains the notification paths Angular relies on and designs components that do not depend on incidental global checks.
Chooses runtime from dependency, data locality, feature, latency, and deployment constraints instead of fashion.
Uses input availability, rendering completion, cleanup, and SSR safety to choose lifecycle work deliberately.
Profiles real interactions to separate excessive change detection, expensive component work, layout cost, and network delay before optimizing.
Uses version-ready notifications, user-safe reloads, cache policy, and deployment compatibility instead of activating mixed versions in place.
Uses production build output, explicit budgets, dependency analysis, and meaningful lazy boundaries instead of arbitrary size cuts.
Overrides dependencies at the provider boundary while preserving the same injection scope and contract used in production.
Uses HttpTestingController to verify request semantics and return controlled responses without calling a real server.
Uses a real route configuration and RouterTestingHarness to verify URLs, rendered components, redirects, guards, and failures.