Advanced: Scale & Migration
advanced: scale & migration scale & migration — 25 interview questions with traps, follow-ups, and production context. practice out loud;
Introduction
Scale & Migration — 25 interview questions with traps, follow-ups, and production context. Practice out loud; staff loops reward trade-offs, not definitions.
Business problem
Business pressure: Product teams need Scale & Migration interview questions to ship polished UI without layout regressions, accessibility lawsuits, or LCP regressions that hurt conversion.
- Conversion: Visual polish and performance directly affect checkout and signup funnels.
- Brand: Inconsistent Scale & Migration interview questions implementation fragments design system trust.
- Velocity: CSS debt slows every feature team — architecture matters at scale.
Why this feature exists
Platform history: CSS evolved Scale & Migration interview questions to solve author needs without JavaScript layout engines or table hacks.
- Problem solved: Declarative styling separated from document structure.
- Rejected alternative: Inline styles and JS layout — unmaintainable at enterprise scale.
Browser rendering perspective
Rendering impact: Scale & Migration interview questions affects style recalculation, layout, paint, and composite stages in the browser pipeline.
- Chrome (Blink): Style → LayoutNG → Paint → Viz compositor.
- Firefox (Gecko): Servo-based stylo + WebRender compositing.
- Safari (WebKit): WebKit style resolver + GPU layer promotion rules.
Internal browser workflow
Workflow: Selector match → cascade → computed values → layout tree → paint layers → composite.
Real production example
Production: Netflix, Amazon, and Shopify enforce Scale & Migration interview questions patterns via design tokens, lint rules, and visual regression CI.
Enterprise use case
Enterprise: Design systems (Polaris, Carbon, Atlassian) codify Scale & Migration interview questions in token pipelines and component APIs.
Accessibility considerations
A11y: CSS must not remove focus visibility, break zoom, or convey state by color alone (WCAG 2.2).
Performance considerations
Performance: Scale & Migration interview questions can trigger reflow, expensive selectors, or layer explosion — profile with DevTools Performance panel.
SEO considerations
SEO: CSS affects LCP, CLS, and mobile usability — ranking signals tied to Core Web Vitals.
Scalability considerations
Scale: Scale & Migration interview questions choices compound across micro-frontends, white-label tenants, and dark-mode variants.
Common production issues
Production failures: Specificity wars, z-index stacks, and responsive breakpoints that work in Chrome but break Safari.
Debugging guide
Debug: Chrome DevTools → Elements (computed styles), Layout panel, Rendering layers, Coverage for unused CSS.
Interview questions
Advanced — Scale & Migration: micro-frontend CSS?(Advanced)
Deep answer on micro-frontend CSS: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 1: How would Netflix/Amazon CSS platform handle micro-frontend CSS?
Advanced — Scale & Migration: token npm package?(Advanced)
Deep answer on token npm package: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 2: How would Netflix/Amazon CSS platform handle token npm package?
Advanced — Scale & Migration: stylelint org-wide?(Advanced)
Deep answer on stylelint org-wide: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 3: How would Netflix/Amazon CSS platform handle stylelint org-wide?
Advanced — Scale & Migration: visual regression scale?(Advanced)
Deep answer on visual regression scale: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 4: How would Netflix/Amazon CSS platform handle visual regression scale?
Advanced — Scale & Migration: CSS migration codemods?(Advanced)
Deep answer on CSS migration codemods: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 5: How would Netflix/Amazon CSS platform handle CSS migration codemods?
Advanced — Scale & Migration: deprecated token aliases?(Advanced)
Deep answer on deprecated token aliases: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 6: How would Netflix/Amazon CSS platform handle deprecated token aliases?
Advanced — Scale & Migration: specificity debt paydown?(Advanced)
Deep answer on specificity debt paydown: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 7: How would Netflix/Amazon CSS platform handle specificity debt paydown?
Advanced — Scale & Migration: global CSS strangler?(Advanced)
Deep answer on global CSS strangler: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 8: How would Netflix/Amazon CSS platform handle global CSS strangler?
Advanced — Scale & Migration: CSS bundle per pod?(Advanced)
Deep answer on CSS bundle per pod: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 9: How would Netflix/Amazon CSS platform handle CSS bundle per pod?
Advanced — Scale & Migration: CDN cache CSS fingerprint?(Advanced)
Deep answer on CDN cache CSS fingerprint: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 10: How would Netflix/Amazon CSS platform handle CDN cache CSS fingerprint?
Advanced — Scale & Migration: A/B CSS experiments?(Advanced)
Deep answer on A/B CSS experiments: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 11: How would Netflix/Amazon CSS platform handle A/B CSS experiments?
Advanced — Scale & Migration: white-label tenant tokens?(Advanced)
Deep answer on white-label tenant tokens: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 12: How would Netflix/Amazon CSS platform handle white-label tenant tokens?
Advanced — Scale & Migration: design system semver?(Advanced)
Deep answer on design system semver: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 13: How would Netflix/Amazon CSS platform handle design system semver?
Advanced — Scale & Migration: platform z-index doc?(Advanced)
Deep answer on platform z-index doc: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 14: How would Netflix/Amazon CSS platform handle platform z-index doc?
Advanced — Scale & Migration: cross-team RFC CSS?(Advanced)
Deep answer on cross-team RFC CSS: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 15: How would Netflix/Amazon CSS platform handle cross-team RFC CSS?
Advanced — Scale & Migration: shadow DOM isolation?(Advanced)
Deep answer on shadow DOM isolation: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 16: How would Netflix/Amazon CSS platform handle shadow DOM isolation?
Advanced — Scale & Migration: CSS in JS at scale?(Advanced)
Deep answer on CSS in JS at scale: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 17: How would Netflix/Amazon CSS platform handle CSS in JS at scale?
Advanced — Scale & Migration: Tailwind at enterprise?(Advanced)
Deep answer on Tailwind at enterprise: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 18: How would Netflix/Amazon CSS platform handle Tailwind at enterprise?
Advanced — Scale & Migration: legacy IE drop migration?(Advanced)
Deep answer on legacy IE drop migration: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 19: How would Netflix/Amazon CSS platform handle legacy IE drop migration?
Advanced — Scale & Migration: Safari rollout testing?(Advanced)
Deep answer on Safari rollout testing: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 20: How would Netflix/Amazon CSS platform handle Safari rollout testing?
Advanced — Scale & Migration: CSS on-call incidents?(Advanced)
Deep answer on CSS on-call incidents: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 21: How would Netflix/Amazon CSS platform handle CSS on-call incidents?
Advanced — Scale & Migration: rollback CSS bundle?(Advanced)
Deep answer on rollback CSS bundle: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 22: How would Netflix/Amazon CSS platform handle rollback CSS bundle?
Advanced — Scale & Migration: scale interview trap rewrite?(Advanced)
Deep answer on scale interview trap rewrite: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 23: How would Netflix/Amazon CSS platform handle scale interview trap rewrite?
Advanced — Scale & Migration: 100 engineer CSS governance?(Advanced)
Deep answer on 100 engineer CSS governance: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 24: How would Netflix/Amazon CSS platform handle 100 engineer CSS governance?
Advanced — Scale & Migration: CSS platform team KPIs?(Advanced)
Deep answer on CSS platform team KPIs: connect browser pipeline, measurable CWV/a11y impact, and production rollback strategy. Interview trap: defining feature without failure mode — always state what breaks at scale (Safari, TV, 10k DOM, tenant themes).
Follow-up: Drill 25: How would Netflix/Amazon CSS platform handle CSS platform team KPIs?
Hands-on exercise
Mock interview drill: Answer all 25 questions out loud in 45 minutes. Record yourself explaining trade-offs, not just definitions.
Try it yourself
Edit the CSS panel — the preview updates live. Use DevTools Performance and Accessibility panels to validate.