What is CI/CD and why is it important for QA?

CI/CD fundamentals
DevOps
quality enablement

Your answer

Answer it first, then compare. Nothing here is saved or scored.

Model answer

CI (Continuous Integration): developers merge code frequently, automated builds and tests run on every merge. CD (Continuous Delivery/Deployment): code automatically progresses through stages to production. For QA: CI/CD means faster feedback (know within minutes if a change breaks something), consistent test execution (no "works on my machine"), and the ability to test every commit rather than a batch of changes. QA's role shifts from "gatekeeper" to "quality enabler", building test automation that runs in the pipeline.

What interviewers listen for

Pipeline shape
You design stages by failure cost and runtime budget, not by tool feature lists.
Parallelisation craft
You can shard a real suite and explain the state-isolation choices you made.
Quality gates
You know which checks block merge, which warn, and why those defaults are correct.
Shift-left fluency
You talk about ownership transfer, not just earlier execution.

See all 34 ci/cd questions