Tailwind is not a component library like Bootstrap cards or Material buttons. It is a low-level styling system: thousands of tiny utilities generated from a shared theme (spacing scale, palette, breakpoints).
Compared to writing CSS files
Traditional CSS: create .hero-title, move to a file, name conflicts, debate BEM. Tailwind: put text-3xl font-bold tracking-tight on the element. Extraction happens when patterns repeat—not on the first draft.
Important interview questions and answers
- Q: What problem does Tailwind solve?
A: It standardizes micro-decisions (spacing, type scale, breakpoints) so teams ship consistent UI faster with less bespoke CSS. - Q: Is Tailwind inline styles?
A: No. Classes still go through stylesheets (generated at build time). You get design tokens and responsive/state variants that inline styles lack. - Q: When would you avoid Tailwind?
A: Email templates, strict CMS constraints, or teams without a build step who cannot purge unused CSS—though CDN works for prototypes.
Self-check
- Name one thing Tailwind gives you that raw inline
style=""does not. - How is Tailwind different from Bootstrap’s pre-built components?