Interviewers ask about Bootstrap when you maintain legacy apps, Laravel projects, or internal tools. Anchor answers in trade-offs—speed vs customization, bundle weight vs developer velocity—not nostalgia.
Important interview questions and answers
- Q: Bootstrap vs Tailwind?
A: Bootstrap ships opinionated components and jQuery-free JS plugins; Tailwind ships composable utilities and expects you to build or buy components. Bootstrap is faster for standard admin/marketing patterns; Tailwind fits highly custom product UI. - Q: What changed in Bootstrap 5?
A: Dropped jQuery dependency, added RTL helpers, utilities API, offcanvas, and later color modes in 5.3. Migration means checking custom JS that relied on jQuery plugins. - Q: How does the grid differ from CSS Grid?
A: Bootstrap’s grid is flexbox-based twelve-column with breakpoints; CSS Grid handles arbitrary two-dimensional tracks. Many apps use both—Bootstrap for page shell, CSS Grid for specific widgets. - Q: How do you customize without forking?
A: Override Sass variables before import, or override--bs-*CSS variables at runtime; avoid editing files innode_modules. - Q: Accessibility concerns with Bootstrap?
A: Components include baseline ARIA, but modals, dropdowns, and carousels still need correct markup, labels, and keyboard testing—do not treat widgets as plug-and-play accessible.
Self-check
- Explain Bootstrap’s JS dependency model in one sentence.
- Name one weakness of component frameworks and your mitigation.
- When would you recommend against adopting Bootstrap on a greenfield app?
Interview prep
- When would you avoid Bootstrap?
Highly custom design systems, email templates, or apps that need minimal CSS with no component opinions.
- How do you customize without fighting the framework?
Sass variables/maps, CSS variables in BS5, or override tokens—not endless
!importantwars.