Loading
Hire developers
DevOps is a title stretched across very different jobs, from someone who wrote a few GitHub Actions workflows to someone who keeps a Kubernetes cluster alive under real load. The pool looks deep, but a lot of it is people who have only ever worked on top of managed platforms and have never had to reason about the layer underneath. Cloud knowledge also does not transfer as cleanly as resumes suggest: deep AWS experience does not make someone productive on GCP or Azure in week one. The real risk is hiring a capable CI script writer when what you actually need is someone who can own production and be woken up when it breaks.
Ask for a specific outage: what broke, how they found it, and how they rolled back or contained it. Strong candidates talk about observability, blast radius, and what they changed afterward so it would not happen again, not just the tools they ran. Probe how they handle secrets, cost, and a failed deploy at the worst possible time, since those separate people who operate systems from people who only set them up once. A good tell is whether they can explain a place where the managed abstraction leaked and they had to understand what was really happening underneath.
Describe the role in one chat and it goes live after a quick review. DevOps developers apply straight to your inbox.
Post a roleLooking for work? See DevOps developer jobs.