Cloud / DevOps Engineer CV example
Experienced · UK CV · set in the Modern template
Platform and DevOps roles are judged on reliability, speed and cost. The CV should show the systems you run, how you made them more reliable or cheaper, and the incidents you handled. Certifications help get past a screen; outcomes get the interview.
A sample person: the name, employers and figures are invented. A platform engineer who moved a bank’s services to Kubernetes and cut deployment time, applying for a senior cloud role.
The order, and why
A short profile; experience; certifications in their own section; education; skills grouped by platform.
Weak bullets, made strong
Weak: Managed Kubernetes clusters
Strong: Migrated 85 services to Kubernetes on AWS, cutting deployment time from 2 hours to 9 minutes and releases from weekly to daily
Scope, platform and the delivery metrics that moved.
Weak: Reduced cloud costs
Strong: Cut monthly AWS spend by £38K (22%) through rightsizing and spot instances, with no change to SLOs
The amount, the method and the guardrail.
Mistakes to avoid
- A list of tools with no systems or outcomes.
- Omitting incident work, which is where judgement shows.
- Certifications only, with no evidence of running anything.
UK CV or US resume
UK: two pages is acceptable at this level. US: one page; list certifications in one line.
Live cloud and devops roles
Open now on the tracker, with their deadlines.
- Google STEP Software Engineering Intern (1st & 2nd year)
- Meta Software Engineer, University Grad
- Bloomberg Software Engineer Graduate
- Stripe Software Engineer, New Grad
- Jane Street Software Engineer