Is Marisol Trenchard a real engineer

No. She is invented for this page, and so are Pellworth Health and Ovingdean Systems. The figures show a shape and describe nobody's career.

What is the strongest DevOps line

The one about on-call. Incidents per engineer falling from six to two a month across nine teams is a change to other people's lives, and it is the result a platform lead is hired to produce.

Should I list every cloud service

No. Ten skills, and the ones that matter appear again inside an achievement line where they are attached to an outcome. A list of forty services reads as a list of forty tutorials.

What did the checker score it

98 out of 100, re-measured on 25 September 2026, with readable volume 4 points short. The arithmetic is 100 × 30% for parseability + 100 × 30% for completeness + 96 × 40% for content. The writing check beside it scored 95, which is 91 of the 96 points that applied, and the five it withheld are the bullet tense rule.

Is a cost saving safe to publish

A percentage usually is; an absolute cloud bill usually is not. Right-sizing 260 workloads for a 29% reduction makes the point without publishing a former employer's spend.

Which design is this rendered in

Architect, one of the eight layouts in the ATS family. The eight were chosen from a measurement taken on 2026-09-14: each exports a PDF whose text layer scores exactly what the pasted text scores, on both test documents, in one column, with the reading order kept and no graphics. Its single column and tight rhythm suit a page of short technical lines.

Example · Platform

A free DevOps engineer résumé example, measured in deploys and pages

One complete DevOps engineer résumé, written out in full. The person is invented. The reading and the score come from the product itself.

ConxfolioPublished 2026-09-13 · updated 2026-09-25

— on-call load is a result. say what it was before.

The DevOps engineer example résumé drawn as a complete page in the Architect design: name, summary, three dated roles with five achievement lines under each, education and a skills row — The example below, drawn by the builder's own renderer in the Architect design. The picture was taken by pressing this page's own Use this example door and photographing what the editor rendered.

Platform work is judged by how much friction it removed, and that is measurable in ways most DevOps résumés never use. This example is written out in full so you can read those measures, then put through the tools here so you can see what software takes from them. The candidate is invented.

The example, in full

An invented person. Not a real document, and not yours.

Marisol Trenchard
DevOps Engineer
Barcelona, Spain · [email protected] · +34 93 555 0187

Summary
Site reliability and platform engineer with seven years on build systems and production infrastructure in Spain, working on deploy speed, on-call load and the paved road forty services now ship through.

Experience

Senior DevOps Engineer · Pellworth Health, Barcelona · 2021 to present

Cut deploy time by 84% across 40 services and raised the release rate from 12 to 90 deployments a week.
Reduced infrastructure spend by 29% a year by right-sizing 260 workloads and deleting 40 environments that no team had used since 2020.
Rebuilt the on-call rota so incidents for each engineer fell from 6 to 2 a month across 9 product teams.
Migrated 40 services onto a single deployment pipeline over 11 months with no customer-facing outage recorded in that whole period.
Wrote the incident review process the whole engineering group follows and ran 30 reviews in 2 years without a repeat cause.

Platform Engineer · Ovingdean Systems, Valencia · 2018 to 2021

Built the continuous integration platform that ran 2 800 builds a day for 14 teams across 3 years of daily use.
Halved the average build from 21 minutes to 9 by caching dependencies and splitting the tests across 8 runners for 14 teams.
Wrote the infrastructure modules that 14 teams used for 3 years and versioned every change behind a written upgrade note.
Automated 300 manual server changes into 40 repeatable jobs and returned 20 hours a week to a team of 5 engineers.
Monitored 200 production alerts a week and removed 120 of them that no engineer had ever acted on in 2 years.

Junior Systems Engineer · Ovingdean Systems, Valencia · 2017 to 2018

Maintained 60 Linux servers across 2 data centres and closed 400 support tickets in a single year without an escalation.
Scripted 40 routine operations tasks in Python and cut the weekly maintenance window from 6 hours to 2 across 9 sites.
Patched 200 machines a month against the security baseline and reported every exception to the platform lead the same day.
Documented 30 runbooks for the on-call rota and answered 90 questions from 6 engineers about them in the first year.
Restored service on 20 production incidents inside the agreed 30 minute target and logged each cause for the weekly review.

Education
BSc Software Engineering · Montjuic Polytechnic, Barcelona · 2014 to 2018

Skills
Kubernetes, Terraform, AWS, CI/CD, observability, incident response, Go, Python, cost optimisation, platform engineering

Languages
Spanish · native · Catalan · native · English · C1

Four numbers describe a platform

