How to Interview a DevOps Consultant: 12 Questions That Separate Experts from Pretenders

You need a DevOps consultant, but resumes all look the same: "10+ years, Kubernetes, CI/CD, cloud-native." The real question is whether they can actually architect resilience or just deploy from templates.

The Infrastructure Mastery Tier (Questions 1–4)

Ask candidates to walk you through a multi-region failover strategy. Not the theory—the actual failure mode they'd prevent. Listen for: specific metrics they'd monitor, RPO/RTO definitions they'd defend, and which cloud primitives they'd use.

Then ask: "Describe the last time your infrastructure failed in production. What did you miss in your design?" Anyone worth hiring has a war story and learned from it. If they say "it never happened," they haven't built anything at scale.

Third: "How would you cost-optimize our cloud spend without sacrificing reliability?" The answer reveals whether they understand the tension between architectural decisions and P&L impact.

Fourth: "Walk me through your approach to Kubernetes resource requests and limits." If they hand-wave this, they don't understand containerization fundamentals.

The Operations & Tooling Tier (Questions 5–8)

"What's your opinion on GitOps vs. traditional IaC?" Their answer matters less than why they choose. Experts articulate trade-offs; pretenders pick a buzzword.

"How do you design observability into a system from day one?" Red flags: "we use a monitoring tool" or "we alert on CPU." Green flags: mention traces, distributed context, and log correlation.

"Build me a basic CI/CD pipeline in pseudocode right now." Watch them struggle with branching strategy, artifact management, or environment promotion. This separates consultants from hands-on architects.

"What's your disaster recovery testing cadence, and why?" Bonus points if they mention chaos engineering or game days.

The Architecture & Culture Tier (Questions 9–12)

"How do you handle DevOps adoption resistance from legacy teams?" Consultants who only know tools fail here. Listen for change management, mentorship, and empathy.

"What's your stance on containerization when legacy monoliths aren't ready?" If they push containers as a religion instead of a tool, keep looking.

"Give me three red flags you'd see in a DevOps team's setup in the first week." Expert answers are specific and predictive.

Finally: "Show me a project where your work directly impacted revenue." Real consultants quantify impact.

---

TL;DR

• Ask for specific production failures and what they'd change—experience matters more than certifications
• Test infrastructure fundamentals (Kubernetes resources, GitOps trade-offs, observability design) with concrete scenarios
• Evaluate cultural fit and architecture thinking, not just tooling knowledge

Finding the right DevOps consultant means seeing past the resume. At ClockHash DevOps Consulting, we hire using these same standards—and we expect the same rigor from teams evaluating us.

---

Originally published on the ClockHash Engineering Blog.

---

ClockHash Technologies — DevOps · AI · Cloud · Built for Engineers

Products:
HashInfra · HashSecured · HashNodes · AlphaInterface

Free Tools:
AutoCI/CD · CloudAsh · DockHash

Services:
DevOps Consulting · AI/ML Development · App Development · Remote Tech Teams