SeniorCI/CD & DevOps for QA
How do you implement quality gates in a CI/CD pipeline?
- quality gates
- CI enforcement
- automated checks
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Quality gates are automated checkpoints that block promotion if criteria aren't met. Examples: (1) Code coverage threshold (e.g., new code must be >80% covered). (2) Zero critical/high security vulnerabilities (Snyk, SonarQube). (3) All tests pass (no test failures). (4) Performance budget met (Lighthouse score >90). (5) No flaky tests introduced. Implementation: configure CI to run checks and block merge/deploy on failure. Balance: too strict = developer friction, too loose = quality issues. Start strict on critical paths, lenient on experimental branches.
What interviewers listen for
- Pipeline shapeYou design stages by failure cost and runtime budget, not by tool feature lists.
- Parallelisation craftYou can shard a real suite and explain the state-isolation choices you made.
- Quality gatesYou know which checks block merge, which warn, and why those defaults are correct.
- Shift-left fluencyYou talk about ownership transfer, not just earlier execution.