How to Screen a DevOps Engineer Resume: Must-Haves, Red Flags and a Scoring Rubric
DevOps CVs are tool inventories: a cloud, an orchestrator, a CI system, an infrastructure-as-code tool, a monitoring stack. Screen past the inventory for what the candidate changed about how software reached production, and for what they did when it broke.
- Read for evidence before matching keywords: a devops engineer CV should show what the candidate built, ran, closed or decided, with a result. The must-haves below are the four things the job cannot be done without.
- Must-haves: infrastructure as code in production for a real system, tool named and scope described; ownership of a CI/CD pipeline with some improvement described (speed, reliability, safety). Nice-to-haves raise a candidate; they do not rescue one missing a must-have.
- Red flags are patterns, not single lines: a tool list with no system it was applied to, and no incident, outage or on-call anywhere in the history.
- Use the five-criterion rubric on the page, weighted so that delivery improvements counts more than job description match. It is written to be pasted into WadeCV as a role and scored automatically.
- Spend three minutes per CV with the rubric and write one line of evidence per criterion. Screening decisions with evidence attached can be explained to the candidate, to the hiring manager, and to anyone who audits them later.
Must-haves
- Infrastructure as code in production for a real system, tool named and scope described
- Ownership of a CI/CD pipeline with some improvement described (speed, reliability, safety)
- Operational experience: on-call, incidents, monitoring, with a story or a metric
- The cloud provider the role uses, or a close enough one with depth
Nice to have
- Security work: secrets management, IAM, rotation, scanning
- Cost management with a result
- Container orchestration at the scale the role needs
- Developer experience work: templates, platforms, self-service
Red flags
- A tool list with no system it was applied to
- No incident, outage or on-call anywhere in the history
- 'Migrated to Kubernetes' with no reason or outcome
- Certifications outnumber projects
The rubric
Score each criterion from what the CV shows; weight 3 counts three times weight 1. In WadeCV, create the role with these criteria and every CV is scored this way automatically.
| Criterion | How to measure it | Weight |
|---|---|---|
| Job description match | Match between cloud, tooling, scale and the role as written | 2 |
| Years of relevant experience | Years running production infrastructure, not total years in IT | 2 |
| Delivery improvements | Pipeline and deployment changes with measured outcomes | 3 |
| Operational maturity | Incidents, on-call, monitoring and follow-ups described concretely | 3 |
| Security and cost | Evidence of secrets, access and spend being managed deliberately | 1 |
How to read the CV
Look for the before and after. 'Cut deploy time from 40 minutes to 6 and reduced failed deploys by half by splitting the pipeline and adding canaries' is a DevOps bullet. 'Managed CI/CD pipeline in Jenkins' is an inventory entry. The candidates you want have the first kind, usually several.
Then look for the bad day. Incidents, outages, on-call: every real operations engineer has them and the good ones write about what changed afterwards. A history with no failure in it is either very junior or very selective.
Weight operational maturity above tool match. Tools change yearly; the judgement about risk, blast radius and rollback is what you are hiring, and it shows in how incidents are described.
Frequently asked questions
How much do cloud certifications count?
As evidence of study, a little; as evidence of operating skill, nothing. Score the delivery and incident bullets and treat the certification as a tie-breaker at most.
Our stack is on a different cloud. Does that rule candidates out?
Not if their depth is real. The concepts transfer; the console does not, and that takes weeks. Weight cloud match at 2 and let the rest of the rubric decide.
Should a DevOps engineer have a software development background?
Enough to read and write code comfortably; the role is increasingly about building internal tooling. Look for scripting and tooling work in the history.
Related guides
Screening devops engineer CVs this week?
Paste the job description into WadeCV, check the rubric it drafts, and upload the CVs. Each one is read against the rubric and scored with an explanation. Ten screenings are free; there is no subscription.
Screen your first CVs free