What stages should a good CI/CD pipeline have?
What they are really testing: Whether you know the logical sequence (build, test, scan, package, deploy) and the principle of failing fast with fast feedback, rather than a vague "it runs tests and deploys".
A real interview question
What stages should a good CI/CD pipeline have?
What most people say
drag me
“The pipeline runs the tests and then deploys the code.”
Too coarse. A good pipeline has ordered stages, build, fast-then-slow tests, static/security scans, package, deploy, each gating the next, and is designed for fast feedback (fail fast). "Runs tests and deploys" misses the structure.
The follow-ups they ask next
Why run unit tests before integration and e2e tests?
Fail fast: unit tests are fast and catch most issues in seconds, so developers get feedback immediately. Slow, expensive integration/e2e tests run only after the cheap checks pass, saving time and compute.
Where do security checks fit in the pipeline?
As gates within CI: SAST on the source, SCA on dependencies, and secret scanning, ideally early (even pre-commit) so issues are caught cheaply, with the build failing on critical findings.
What the interviewer is listening for
- Names build/test/scan/package/deploy stages
- Fastest-tests-first / fail fast
- Each stage gates the next + security gates
What sinks the answer
- "Runs tests and deploys" only
- No ordering / fail-fast
- Omits security/packaging
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“A pipeline is [ordered, gated stages]: [build (compile to artifact)], [test fastest-first: unit then integration, fail fast for quick feedback], [analyze/scan: lint + SAST/SCA/secret scanning], [package the immutable artifact and publish], then [deploy through environments, manual gate before prod for delivery]. Principles: [fail fast and gate each stage].”
Keep going with deployment
Foundation
What do CI and CD actually mean, and what is the difference between continuous delivery and continuous deployment?
Foundation
Why should you build an artifact once and promote the same one through environments?
Junior
A deploy went bad in production. How do you handle rollback, and how do you make rollback easy?
Junior
What are feature flags, and how do they decouple deployment from release?
Mid
Compare blue-green and canary deployments. When would you reach for each?
Mid
How does your branching strategy affect continuous delivery? Trunk-based versus long-lived branches.
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free