What does a DevOps consultant do?
A DevOps consultant designs, builds, and hands over the delivery machinery your product runs on: CI/CD pipelines, infrastructure as code, Kubernetes platforms, deployment automation, and the observability wired to releases. The good ones engineer themselves out of the critical path; the bad ones become a staffing line you can't cancel. Everything on this page is scoped toward the first outcome.
Week one is a read-only audit. We read your pipeline configs, your Terraform state, your deploy history and your incident channel before we touch anything — because the call usually comes after a run of bad release days, and the cause is rarely the CI tool on the label. It is almost always state: drift between environments, secrets handled by hand, a deploy path that works only when one specific person runs it. The audit ends in a written findings doc with the fixes ranked by risk-reduction per week of effort.
From there the engagement ships in reviewable increments — every change lands as a pull request your team reviews, not a mystery branch we merge on the way out. What you hold at the end is concrete: pipelines with explicit gates, infrastructure that rebuilds from code, runbooks someone other than us has executed, and DORA metrics reported out of the pipeline itself so the improvement is measurable rather than asserted.
Consultants or another in-house hire?
Honest answer: it depends on whether the work is a project or a function. The short version:
| Consulting engagement | In-house hire | |
|---|---|---|
| Time to start | Days to weeks | Months of hiring, plus ramp |
| Cost shape | Fixed scope, defined end | Permanent payroll, whatever the backlog |
| Breadth | Patterns from many production estates | Deep context on yours, over time |
| Knowledge transfer | Built into the engagement (pairing, docs) | Walks out the door if they leave |
| Pager | Yours after handover (or ours, under managed DevOps) | Theirs, on day one |
| Fits best when | A platform needs building or fixing | A built platform needs owning |
The full argument, with the cost math for both models, is in managed DevOps vs in-house. Where your rates land is in DevOps consulting rates.