DevOps engineer CV: example, skills and writing tips

DevOps engineer CV example

The example below shows how the advice in this guide fits together on one page. The person, the companies and all the figures are invented: use the structure, not the content, and replace every detail with your own.

Notice what makes this CV useful to a recruiter: every line says which environment, which tool, at what scale and with what effect. The rest of this guide explains how to build each section in the same way.

Job title and professional summary

Choose a title that shows your stack

“DevOps” covers very different jobs: some roles are mostly CI/CD, others mostly cloud infrastructure, Kubernetes platforms or production reliability. A title that names your main environment is far more informative than “DevOps Engineer” alone, as long as it is true:

DevOps Engineer – AWS / Kubernetes / Terraform
DevOps Engineer – Azure and Azure DevOps pipelines
DevOps Engineer – CI/CD and Infrastructure as Code
Cloud DevOps Engineer – GCP
DevOps / Platform Engineer – Kubernetes

The goal is not to stuff in keywords. A precise title lets recruiters, and the search tools they use, see your stack at a glance.

DevOps, SRE, platform or cloud engineer: which title fits?

These titles overlap and their scope varies between employers. Pick the one that describes what you actually do, and keep your real past job titles in the experience section.

Professional summary example: experienced DevOps engineer

The professional summary (often called a personal profile in the UK) is three to five lines that answer three questions: what is your profile, how much experience do you have, and what can you take charge of?

DevOps engineer with 6 years’ experience automating infrastructure and CI/CD for SaaS products. Runs Kubernetes workloads on AWS, provisions environments with Terraform and maintains GitLab CI pipelines for 12 teams. Took part in reducing deployment time and manual operations work.

Professional summary example: junior DevOps engineer

Computer science graduate ([degree], [year]) with a [12-month] work-study placement in a DevOps team. Hands-on experience maintaining GitLab CI pipelines, building Docker images, deploying to Kubernetes and provisioning cloud resources with Terraform, under the supervision of senior engineers.

Adapt these examples to your real situation. Never add a tool or a cloud provider just because it appears in a job ad, and replace phrases such as “passionate about cloud” with concrete facts.

DevOps engineer CV skills by area

A DevOps engineer’s work typically covers delivery pipelines, containers and orchestration, infrastructure as code, cloud, scripting and observability. Do not list every tool you have heard of: select the skills you genuinely use, ideally in production, and phrase them so a recruiter can see how.

A skills line such as this gives little information:

DevOps – Cloud – Docker – Kubernetes – Agile

This one is far more useful:

GitLab CI · Docker · Kubernetes and Helm · Terraform · AWS (EC2, VPC, IAM) · Prometheus/Grafana · Bash and Python

Describing your experience and achievements

Experience is the section recruiters read most closely on a DevOps CV, because it shows your real level of autonomy. For each line, follow this order where possible:

context → your own action → tools or method → scope → result

For example: “For a SaaS product with 12 development teams (context), I rebuilt the shared CI templates (action) in GitLab CI with build caching and parallel tests (tools), used by around 60 pipelines (scope), which cut average deployment time from 40 to 12 minutes (result).” The figures in this sentence are illustrative.

Too vague

CI/CD
Kubernetes
Terraform
Monitoring

More informative

Illustrative figures.

Maintained around 60 GitLab CI pipelines and their shared templates
Operated 4 Kubernetes clusters hosting around 35 services
Provisioned AWS environments with reusable Terraform modules
Built Prometheus/Grafana dashboards and alerts for production services
Took part in the on-call rotation and post-incident reviews

The second version shows the scale, your exact role and your autonomy. Be precise about the difference between deploying applications on Kubernetes and administering the clusters themselves: they are different levels of responsibility. Add figures when they are accurate and not confidential: number of pipelines, services, clusters, environments, teams supported, deployment frequency or duration.

Achievement examples to adapt

Replace [X] and [Y] with your own verified figures, or leave the line out if you cannot support it. When a result was achieved by the team, say that you contributed to it.

• Cut average pipeline duration from [X] to [Y] minutes by [caching dependencies / running tests in parallel].
• Reduced the time to provision a new environment from [X] to [Y] with reusable Terraform modules.
• Migrated [X] Jenkins jobs to [GitLab CI / GitHub Actions] with shared templates, removing [Y] redundant jobs.
• Containerised and moved [X] applications from virtual machines to Kubernetes.
• Contributed to reducing deployment-related incidents by [X]% over [period] through automated pre-production checks.
• Identified [X]% of cloud spend on unused or oversized resources and set up automatic shutdown of non-production environments.

Tools and stack: show how you used them

A list of twenty logos tells a recruiter little. Name the tools you have actually used and, for the ones that matter for the role, say what you did with them. A grouped stack is easy to scan:

Cloud: AWS (EC2, VPC, IAM, RDS, S3)
Containers: Docker · Kubernetes · Helm
Infrastructure as Code: Terraform · Ansible
CI/CD: GitLab CI · Jenkins
Observability: Prometheus · Grafana
Scripting: Bash · Python

Then give context in your experience section. This is more informative than:

Kubernetes: expert
AWS: expert
Terraform: 5/5

Name the cloud services you use rather than a whole provider catalogue, and state your main provider honestly: “mainly AWS, with some Azure projects” is more credible than “multi-cloud expert”. Do not list a tool you have only tried in a tutorial; if it comes from a personal lab, present it as such.

Education and qualifications

On your CV, use the format qualification – specialism – institution – year:

[Degree] – [computer science / networks and systems / cloud]
[Institution] — [year]

