# DevOps Engineer Interviews: What Gets Asked DevOps interviews check whether you can build and run the systems that ship software. Expect a mix of fundamentals, tooling questions, and troubleshooting scenarios. ## Linux and scripting You will probably be asked to explain processes, signals, file permissions, systemd services, and how to find what is eating disk space or memory. Scripting tasks are common: parse a log file, rotate old files, or call an API and act on the result. Bash and Python are both fine; write clear code and handle errors. ## CI/CD Be ready to describe a pipeline you built from commit to production: - Build, test, and security scan stages. - How artifacts are versioned and stored. - Deployment strategies: rolling, blue-green, canary. - How a bad release gets rolled back, and how fast. ## Containers and orchestration Know the difference between an image and a container, how layers and caching work, and how to keep images small. For Kubernetes, expect pods, deployments, services, ingress, config maps and secrets, resource requests and limits, and debugging a pod stuck in CrashLoopBackOff. ## Infrastructure as code Talk about Terraform or a similar tool: state files and locking, modules, plan review, drift, and how you keep secrets out of the repository. ## Monitoring and incidents Describe the metrics, logs, and traces you rely on, how you set alerts that page only for real problems, and an incident you handled. Walk through detection, mitigation, communication, and the follow-up review. ## Troubleshooting scenario "Users say the site is slow." Work outward from symptoms: check dashboards, recent deploys, error rates, dependencies like the database or cache, and resource saturation. Interviewers want a calm, ordered approach more than a lucky guess. ## Practice the scenario rounds Talking through an outage under time pressure is a skill. Rehearse a few with a friend or with [Linkjob AI](https://www.linkjob.ai/) so your reasoning comes out in a clear order.