CI vs. CD
CI (Continuous Integration) means code changes are merged and tested frequently. CD is ambiguous on its own — it can mean Continuous Delivery (always releasable, but a human still triggers the release) or Continuous Deployment (every passing change ships automatically) — and teams that say "we do CI/CD" often only really do the CI half.
How to tell them apart on a resume
CI (Continuous Integration)
Describes automated build/test on every pull request — GitHub Actions, Jenkins, or similar.
CD (Continuous Delivery / Deployment)
Describes what happens after tests pass — but "CD" alone doesn't say whether that's an automatic production deploy or just a one-click-ready release.
The question that settles it
“When you say CI/CD, does a merge to main actually deploy to production automatically, or is there still a manual release step?”
Read the full definitions
Open the full tool for the other look-alike pairs, role profiles, and the JD decoder.