Tech hiring Cloud, DevOps & security
Hire DevOps engineers who make releases routine.
A DevOps engineer owns the path from a developer’s commit to running software: the pipeline, the environments, the infrastructure code and the checks in between. When that path is slow or fragile, every developer you employ ships less. We shortlist engineers who have automated it for teams like yours.
01 The role
What DevOps engineers do all week, and what comes out of it.
A DevOps engineer builds and maintains everything between “the code is merged” and “customers are using it”. That covers build and test pipelines, container images, environments defined in code, deployment and rollback, secrets, and enough monitoring for the team to know whether a release worked. Their customers are your developers.
The tools are the easy part. The hard part is changing how a team ships without stopping it from shipping: replacing a deployment only one person understands, getting a forty-minute pipeline down to ten, removing the long-lived credentials scattered across CI, and making production reproducible when it was built by hand over five years. Each of those is a migration carried out under live traffic.
In current practice the work is often called platform engineering: paved paths and templates that let developers create a service, a pipeline and an environment without filing a ticket. It differs from its neighbours in emphasis. A cloud engineer designs the accounts, networks and services everything runs on. A site reliability engineer is accountable for how production behaves. A DevOps engineer is accountable for how change gets there.
What they ship
- CI pipelines that build, test and scan every change in minutes
- Deployment automation with health checks and one-step rollback
- Infrastructure as code for every environment, reviewed like application code
- Container images and the Kubernetes or ECS manifests that run them
- Preview environments created for each pull request
- Secrets management and short-lived credentials for pipelines
- Dashboards and alerts that say whether a release was healthy
02 Skills and stack
Skills to look for, in three columns.
The useful question is not which of these a candidate has touched, but which they have run for a team in production. Tell us your CI system, cloud and orchestrator and we shortlist against them.
Core
The role cannot be done without these.
- Linux administration and networking fundamentals
- Scripting in Bash and Python or Go
- Git workflows and CI/CD pipeline design
- Containers: images, registries, runtime behaviour
- Infrastructure as code
- One cloud platform in working depth
- Deployment strategies: rolling, blue-green, canary
- Secrets and access management
Tooling
Varies from team to team.
- GitHub Actions, GitLab CI or Jenkins
- Docker and BuildKit
- Kubernetes with Helm or Kustomize
- Terraform or OpenTofu
- Argo CD or Flux for GitOps
- Ansible
- AWS, Azure or Google Cloud
- Prometheus and Grafana, or Datadog
- HashiCorp Vault or a cloud secrets manager
- Nginx, Caddy or Traefik
Adjacent
Useful, not required.
- Database operations: backups, migrations, replication
- Supply-chain security: image scanning, SBOMs, signed artefacts
- Cloud cost reporting and right-sizing
- Test automation and flaky-test triage
- Incident response and post-incident reviews
- Internal developer portals such as Backstage
03 When to hire one
Hire a DevOps engineer for the right problem, or hire someone else.
The wrong hire for the problem is an expensive way to learn what the problem was. Check your situation against both columns.
Hire a DevOps engineer when
-
Releases are an event, not a habit
Deploying means a checklist, an evening slot and one person who knows the steps. Teams in this position ship less often, so each release is larger and riskier.
-
Your best developer has become the part-time ops person
They keep the pipeline alive between features and resent it. The work is real and deserves an owner, and you get your developer back.
-
Nobody could rebuild production from scratch
Servers were configured by hand and the knowledge lives in two people’s heads. Putting it into code is the first job a DevOps engineer does.
-
Developers wait on builds, environments or access
Slow pipelines and a shared staging server that is always broken cost every engineer time each day. It is the cheapest productivity gain available.
-
You are moving to containers or Kubernetes
The migration touches builds, configuration, networking and deployment at once. It goes better led by someone who has run workloads on it before.
Look elsewhere when
-
You are designing a cloud estate or planning a migration
Account structure, network layout, identity and service selection are architecture decisions that outlast any pipeline. A cloud engineer is closer to that work.
Hire cloud engineers -
Deployment is fine but production keeps having incidents
If the pain is outages, paging and slow recovery, you need someone accountable for reliability targets and incident practice.
Hire site reliability engineers -
One small app on a managed platform
On Vercel, Render, Fly.io or a similar service, the platform is your DevOps. A developer comfortable with deployment is enough until you outgrow it.
Hire full-stack developers -
The driver is a compliance audit or a security review
DevOps engineers apply security controls in pipelines and infrastructure; they do not usually own threat modelling, policy or audit evidence.
Hire security engineers -
The database is the thing that is slow or at risk
Query tuning, replication and recovery testing on a large database is specialist work. Do not expect a pipeline engineer to carry it alone.
Hire database administrators
04 How we assess
How we assess DevOps engineers, before you meet one.
A CV says what someone claims. We test what they can do, then send you the evidence with the shortlist.
-
Stage 1
Profile review
We look for pipelines and infrastructure the candidate built and then ran: the size of the team it served, what was in code and what was manual, and what they changed. A list of certifications and tool names tells us little by itself.
-
Stage 2
Technical test
A timed test covering Linux, networking, containers and scripting, with practical tasks such as reading a failing pipeline, writing infrastructure code for a small service or spotting what is unsafe in a deployment configuration.
-
Stage 3
Conversation with our team
Our engineers ask the candidate to walk through a delivery pipeline they owned: how a change reached production, how it was rolled back, where secrets lived and what broke. We listen for whether they treated developers as users.
-
Stage 4
Review and levelling
Reviewers score accuracy, speed, problem-solving, communication and teamwork, then assign a level from our DevOps framework. The notes separate engineers who designed a delivery path from those who operated one somebody else built.
-
Then
Your shortlist
Assessed candidates, with notes and scores.
The engine
Evalia
Assessments run on Evalia, the assessment platform we built ourselves. Across the ProDevs network, more than 100,000 assessments have been completed.
The levels we assign are public. Read the DevOps framework, or see how a hire runs from brief to offer.
05 Seniority
Same title, different scope. What each level can own.
The title on a CV tells you little. What matters is how much a DevOps engineer can be handed without someone checking each step.
Junior
Owns a pipeline job or a module
- Adds and fixes pipeline steps, Dockerfiles and small Terraform modules
- Follows runbooks for deployments and routine maintenance
- Needs review on anything touching production access, networking or state
- Rarely a sensible first infrastructure hire for a team with no senior
Mid-level
Owns the pipeline for a team
- Builds CI/CD for a new service end to end, including rollback
- Writes and refactors infrastructure code without breaking existing state
- Debugs failures across build, network, container and cloud layers
- Takes part in the on-call rota and writes up what went wrong
Senior
Owns the delivery platform
- Designs how every team builds, deploys and gets an environment
- Leads migrations, such as VMs to containers, with no freeze on feature work
- Sets standards for secrets, access, artefact provenance and change review
- Chooses what to build, what to buy and what to delete
Indicative salary
DevOps and cloud engineers. Annual, in US dollars, for remote roles with US, UK and EU companies.
- Mid-level
- $35–60k
- Senior
- $60–90k
- Typical US equivalent
- $130–200k
Indicative market ranges as of August 2026, based on ProDevs placement experience and published market data. The exact figure depends on stack, seniority and time-zone requirements. See the full cost breakdown.
06 Interview questions
Interviewing a DevOps engineer? Ask these.
Borrow these for your own interview loop. Beside each is what to listen for.
-
Walk me through what happens between a merge to main and that change serving traffic.
A good answer shows: Every step named in order: build, tests, image, registry, deploy mechanism, health checks, traffic shift. Strong candidates say where it can fail and what happens automatically when it does. Gaps here mean someone else built it.
-
A deployment went out and error rates doubled. What do you do in the first five minutes?
A good answer shows: Roll back first, investigate second, and tell people what is happening. Then they explain how rollback works when a database migration was part of the release. Debugging forward on a live system is the weak answer.
-
How do you handle Terraform state, and what has gone wrong with it for you?
A good answer shows: Remote state with locking, split by environment or component, with plans reviewed before apply. Real experience shows in the stories: drift from console changes, a resource that had to be imported, a state file that needed careful surgery.
-
Our pipeline takes forty minutes. How would you bring that down?
A good answer shows: They measure which stages take the time before changing anything, then talk about dependency and layer caching, parallel test shards, running only what a change affects and fixing flaky tests. Buying bigger runners is a last step, not a first.
-
Where do secrets live in your pipelines, and how do they reach the running application?
A good answer shows: A secrets manager, short-lived credentials through OIDC federation in place of stored cloud keys, and nothing sensitive baked into images or printed to logs. Ask how they would rotate a leaked key; a good candidate has done it.
-
When would you advise a team not to adopt Kubernetes?
A good answer shows: When a handful of services would run happily on a managed container service or a platform-as-a-service, and nobody is available to operate a cluster. Willingness to recommend the simpler option is a mark of seniority.
-
Tell me about something you automated that developers actually thanked you for.
A good answer shows: A concrete problem developers had, how they found out about it, and the before and after. It shows whether the candidate builds for their users or for their own interest in tools.
07 Ways to engage
Four ways to bring a DevOps engineer in.
A permanent hire is the usual route, not the only one. Choose by how long the work lasts and who should employ the person.
- Placement fee, of first-year salary. One-time.
- 10–15%
- Replacement guarantee on direct hires.
- 2 weeks
- To a first shortlist, for most roles.
- 48h
-
Direct hire
A permanent employee on your contract and your payroll. One-time placement fee of 10–15% of first-year salary.
Tech hiring -
Dedicated team
A DevOps engineer inside a team we assemble and run for you: product, design and engineering on your roadmap, for a monthly retainer.
Dedicated teams -
Outsourcing & payroll
A full-time person in a country where you have no legal entity. ProDevs employs and pays them: 20% of salary if we find the person for you, or 5% of salary, capped at $500 a month, for payroll and compliance on someone you have already chosen.
Outsourcing -
Freelance project
A defined piece of work with a clear end. You pay the agreed price per milestone through escrow, plus a 5% client fee. Free to post.
Freelancers
08 Around the role
Who DevOps engineers depend on, and who depends on them.
In a small company the DevOps engineer is a team of one serving every developer, so priorities come from whatever is slowing releases most. In larger organisations they form a platform team that builds shared tooling while product teams run their own services on top of it.
- Software developers
- Treats them as customers: shortens their feedback loop and gives them a safe way to deploy their own changes.
- Cloud engineer
- Builds pipelines and tooling on the accounts, networks and guardrails the cloud engineer defines.
- Site reliability engineer
- Shares deployment safety: canary analysis, rollback triggers and the telemetry each release emits.
- Security engineer
- Puts scanning, signing and access policy into the pipeline so that controls run on every change.
- QA tester
- Provides stable test environments and makes automated suites fast enough to run on every pull request.
09 Client testimonials
Hear it first-hand, from companies that hired.
Founders, operators and executives describe working with ProDevs, in their own words.
Play video: Client testimonial: Olufemi Seyi, COO, Casafina development company
Play video: Client testimonial: Aproko Doctor, Building AwaDoc
Play video: Client testimonial: JT Liddell, Promenade CEO
10 Questions
Before you hire a DevOps engineer: the usual questions.
Something else? Book a call (opens in a new tab) and ask us directly.
-
What is the difference between a DevOps engineer, a cloud engineer and an SRE?
They overlap, and small companies ask one person to do all three. The emphasis differs. A DevOps engineer owns how code gets to production: pipelines, environments and deployment. A cloud engineer owns what it runs on: accounts, networks, identity and cost. A site reliability engineer owns how production behaves: availability targets, alerting and incident response.
-
When should a startup hire its first DevOps engineer?
Usually when a developer is spending a day or more each week on deployments and infrastructure, or when a customer contract demands environments and controls you cannot produce by hand. Before that point a managed platform and a careful developer are enough. Hire a senior person first; this is a poor role to learn alone.
-
Is platform engineering the same thing as DevOps?
It is the same work with a clearer product: a platform team builds self-service tooling, templates and paved paths that other teams use, where a traditional DevOps engineer often handled requests one at a time. If you have more than a few product teams, ask for platform experience in the brief.
-
Do we need Kubernetes experience?
Only if you run Kubernetes or have a firm reason to adopt it. Many products are served well by a managed container service such as ECS, Cloud Run or Azure Container Apps, with far less to operate. Tell us what you run today. A strong engineer on a simpler stack is a better hire than a Kubernetes specialist with nothing to orchestrate.
-
How do you assess DevOps engineers?
In four stages. We review the pipelines and infrastructure a candidate has built and run, set a timed technical test, hold a conversation with our engineering team about a delivery system they owned, then review the results together and assign a level from our public DevOps framework. The assessments run on Evalia.
-
What does a DevOps engineer in Africa cost?
For remote DevOps and cloud roles with US, UK and EU companies, indicative annual salary ranges are $35,000–$60,000 at mid-level and $60,000–$90,000 at senior level. These are market ranges, not quotes. A direct hire through ProDevs also carries a one-time placement fee of 10–15% of first-year salary.
Talk to ProDevs
Tell us about the role.
Tell us the level and the stack. We will tell you how quickly we can put assessed DevOps engineers in front of you.
Project work
Need it for a project instead?
Not every job needs a full-time hire. Describe the work, get proposals from vetted freelance DevOps engineers, and pay per milestone through escrow. Free to post.