GhostpilotHome · Interview questions · DevOps Engineer
DevOps Engineer interview questions
DevOps interviews focus on how you keep software shipping safely. Expect to debug a broken deployment out loud and explain how you'd roll back when something goes wrong.
What interviewers look for
- Delivery. Pipelines that are fast, safe and easy to roll back.
- Operations. How you monitor, debug and respond to incidents.
- Automation. Infrastructure as code and removing manual work.
How the interview usually runs
- Recruiter call.
- Technical screen on Linux, networking and containers.
- Hands-on troubleshooting or design session.
- Behavioural round on incidents and collaboration.
Stages vary by company, so ask the recruiter what to expect before you start preparing.
10 DevOps Engineer interview questions, and how to answer them
1. Walk me through a CI/CD pipeline you built.
What they want to see: Real ownership.
How to answer: Cover stages, tests, artefacts, deploy strategy and rollback, with build times.
2. A pod is in CrashLoopBackOff. What do you do?
What they want to see: Systematic debugging.
How to answer: Run kubectl describe and logs with --previous, check exit codes, probes, config and memory limits.
3. Blue-green or canary?
What they want to see: Release trade-offs.
How to answer: Blue-green switches all at once, canary limits exposure. Choose by risk, traffic and rollback speed.
4. How do you manage Terraform state?
What they want to see: Safe infrastructure work.
How to answer: Use a remote backend with locking, separate environments and plan reviews.
5. What is GitOps?
What they want to see: Modern delivery practice.
How to answer: Git is the source of truth and an agent such as Argo CD reconciles the cluster, which gives audit history and easy rollback.
6. What do you alert on?
What they want to see: Monitoring judgement.
How to answer: Alert on symptoms users feel, such as error rate and latency, and keep alerts actionable.
7. How do you handle secrets?
What they want to see: Security basics.
How to answer: Use a secrets manager, rotate them, and never bake them into images or logs.
8. Debug a server that's slow.
What they want to see: Linux fundamentals.
How to answer: Check load, memory, disk I/O and network using top, vmstat, iostat and ss.
9. How do you reduce cloud spend?
What they want to see: Business awareness.
How to answer: Use rightsizing, autoscaling, spot capacity and removing idle resources, then track cost by team.
10. Tell me about your worst incident.
What they want to see: Calm and learning.
How to answer: Describe the timeline, how you communicated, and the fix that stopped it recurring.
A sample answer
Walk me through a CI/CD pipeline you built.
Our services deployed by hand with scripts, and config drifted. I moved 40 services to GitHub Actions and Argo CD, with images built once and promoted through environments. Automated sync and rollback replaced the manual steps. Deploys went from 40 minutes to six, and we stopped seeing drift-related incidents.
A made-up example to show the structure. Use your own experience and real numbers.Common mistakes
- Listing tools without saying what problem they solved.
- Jumping to a fix before gathering evidence.
- No rollback plan in a design answer.
- Blaming developers in an incident story.
Practise this out loud
Run a mock interview for a DevOps Engineer role. Questions change every time, you answer by voice or typing, and each answer gets a score with feedback.
Frequently asked questions
Is coding required for DevOps interviews?
Usually scripting rather than algorithms. Expect Bash or Python tasks such as parsing logs or calling an API.
Which certifications help?
CKA, AWS or Azure certifications can help you pass screens, particularly early in a career, but hands-on stories matter more in the interview.