Cloud and Kubernetes certifications can support a profile. List only those you have actually obtained, with their exact title and year, and keep them relevant to the role. They do not replace production experience: recruiters still want to know what you have deployed and run.

If you are experienced, your recent stack and achievements matter more than your degree, which can move to the end of the CV.

Making your DevOps engineer CV easy to read for ATS

Many employers use an applicant tracking system (ATS) or recruitment software to store and search applications, often by technology. The aim is not to “beat” or trick an ATS: it is to make sure your key information is extracted correctly and easy to find.

• an explicit job title that names your main stack;
• clearly identifiable employers and dates;
• experience organised role by role;
• tools written as text, not only as logos or rating bars;
• tool names spelled as the industry writes them (Kubernetes, Terraform, GitLab CI);
• certifications with their exact titles.

When a job ad asks for a technology you genuinely use, use its vocabulary. If your CV only says “automation” while you actually write “Terraform modules and Ansible roles”, the second phrasing is more precise for both the software and the recruiter.

Tailoring your DevOps engineer CV to each job

Tailoring helps, because DevOps job ads lean in very different directions. Your background does not change, but you can bring forward the experience most relevant to the job’s main focus.

Before applying for a Kubernetes, cloud or CI/CD role, it helps to see which requirements of the job description your CV already covers and which are missing. CVReader compares your CV with a job description and highlights the points of correspondence.

Compare my CV with a job description

Free matching requires an account.

Junior DevOps engineer or career changer

With little DevOps experience, the same principle applies: be precise about what you have actually done.

• Students and recent graduates: describe internships and work-study placements like real jobs, with pipelines, tools and environments.
• Systems administrators: bring forward Linux, scripting, monitoring and incident work, then show your progress on Git, CI/CD, containers and infrastructure as code.
• Developers: your experience of build processes, Git and debugging is an asset; add the infrastructure, cloud and operations work you have done.
• Personal projects: a documented lab (cluster, pipeline, Terraform, monitoring) can show skills, as long as you present it as a personal project and not as production infrastructure.

Systems administrator moving into DevOps. Four years administering Linux servers and automating tasks in Bash; recently containerised two internal tools with Docker and built their GitLab CI pipelines. Personal Kubernetes and Terraform lab documented on [GitHub].

Trained or working in France?

If your background is French, a few adjustments make your CV clearer to English-speaking recruiters.

French qualifications

Keep the French name of your qualification and add a short explanation, without claiming an equivalence with British, American or other degrees:

• Diplôme d’ingénieur: a French engineering degree, generally awarded after five years of higher education.
• Master: keep the French specialism name and add a short translation of the field, for example “networks and systems”.
• Alternance: a French work-study programme; describe it as a work-study placement or apprenticeship and treat it as real experience.

Diplôme d’ingénieur – [specialism] (French engineering degree, five years of higher education)
[School] — [year]

French job titles

Translate the role, not the words. An “ingénieur systèmes” is usually a systems engineer or systems administrator depending on the work; “exploitation” is best described as operations, and an “astreinte” is an on-call rotation. If your contract was with a consultancy (“ESN”), say you were a consultant placed with a client and describe the client’s environment.

Mistakes to avoid and final checklist

Listing every technology you know

A long list hides your real stack. Show the tools you use in production, with context.

Writing “Kubernetes” without saying your level

Deploying applications and administering clusters are different responsibilities. Say which one you do.

Borrowing a title you have not held

Do not call yourself SRE, DevSecOps or multi-cloud expert unless your work matches it.

Giving no results

DevOps work lends itself to measurable effects: deployment time, provisioning time, incidents, manual steps removed.

Using a layout that hides information

Logo walls and rating bars should never replace job titles, employers, dates and written skills.

Translating job titles word for word

If your experience is in another language, translate the role, not the words, and keep qualification names in their original language with a short explanation.

Checklist before you apply

• My title names my main stack and, if useful, my level of experience.
• My summary fits in three to five lines and contains facts, not adjectives.
• Each role shows context, my own actions, tools, scale and, where possible, a result.
• Every figure is accurate, verifiable and not confidential.
• Each tool listed is one I have actually used, and I can discuss it in an interview.
• Certifications are listed with their exact titles, only if obtained.
• Employers and dates are easy to find, and skills are written as text.
• I have brought forward what matches the job’s main focus.

DevOps engineer CV: frequently asked questions

What skills should I put on a DevOps engineer CV?

Choose skills you genuinely use and that match the role: your main cloud provider, Linux, CI/CD, Docker, Kubernetes, infrastructure as code, scripting and observability, each placed in context in your experience.

Should I list every DevOps tool I know?

No. Focus on the tools you have used for real, ideally in production. A shorter, accurate stack is more convincing than a long list.

What is the difference between DevOps and SRE on a CV?

The roles overlap, but SRE positions usually focus more on reliability, availability targets, incidents and capacity. Scopes vary between companies, so use the title that matches your real responsibilities.

Is a DevOps engineer resume different from a DevOps engineer CV?

“Resume” is the usual American term; “CV” is used in the UK and much of the world. For a job application, the advice in this guide applies to both.

Which figures should I put on a DevOps CV?

Numbers of pipelines, services, clusters or teams supported, and changes in deployment time, provisioning time or incidents, as long as they are accurate and you can explain your part in them.

Should a DevOps engineer CV fit on one page?

There is no absolute rule. A junior profile often fits on one page. An experienced engineer can use two pages if the extra information is genuinely relevant.