Typical blocking gates are type checking, lint, unit and component tests, a production build and a bundle size budget. Accessibility scans and end to end tests run on the pull request too, blocking on the critical journeys only. Anything advisory, such as a Lighthouse score or visual diffs, reports without blocking, because a gate that fails for reasons the author cannot control gets disabled within a month.
Why interviewers ask this
The interviewer is probing for pragmatism. Anyone can list tools; the useful signal is which checks you trust enough to block on and how you keep the pipeline fast enough that people do not route around it. Mentioning preview deploys and size budgets shows you think about catching regressions before users do rather than only after a rollback.
How to structure your answer
- Split the checks into blocking and advisory.
- Justify why each blocking one is trustworthy.
- Mention feedback speed and how you keep the pipeline short.
- Add preview environments and what they are for.
Example answer
Blocking, I want type check, lint, the unit and component suite, a real production build and a bundle size budget. Those are deterministic, they fail for reasons the author can fix, and they are fast. End to end tests run on the pull request but I only block on the small critical path suite, with the rest running on merge, otherwise the queue becomes the bottleneck and people start merging on red. Advisory, we post a Lighthouse run and a visual diff as a comment. I deliberately do not block on a performance score because it moves with runner noise, and a flaky gate gets bypassed and then ignored. Every pull request also gets a preview deploy, which is what designers and product actually review, and it catches the class of bug that only appears in a real build, like an environment variable that was never set outside development. The one gate people underestimate is the size budget: it is the only thing that stops a bundle drifting upward one dependency at a time.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How do you keep the pipeline under ten minutes as the suite grows?
- What do you do when a flaky test blocks an urgent fix?
- How would you set a sensible bundle size budget for a new project?
Related frontend developer questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions