Roles we recruit
Seven practices, 27 functions. Start at the practice when you cannot yet name the title; go straight to the function when you can.
Browse all 229 roles Brief us on a seatFlat 15% of first-year base · shortlist in 10 working days
A DevOps engineer owns the path from code to production: pipelines, infrastructure as code, containers and the monitoring that tells you something broke before a customer does. Tool lists are easy to write, so we screen for releases they made routine, an outage they handled well, and how they work with engineers who just want to ship.
The first quarter decides whether releases get safer and faster or the team keeps working around a fragile process. Each stage below has a signal that predicts it, and we test for that signal before you meet anyone.
The ramp, and the test behind each milestone
Weeks 1 and 2
Every step from merge to live, who can deploy, what breaks and the last ten incidents. Reads the pipeline, the environments and the access list, and finds the manual steps that carry risk.
On track looks like a written map of the release path and the five riskiest steps in it, ranked by what breaks.
How we test for it before you meet them
A review exercise in our screen: a described pipeline and an outage timeline. We score what they find first and what they would leave alone.
Weeks 3 to 6
The manual step most likely to break signup or billing automated or guarded, with a rollback that has been tried, so a bad release can be reversed in minutes.
On track looks like a release that no longer needs a person to remember a step, and a rollback they have tested.
How we test for it before you meet them
We ask for a pipeline they improved and what changed in release frequency or failures. A former engineering lead confirms it.
Weeks 7 to 10
The systems revenue depends on, signup, billing and the integrations, described in code, reviewed like any other change, with staging that matches production closely.
On track looks like the revenue-critical systems rebuilt from code in a test environment, with no hand-made settings.
How we test for it before you meet them
We ask how they would rebuild a system from nothing and what they could not, so we see where the manual knowledge sits.
Weeks 11 to 13
Monitoring on the paths customers use, alerts with owners and a short runbook for each, plus an on-call routine that does not burn out the team.
On track looks like a customer-facing failure found by an alert first, and handled from a runbook.
How we test for it before you meet them
A reference call about an incident they led: how it was found, how it was handled and what changed afterwards.
After day 90
Strong DevOps engineers start reporting how often the team ships, how often a change fails and how fast it is fixed, and watch cloud cost as well as uptime.
On track looks like a monthly view of deploy frequency, failures and recovery time that engineering leadership uses.
How we test for it before you meet them
We ask what they would measure first at your company. A specific answer tied to release pain predicts an engineer who improves delivery, not only tooling.
Five responsibilities. If the seat mainly designs the overall architecture, it is a solutions architect; if it mainly secures systems, it is a security engineer.
CI/CD from merge to production, with tests, approvals and a way to reverse a bad release.
Environments described in code and reviewed like any other change, not built by hand.
Consistent staging and production setups, so what passes testing behaves the same live.
Alerts on what customers use, runbooks and an on-call routine that people can sustain.
Who can change what, and what the cloud bill is buying, reviewed on a schedule.
Three neighboring seats absorb work people assume belongs here. Drawing the line wrong is how a DevOps hire ends up writing product features or running a security program.
That seat ownsDesigning and running the cloud setup itself: accounts, networks, services and cost.
Hire it instead whenthe cloud foundation needs design or cleanup, beyond the release process.
That seat ownsProtecting the systems: access, vulnerabilities, secrets and response to threats.
Hire it instead whenthe main risk is a breach or a compliance gap, not a failed release.
That seat ownsThe APIs and webhooks customers and partners call: design, authentication and versioning.
Hire it instead whenthe problem is the interface other people build on, not how it reaches production.
The title stays the same; the work does not. Pick the one that matches your engineering team.
The first dedicated engineer, taking over deployments that developers did by hand.
Builds the internal tools and templates that let product teams ship without asking for help.
Concentrates on uptime, monitoring and incident response for systems where downtime costs revenue.
The questions we ask in our own screen. Use them in yours; the warning signs are as useful as the answers.
Every candidate we put forward is scored on these five, and the scores travel with the shortlist, gaps included. Four out of five with a named weakness beats a clean sweep you cannot verify.
| What we score | Weak evidence | Strong evidence |
|---|---|---|
| Release improvements with numbers | Lists tools and certifications. | Names frequency, failure rate or time to deploy, before and after. |
| Incident handling | Debugs in production first. | Rolls back, communicates and fixes the cause, confirmed by a reference. |
| Infrastructure as code | Hand-built environments no one can reproduce. | Systems rebuilt from code, with the manual gaps named. |
| Monitoring that helps | Alerts on machine metrics only. | Alerts on customer paths, with owners and runbooks. |
| Working with developers | Treats requests as interruptions. | Tools and templates developers use on their own, confirmed by a developer. |
Public US benchmarks, read October 2026. Salary.com’s DevOps engineer band and Built In’s self-reported figures agree closely, with Built In’s average total of $150,355 above the base band. Cloud and architecture seats sit nearby, and the BLS band for systems administrators runs lower.
Each bar runs from the 25th to the 75th percentile, the middle half of reported pay.
Base salaryWages including commission (BLS)Average total pay, base plus variable
DevOps Engineer
Salary.com base, Built In total
$122,133 to $142,408 base$150,355 average total
Cloud Engineer
Salary.com base benchmark, neighboring seat
$96,514 to $117,252 base
Solutions Architect
Salary.com base benchmark, neighboring seat
$118,623 to $139,366 base
Network and computer systems administrators
BLS, all industries
$78,010 to $126,640
DevOps Engineer bar, Cloud Engineer and Solutions Architect: Salary.com base salary, 25th to 75th percentile, United States, as of October 1, 2026. DevOps Engineer ring: Built In average total compensation (base plus additional cash, self-reported), reviewed October 16, 2026. Network and computer systems administrators: U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2025, annual wage at the 25th and 75th percentiles (SOC 15-1244), all industries. Public aggregates, not ZaphyrRecruit placement data.
A DevOps engineer builds and runs the path from code to production: CI/CD pipelines, infrastructure described in code, containers and environments, and the monitoring and alerts that show problems early. In a go-to-market company that includes the systems revenue depends on: signup, billing and the integrations that connect the CRM.
Salary.com puts a DevOps engineer at $122,133 to $142,408 base, with a median of $134,601 (October 2026). Built In’s self-reported figures show a $125,000 median base and $150,355 average total pay. Cloud engineers sit lower, at $96,514 to $117,252 base on Salary.com. Seniority and on-call duty move the number. Ask for the full package, not base alone.
A DevOps engineer for hire is often a contractor or agency, which suits a one-off migration or a pipeline build. In-house pays off when you ship weekly, downtime costs revenue and someone has to own incidents. They learn the product and keep the setup simple. Managed platforms help for the commodity parts.
A DevOps engineer owns how code gets released and how it behaves in production: pipelines, environments and monitoring. A cloud engineer designs and runs the cloud setup: accounts, networks, services and cost. In small companies one person does both. If releases are the pain, hire DevOps; if the foundation is the pain, cloud.
When releases are manual and risky, when a deploy can break signup or billing, when customers spot outages before you do, or when developers spend real time on deployment. Before that, managed hosting and a small set of scripts may do. The signal is engineering hours lost to releases and incidents.
Describe a pipeline and an outage timeline with real problems in them and ask what they would find first and what they would leave alone. An hour is enough. It shows judgment about risk and priorities, which tool lists hide. Avoid long unpaid builds: strong engineers decline them. A short paid exercise is fairer if you need more.
Ten working days from a signed brief to a shortlist of three to five calibrated engineers, each with our review exercise scored and their pipeline work checked with a former engineering lead. Interview speed decides the rest: good DevOps engineers rarely run one process at a time, so a decision within two weeks of the first interview keeps them.
Tell us how code reaches production today, what has broken and who will work with the engineer. We come back within one business day with how we would run the search and what the seat pays.
We build shortlists from people doing this work now, often before a seat is advertised. Set up a job alert for engineering roles, or send your CV and we will come to you when a seat opens.
The DevOps engineer is one of eight seats in this function. If the gap sits elsewhere, start there.