Skip to main content
Strategy & Process
DEFINITION

What is Quality Gates?

Quality gates are checkpoints in the software delivery process where predefined quality criteria must be met before work can proceed to the next stage, enforcing minimum standards at each phase. Typical gates include passing tests, code coverage thresholds, static analysis results and security scans, and they are automated in the CI/CD pipeline.

No account needed · Scored in under a minute against a senior rubric

IN DEPTH

What does Quality Gates mean in practice?

Quality gates act as automated or manual tollbooths in your delivery pipeline. Each gate has specific pass/fail criteria. A commit-level gate might require passing linting and unit tests. A PR gate might require code review approval, minimum test coverage, and no new security vulnerabilities. A pre-production gate might require passing integration tests, performance benchmarks, and accessibility scans. A release gate might require stakeholder sign-off and successful smoke tests in staging.

The most effective quality gates are automated and integrated directly into CI/CD pipelines. When a developer pushes code, the pipeline runs each gate sequentially and blocks progression if any gate fails. This removes human bias and ensures consistency. Tools like SonarQube, GitHub Actions branch protection rules, and Argo CD sync policies enable automated gating.

The risk of quality gates is over-gating: too many gates or overly strict criteria slow delivery to a crawl. The solution is to calibrate gates to the risk level of each stage. Early gates should be fast and lenient (linting, unit tests). Later gates can be thorough and strict (full regression, performance benchmarks).

WHY IT MATTERS

Why do interviewers ask about Quality Gates?

Interviewers ask about quality gates to see whether you can design and enforce systematic quality controls. This is a key skill for QA leads and SDETs who shape delivery processes.

EXAMPLE

What does Quality Gates look like in a real project?

A team implements three quality gates: PR gate (unit tests, lint, coverage >= 80%), staging gate (integration tests, zero critical bugs), and release gate (smoke tests pass in production-like environment, load test meets SLA). A developer's PR is blocked because coverage dropped to 76%. They add two unit tests and the gate passes on the next push.

TIP

How should you talk about Quality Gates in an interview?

Describe quality gates you have implemented or improved. Be specific about the criteria at each gate and how you balanced thoroughness with delivery speed.

FREE TOOLS  /  no signup

Free QA career tools, no account needed

Instant and private, everything runs in your browser. Try them before you sign up.

EXEC.NOW

Ready to Ace Your QA Interview?

Practice explaining quality gates and other key concepts with our AI interviewer.

Join 500+ QA engineers already practicing with AssertHired.

Question 1 · Automation · Mid-levellive scoring

A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.

Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.

Rather skip ahead? Create a free account

FREE.TO.START  ·  7.DAY.TRIAL ON PAID PLANS
Written by , Senior QA Automation Engineer, 50+ QA candidate interviews conductedLast updated July 2026