Deploy time down 84% across forty services. Releases from twelve to ninety a week. Infrastructure spend down 29% across 260 workloads. Incidents per engineer from six to two a month. Each of those is a measured change with its scope attached, and together they describe a platform team that changed how a company ships.

The migration line carries the risk half: forty services onto one pipeline with no customer-facing outages. A platform engineer who has moved forty services without breaking anything is making a claim about care, and the absence of an incident is the evidence for it.

Build times are the line juniors should copy

Two thousand eight hundred builds a day, average build from 21 minutes to nine by caching and parallel test shards. It names the volume, the improvement and the method in one sentence, and every engineer reading it knows exactly what work that was.

The modules line is the quiet one: infrastructure modules used by fourteen teams for three years. Longevity is a result. Something other teams still depend on after three years is a stronger signal than a migration that was reversed.

Skills for a DevOps résumé, grouped

Marisol's skills fall into infrastructure, delivery and operations. Infrastructure: Kubernetes, Terraform, AWS, platform engineering. Delivery and code: CI/CD, Go, Python. Operations: observability, incident response, cost optimisation. An SRE or platform lead reads the operations group as proof you have been on call and learned from it.

If you hold a cloud certification, list it in certifications with the year rather than in the skills row. The free résumé builder lets you group skills under names you choose and move any skill with one click.

From systems engineer to senior DevOps

A junior systems résumé proves you keep things running: tickets closed, patches applied, a build that became reliable. The build-time line from the Ovingdean junior role is the one to copy early on, because it is measurable and it is yours.

Platform and senior roles move to the numbers that describe a platform: deploy frequency, lead time, availability, spend. Add the engineers who use what you built, since adoption is the proof a platform works. The bullet guide shows the verb, figure and result pattern.

How it reads and scores

The import review read three dated roles with five lines under each, one degree, ten skills and three languages. The ATS checker scored it 98 out of 100, re-measured on 25 September 2026, with readable volume 4 points short: 100 × 30% for parseability, 100 × 30% for completeness and 96 × 40% for content. The writing check scored it 95, which is 91 of the 96 points that applied here. How our examples are made explains the import review and the scoring behind these figures.

The Conxfolio import review after the door opened, showing Marisol Trenchard's example read into fields beside the rendered page, with the line saying it is an example — Marisol Trenchard's devops engineer résumé read into fields, each field beside the line it came from.

The same import review on a 390 pixel phone screen, with the example notice above the accept button — Marisol Trenchard's devops engineer résumé in the same review on a 390 px phone.

What this example leaves off

No certification list, no cluster counts without context and no uptime figure quoted as nines without saying what was measured. An availability number is only useful beside the thing it describes, and a naked string of nines invites the question rather than answering it.

Tool inventories are left off as well. A platform engineer is hired for what happened to deploy time, spend and on-call load, and a list of thirty tools is usually where a page goes when those three numbers are missing.

What to change for your own

Change the platform and keep the four numbers. Bare metal, managed Kubernetes, serverless and hybrid estates all use this shape. Then put your own deploy times, release counts, spend changes and on-call load in, and state what each was before.

Keep one longevity line. Keep the languages if you work across borders. The design gallery holds 37 layouts, and the data engineer example, the QA engineer example and the product manager example sit beside this one.

Write yours beside it

Opens the builder with Marisol's example loaded, saved as its own entry in the Architect design. Replace every line with your own. Free, no account.

Use this example Check a résumé instead

Questions

Is Marisol Trenchard a real engineer: No. She is invented for this page, and so are Pellworth Health and Ovingdean Systems. The figures show a shape and describe nobody's career.
What is the strongest DevOps line: The one about on-call. Incidents per engineer falling from six to two a month across nine teams is a change to other people's lives, and it is the result a platform lead is hired to produce.
Should I list every cloud service: No. Ten skills, and the ones that matter appear again inside an achievement line where they are attached to an outcome. A list of forty services reads as a list of forty tutorials.
What did the checker score it: 98 out of 100, re-measured on 25 September 2026, with readable volume 4 points short. The arithmetic is 100 × 30% for parseability + 100 × 30% for completeness + 96 × 40% for content. The writing check beside it scored 95, which is 91 of the 96 points that applied, and the five it withheld are the bullet tense rule.
Is a cost saving safe to publish: A percentage usually is; an absolute cloud bill usually is not. Right-sizing 260 workloads for a 29% reduction makes the point without publishing a former employer's spend.
Which design is this rendered in: Architect, one of the eight layouts in the ATS family. The eight were chosen from a measurement taken on 2026-09-14: each exports a PDF whose text layer scores exactly what the pasted text scores, on both test documents, in one column, with the reading order kept and no graphics. Its single column and tight rhythm suit a page of short technical lines.

Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 22 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.