How would you design a production CI/CD pipeline?
Start with source control, required checks, reproducible builds, tests, security scans, immutable artifacts, environment approvals, deployment strategy, telemetry and rollback.
Interview preparation
Weak answers name tools. Strong answers explain controls, failure modes, operational evidence and why the design fits the risk.
Start with source control, required checks, reproducible builds, tests, security scans, immutable artifacts, environment approvals, deployment strategy, telemetry and rollback.
Continuous delivery keeps every validated change releasable; continuous deployment automatically releases every change that passes the controls.
Use a remote encrypted backend, locking, least privilege, environment separation, versioning, backup and controlled state operations.
Inspect rollout status, events, pod state, logs, probes, resource limits, configuration, secrets, networking and dependencies before choosing rollback or repair.
It identifies user impact, has a clear owner, avoids duplicate noise, includes context and links to a tested response procedure.
Protect branches, pin trusted actions, scan dependencies and images, manage secrets externally, generate provenance and SBOMs, sign artifacts and enforce policy.