FoundationCI/CD

What is the difference between continuous integration, continuous delivery, and continuous deployment?

What they are really testing: A screen-out question. They want to know whether you can separate three things most candidates blur together, and whether you understand that the third one is a business decision, not a technical upgrade.

A real interview question

What is the difference between continuous integration, continuous delivery, and continuous deployment?

What most people say

drag me

CI is when you build automatically and CD is when you deploy automatically.

It collapses two distinct practices into one and completely misses continuous delivery, which is where most real companies actually live. It also shows no awareness of why a company would deliberately keep the manual gate.

The follow-ups they ask next

  • Your company wants continuous deployment. What has to be true first?

    Fast reliable tests with low flake, automated rollback, feature flags to decouple deploy from release, real monitoring that would catch a bad release, and small batch sizes so any single change is low risk.

  • A developer says CI is slowing them down. How do you respond?

    Ask what specifically: a slow pipeline is a real problem to fix, not a reason to skip CI. Usually the answer is parallelisation, caching, or moving slow tests to a post-merge stage.

What the interviewer is listening for

  • Separates all three cleanly
  • Knows continuous delivery is where most teams should sit
  • Frames continuous deployment as a risk decision, not a maturity badge

What sinks the answer

  • Collapses CD into one thing
  • Treats continuous deployment as automatically better
  • Cannot say what CI actually protects against

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.

CI is [everyone merging often with automated build and test on every merge]. Continuous delivery is [every passing build being proven deployable, with a human choosing when]. Continuous deployment is [no human gate at all]. The last step needs [trustworthy tests, monitoring and rollback] first.

Keep going with ci/cd

All 87 devops engineer questions

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