Release / DevOps Engineer interview questions and answers

9 of 9 questions shown

1. juniorBasicsWhat is the difference between continuous delivery and continuous deployment?

   Model answer. Both automate the path to a releasable build. In continuous delivery a person approves the production release; in continuous deployment every change that passes the pipeline is released automatically.

   Tools: Jenkins, GitHub Actions

   I can answer this
2. midStrategiesCompare blue-green and canary deployments.

   Model answer. Blue-green keeps two full environments and switches all traffic at once, giving instant rollback at the cost of double capacity and care with database changes. Canary shifts a small percentage of traffic first and watches metrics, limiting blast radius but requiring good observability and automation.

   I can answer this
3. midDatabaseHow do you deploy a column rename with zero downtime?

   Model answer. Use expand and contract: add the new column, write to both, backfill, switch reads, stop writing the old column and drop it in a later release. Never rename in place while the previous application version is still running.

   I can answer this
4. midPipelineDesign the stages and quality gates of a pipeline for a web service.

   Model answer. Build once, then lint, unit tests and static analysis, build and scan the image, deploy to a test environment, run API and smoke tests, then critical end-to-end tests. Promote the same artifact to production with a canary and automatic verification. Put cheap, fast checks first.

   Tools: Docker, GitHub Actions, GitLab CI

   I can answer this
5. midFlagsHow do feature flags improve release safety and what risks do they add?

   Model answer. They separate deployment from release, allow gradual rollout and give a kill switch. Risks are flag debt, combinations that multiply test paths and untested default states. Test both states and remove flags after rollout.

   I can answer this
6. midRollbackWhen do you roll back and when roll forward?

   Model answer. Roll back when it is fast, safe and no irreversible data change has happened. Roll forward when a small fix is quicker or a migration makes rollback risky. Decide the criteria in advance and rehearse the procedure.

   I can answer this
7. seniorObservabilityWhat do you monitor in the first 30 minutes after a release?

   Model answer. Error rate, latency percentiles, saturation, new error signatures in logs, crash-free sessions and a business metric such as checkout conversion, all compared with a baseline. Automate rollback on SLO burn rate or threshold breach.

   I can answer this
8. seniorContainersHow do you make Docker builds fast and reproducible in CI?

   Model answer. Order layers so dependencies are cached, use multi-stage builds and BuildKit cache, and pin base images by digest. Keep a tight .dockerignore. Run as non-root and scan images before pushing.

   Tools: Docker

   I can answer this
9. seniorMetricsName the DORA metrics and how QA affects them.

   Model answer. Deployment frequency, lead time for changes, change failure rate and time to restore service. Fast, reliable automated tests shorten lead time and lower change failure rate; flaky tests do the opposite.

   I can answer this

No question matches those filters. Clear the search or choose All.