cvharbor editorial

DevOps, SRE or platform engineer: which title belongs on your resume

DevOps engineer, site reliability engineer and platform engineer describe overlapping work, and employers use the labels inconsistently enough that no definition settles it. What matters for your resume is narrower: which one gets you read for the jobs you want.

There is a genuine distinction between these roles and there is also an enormous amount of overlap, and which one dominates depends entirely on the company. A site reliability engineer at one organisation does work that another calls platform engineering. A DevOps engineer at a fifty-person startup does all three jobs. Arguing about the correct definitions is a decent conference talk and a waste of time when you are deciding what to write at the top of a CV.

The resume question is more tractable: recruiters search by title, hiring managers read a title as a claim about your centre of gravity, and you need the one that lands you in the right pile without misrepresenting what you have done.

What the three titles usually mean

Usually, not always. Treat these as the median case and expect individual employers to deviate.

DevOps engineer

The broadest label and the most common. Typically spans CI/CD, infrastructure automation, cloud provisioning and deployment. Often the only infrastructure person or one of a few. At smaller companies it means everything that is not writing product code.

Site reliability engineer

Reliability is the product. SLOs and error budgets, observability, incident response, capacity planning, postmortems. Usually implies a software-engineering bar — SRE interviews frequently include coding rounds that DevOps interviews do not. Concentrated at larger companies with enough scale for reliability to be a discipline of its own.

Platform engineer

The newest of the three and the fastest-growing. Internal developer platforms: paved paths, self-service infrastructure, golden templates. The customer is your own engineering organisation, and the work is treated as a product with users rather than as tickets.

Choosing based on where you want to go, not where you have been

Your title on a resume is a positioning decision within the bounds of the truth. You cannot invent a title you never held — that is checkable — but you have real latitude in your summary, your section headings, and how you describe your own focus.

• Targeting SRE roles: lead with reliability. SLOs you defined, incidents you owned end to end, observability you built, capacity work you did. If your background is infrastructure-heavy, be ready for the coding round.
• Targeting platform roles: lead with the internal-customer framing. What you built for other engineers, adoption of it, what it replaced, how you gathered requirements from your own developers.
• Targeting DevOps roles: breadth is the asset rather than a lack of focus. End-to-end ownership from commit to production is the thing to show.
• Genuinely open: use the title you actually held and let the summary do the positioning. It is the honest default and it costs you nothing.

Neither of those is the wrong version. They are the same person describing the same two years to different audiences, and each one leads with what that audience screens for.

What to do when your actual title was something else

Plenty of people do this work under titles like Systems Engineer, Infrastructure Engineer, Cloud Engineer, or just Software Engineer. Do not rewrite history. The convention that reads as honest is to keep the real title and clarify alongside it.

• Keep the official title as it appears in employment records, then add a parenthetical: "Systems Engineer (platform and CI/CD)".
• Let the summary state your focus in the vocabulary you are targeting, since the summary is your description rather than the employer’s.
• If your internal title was non-standard — "Infrastructure Ninja" and similar — the parenthetical is doing necessary work, not decoration.

Titles are a search problem too

Recruiters search by title string, and a resume that never contains the word "SRE" is unlikely to surface in a search for SREs even when the experience is a perfect fit. This is the practical argument for making sure the vocabulary you are targeting appears somewhere true in the document — in your summary, your skills section, or a parenthetical — rather than relying on a reader to infer it.

Do not solve this by listing all three titles at the top of your resume. "DevOps / SRE / Platform Engineer" reads as someone who has not decided, and it makes the strongest version of your experience harder to find rather than easier.

See how your experience reads against a specific posting before you commit to a framing. Check the fit