Tailwind, Bootstrap, and traditional CSS represent three different philosophies. The interviewer wants to see you understand the trade-offs, not just parrot "Tailwind good."

The three philosophies

• Traditional CSS — you write rules in stylesheets. Maximum control; global scope, naming burden, specificity wars, and dead-code accumulation at scale.
• Bootstrap — component-first — pre-built components (.btn, .card, .navbar) and a grid. Fast to ship a generic UI.
• Tailwind — utility-first — atomic single-purpose classes (flex, pt-4, text-sm) composed directly in markup.

Why teams pick Tailwind

1. Tiny production bundle. Tailwind scans your files and generates only the utilities you actually use — final CSS is often a few KB. Bootstrap ships its whole stylesheet unless you customize the build; traditional CSS only ever grows.

2. Design consistency by construction. Tailwind's tailwind.config is your design-token system — spacing, colors, type scale. You can only use values from the scale, so the UI stays consistent without discipline. It's a design system with guardrails.

3. No naming, no context-switching. No inventing .card-header-title-wrapper, no jumping between files. Styles live with the markup.

4. Design freedom. Unlike Bootstrap, Tailwind has no opinion on how things look — you're not fighting a framework's defaults, and your site doesn't look like every other Bootstrap site.

5. Easy to delete. Remove the markup, the styles go with it. No orphaned CSS.

The honest downsides

• Verbose markup — long className strings. Mitigated by extracting components (the right unit of reuse) and @apply sparingly.
• Learning curve — you must learn the utility names.
• Not great for highly dynamic, computed styles — sometimes you still need a style attribute or CSS-in-JS for truly dynamic values.
• It's still just CSS — it doesn't solve everything, and "ugly HTML" is a real complaint.

When Bootstrap still makes sense

Internal tools, prototypes, MVPs, or teams that want a generic, ready-made UI fast and don't need a custom brand. Bootstrap's pre-built components are genuinely faster when you don't care about uniqueness.

When traditional CSS is fine

Small sites, or large apps that pair it with a scoping strategy (CSS Modules) and conventions (BEM).

Senior framing

The senior answer reframes it: Tailwind's real value is being a constrained, purgeable, config-driven design system, not "fewer files." It trades verbose markup for consistency, tiny bundles, and deletability. And it's not universally right — for a quick generic admin panel, Bootstrap wins; for a branded product at scale with a team, Tailwind's guardrails win. Showing you'd choose based on context, not hype, is the signal.