Be ready to discuss Tailwind trade-offs with engineers who prefer CSS modules, Styled Components, or vanilla extract. Anchor answers in consistency, purge, and team velocity—not hype.
Important interview questions and answers
- Q: Tailwind vs CSS Modules?
A: Tailwind colocates styling as classes with design tokens; CSS Modules colocate scoped selectors in files. Tailwind optimizes for utility composition; Modules for traditional rule authoring. - Q: How do you prevent huge HTML class strings?
A: Extract components, use multi-line formatting, @apply sparingly for primitives, and enforce review guidelines. - Q: How does purge/content configuration work?
A: Tailwind scans configured globs for class strings and emits only matching utilities, keeping production CSS small. - Q: When would you reach for arbitrary values?
A: One-off design specs not in the scale; promote repeats to theme tokens. - Q: How does Tailwind relate to utility-first concepts?
A: Same mindset as atomic utility layers—see our Utility CSS interview track for parallel vocabulary withtu-classes.
Self-check
- Explain purge/content in one sentence out loud.
- Name one weakness of utility-first markup and your mitigation.
Interview prep
- How do you keep Tailwind bundle size sane?
Correct
contentglobs, avoid dynamic class concatenation, use design tokens, and verify CSS output in CI.- Name a common accessibility mistake with utilities.
Removing focus outlines or low-contrast
text-*onbg-*pairs without checking WCAG.