CI/CD Interview Questions and Answers
Pipeline design, artefacts, deployment strategies and rollbacks.
Whether you are preparing for entry-level CI/CD interview questions for freshers or senior software engineer interview questions addressing concurrency, scalability, and system architecture, this track provides peer-reviewed model answers with syntax walkthroughs, edge cases, and practical interview tips.
1 How do you implement safe rollbacks in a delivery pipeline? Hard
Make rollback a first-class, automated, and tested operation.
- Immutable artefacts: deploy versioned images or packages so you can redeploy the previous one exactly.
- Deployment strategies: use blue/green or canary so you can shift traffic back instantly. For Kubernetes, kubectl rollout undo reverts a Deployment.
- Database changes: use expand-and-contract migrations. Add columns and backfill first, make code compatible with both schemas, then remove old columns in a later release. Never ship a destructive migration with the code that needs it.
- Health checks and gates: automated verification after deploy, such as smoke tests and canary analysis, with automatic abort on failure.
- Feature flags: disable a feature without redeploying.
- Observability: alert on SLOs so you detect regressions quickly.
kubectl rollout history deployment/api
kubectl rollout undo deployment/api --to-revision=3
Practice rollbacks in game days; an untested rollback path is not a real safety net.
2 How do you secure a CI/CD pipeline? Hard
Treat the pipeline as production infrastructure with its own threat model.
- Secrets: never hardcode them. Use a secrets manager or OIDC federation so the pipeline gets short-lived credentials instead of static keys. Mask values in logs.
- Least privilege: pipeline roles should only deploy what they need. Separate build and deploy permissions.
- Supply chain: pin and verify third-party actions and base images, sign artefacts, and generate SBOMs. Scan dependencies and images for CVEs.
- Code review: protect main, require reviews, and prevent self-approval of pipeline changes.
- Isolation: run untrusted builds in ephemeral, network-restricted runners. Do not expose long-lived cloud credentials to fork pull requests.
- Audit: log who triggered what, and store pipeline logs immutably.
permissions:
id-token: write
contents: read
Rotate credentials, scan infrastructure code with policy-as-code, and verify provenance before deployment. Assume the pipeline is a high-value target.
Frequently Asked Questions About CI/CD Interviews
What do hiring managers evaluate in CI/CD technical rounds?
Technical interviewers look for foundational fluency, idiomatic syntax, clarity when communicating complex logic, and awareness of performance trade-offs (e.g. memory footprint, render performance, and network latency) in production environments.
What are the best interview tips for practicing CI/CD questions?
Use active recall: summarize each answer in your own words before revealing the model solution. Focus on explaining why a certain approach is chosen rather than just memorizing code syntax.