▸case-16 The codebase contains over 50 stale UI feature flags guarding legacy components, confusing new engineers and cluttering templates. What process should the team implement for feature flag lifecycle management? | pass→pass | 13,979 | 16,408 | +17% | 1 | 1 | 0% | 2,318 | 2,790 | +20% | 0 | 0 | — |
▸case-01 Our 12-person UI engineering team is refactoring a monolith into a shared component library. The team is debating whether design tokens (colors, typography, spacing primitives) should be owned and modified directly by individual feature squads or maintained by a dedicated design system core squad. We want to avoid token duplication while allowing fast feature iteration. How should design token governance be structured? | pass→pass | 17,725 | 14,612 | -18% | 1 | 1 | 0% | 3,059 | 2,535 | -17% | 0 | 0 | — |
▸case-02 During a major design system overhaul, screen reader compatibility and keyboard navigation compliance are failing across multiple team PRs. Should accessibility testing be assigned exclusively to a specialized QA engineer right before release, or integrated into the component developer definition of done? | pass→pass | 11,669 | 13,670 | +17% | 1 | 1 | 0% | 1,888 | 2,172 | +15% | 0 | 0 | — |
▸case-03 Our frontend developers report frequent CI pipeline failures due to pixel-diff threshold mismatches across operating systems in visual regression tests. Should visual regression screenshot generation run locally on developer laptops or in a standardized containerized CI environment? | pass→pass | 13,028 | 12,751 | -2% | 1 | 1 | 0% | 2,095 | 2,183 | +4% | 0 | 0 | — |
▸case-22 Our backend service experiences memory exhaustion in Redis due to high key churn. Which cache eviction policy and TTL strategy should the backend service team implement for session data? | pass→pass | 19,347 | 14,062 | -27% | 1 | 1 | 0% | 2,507 | 2,270 | -9% | 0 | 0 | — |
▸case-04 A core UI component squad needs to deprecate a prop across a multi-repo organization using the shared library. Should the team publish a breaking major release immediately or use a multi-phase deprecation strategy with warnings and codemods? | pass→pass | 12,005 | 11,449 | -5% | 1 | 1 | 0% | 1,995 | 1,992 | -0% | 0 | 0 | — |
▸case-05 Four independent frontend squads build distinct micro-frontend apps for the same portal. Squad A wants to embed its own copy of the CSS framework to move faster, while Squad B suggests bundling a single shared design system artifact at runtime. Which approach balances bundle isolation and visual consistency? | pass→pass | 10,716 | 14,208 | +33% | 1 | 1 | 0% | 1,933 | 2,285 | +18% | 0 | 0 | — |
▸case-06 Developers on the UI team are storing server responses, form input states, and sidebar toggle flags all within a single global Redux store. How should the team divide state ownership between server cache, local component state, and global UI state? | pass→pass | 12,242 | 11,943 | -2% | 1 | 1 | 0% | 2,194 | 2,415 | +10% | 0 | 0 | — |
▸case-07 A product designer provides Figma frames for a complex multi-step checkout form. Developers keep misinterpreting interactive states like hover, focus, disabled, and error. What structured artifact should the UI orchestration workflow require before development begins? | pass→pass | 10,430 | 10,617 | +2% | 1 | 1 | 0% | 1,671 | 1,821 | +9% | 0 | 0 | — |
▸case-08 Feature teams regularly add third-party animation and charting packages that inflate JavaScript bundle sizes. How should team leads automatically enforce bundle size limits in the pull request workflow? | pass→pass | 13,771 | 16,888 | +23% | 1 | 1 | 0% | 2,695 | 2,886 | +7% | 0 | 0 | — |
▸case-09 Our component library has low adoption because developers do not know how to configure story variations or prop combinations. Should documentation be written by a dedicated technical writer after release or authored by the UI engineer alongside the component? | pass→pass | 14,041 | 14,881 | +6% | 1 | 1 | 0% | 2,199 | 2,159 | -2% | 0 | 0 | — |
▸case-10 The team spends excessive developer hours manually verifying complex UI flows across Safari, Chrome, Firefox, and mobile viewports. How should cross-browser verification duties be allocated between automated matrix testing and manual review? | pass→pass | 14,513 | 19,666 | +36% | 1 | 1 | 0% | 2,173 | 2,644 | +22% | 0 | 0 | — |
▸case-11 Pull requests for shared UI components are frequently blocked waiting for senior team members to review styling choices. How should code review responsibilities be distributed across junior and senior engineers? | fail→pass | 14,212 | 15,459 | +9% | 1 | 1 | 0% | 2,282 | 2,327 | +2% | 0 | 0 | — |
▸case-12 UI engineers are hardcoding copy strings in React components and manually passing JSON translation files to localization agencies late in the sprint. How should the i18n extraction and translation synchronization workflow be structured? | pass→pass | 16,031 | 18,751 | +17% | 1 | 1 | 0% | 2,729 | 3,247 | +19% | 0 | 0 | — |
▸case-13 Multiple squads on the web portal write custom CSS classes in global stylesheets, leading to unexpected styling overrides and high specificity collisions. What styling methodology or architecture rule should the team enforce? | pass→pass | 12,660 | 13,305 | +5% | 1 | 1 | 0% | 2,101 | 2,202 | +5% | 0 | 0 | — |
▸case-14 Engineers are writing fragile unit tests that assert against internal DOM element structures and private class names. What testing boundary principle should the UI team adopt for testing components? | pass→pass | 10,523 | 13,563 | +29% | 1 | 1 | 0% | 1,787 | 1,894 | +6% | 0 | 0 | — |
▸case-15 Different engineers are adding arbitrary custom media query pixel values like `@media (max-width: 843px)` across feature CSS files. How should media queries be governed across the team? | pass→pass | 13,994 | 14,635 | +5% | 1 | 1 | 0% | 2,449 | 2,579 | +5% | 0 | 0 | — |
▸case-17 Our organization hosts 20 internal UI packages in a monorepo. Engineers disagree on whether to update all package versions simultaneously (fixed/lockstep versioning) or allow independent semantic versioning per package. Which strategy minimizes dependency churn for UI consumers? | fail→pass | 15,359 | 16,609 | +8% | 1 | 1 | 0% | 2,639 | 2,742 | +4% | 0 | 0 | — |
▸case-18 Feature developers are adding inline conditionals like `isDark ? '#1a1a1a' : '#ffffff'` inside visual components to support dark mode. How should the team architect theme switching across components? | pass→pass | 18,288 | 14,737 | -19% | 1 | 1 | 0% | 2,965 | 2,824 | -5% | 0 | 0 | — |
▸case-19 Feature squads hesitate to contribute new components back to the shared UI library because contributions take weeks to be reviewed. What SLA or intake mechanism should the UI orchestration team put in place? | fail→pass | 14,129 | 16,473 | +17% | 1 | 1 | 0% | 2,238 | 2,252 | +1% | 0 | 0 | — |
▸case-20 Our relational database queries on user orders are causing high CPU spikes during peak traffic. How should the database engineering team structure composite indexes on the orders table for fast lookup by tenant and date? | pass→pass | 15,123 | 13,431 | -11% | 1 | 1 | 0% | 2,727 | 2,541 | -7% | 0 | 0 | — |
▸case-21 The infrastructure team needs to configure routing rules on an NGINX Ingress Controller to manage SSL termination and weighted traffic splitting for canary deployments. What configuration directives should be added to the Ingress manifest? | pass→pass | 11,058 | 10,205 | -8% | 1 | 1 | 0% | 2,198 | 2,204 | +0% | 0 | 0 | — |