What to Put on a Cloud Engineer CV: Sections, Content, and Mistakes

Mandatory vs optional sections

Not every section belongs on every cloud engineer CV. What you need depends on your experience level and background. Here is a clear breakdown:

Always include

• Contact details and header — your name, location, email, phone, and relevant professional links
• Technical skills — a grouped list of your cloud platforms, tools, languages, and frameworks
• Work experience — every substantive role in reverse chronological order
• Certifications — all current, valid certifications with full names and dates

Include if relevant

• Profile summary — two to four sentences; most useful for career changers, juniors explaining their path, or engineers with an unusual profile
• Projects — essential for juniors and self-taught engineers; optional for mid-level and senior engineers with strong experience sections
• Education — always include; adjust how much space it gets based on how long ago it was
• Open source contributions or publications — only if genuinely substantial

Rarely useful

• Hobbies and interests — relevant only if they directly demonstrate cloud or technical skills (home lab, open source contributions, technical writing)
• References — employers know references exist; listing “available on request” takes up space and adds nothing
• Objectives — usually covered better by a profile summary; standalone objectives tend to be generic

Section by section: what goes where

Contact details

Include: full name, city (not full postal address), email, phone number, LinkedIn URL, GitHub URL (only if the profile is presentable).

Do not include: a photo, date of birth, or home address. These are unnecessary in the UK, EU, and US hiring contexts and can cause issues for employers.

Profile summary

Two to four sentences. State your technical background, your main tools or specialisation, and what you’re looking for. Write it as a factual professional statement, not marketing copy.

Useful for: career changers who need to explain their transition, juniors who want to contextualise their path, engineers returning after time away.

Skip it if: your experience section clearly speaks for itself and you find yourself writing generic filler.

Technical skills

A grouped list of your cloud platforms, infrastructure tools, CI/CD systems, monitoring tools, and scripting languages. Use category labels. Do not list tools you could not discuss in an interview.

Position: typically after the summary, before the experience section. It gives the reader technical context before they read your bullet points.

Full guidance: how to write the skills section on a cloud CV.

Work experience

The most important section for anyone with professional experience. Each role includes job title, company, dates, and two to five bullet points. Bullets should describe outcomes and specific work, not generic responsibilities.

For juniors: focus on extracting cloud-relevant work from any role, even if the title wasn’t cloud-specific.

For mid-level and senior: each bullet should demonstrate ownership, decision-making, and concrete outcomes — not just activity.

Projects

Essential for junior and self-taught candidates. Each entry includes what was built, the technologies used, what it demonstrates, and a GitHub link if the repo is presentable.

Position: before work experience for juniors whose projects are stronger than their employment history; after work experience for mid-level engineers.

Full guidance: how to write the projects section on your cloud CV.

Certifications

List all current, valid certifications with the full official name, issuing organisation, and date passed. Do not list expired certifications as current. Do not use abbreviations alone.

Position: near the top for juniors (after skills); below experience for mid-level and senior engineers.

Full guidance: how to list certifications on your cloud CV.

Education

One or two lines per qualification: degree title, institution, year completed. For recent graduates (within two years), education can appear higher up the CV. For anyone with more than two years of work experience, education belongs near the bottom.

Skip module descriptions. Hiring managers do not read them. The degree name and institution are what matter.

Recommended section order by experience level

The order of sections signals what you consider most important. These are the patterns that work best for each stage:

Junior cloud engineer (0–2 years)

1. Contact details
2. Profile summary
3. Technical skills
4. Certifications
5. Projects
6. Work experience
7. Education

Mid-level cloud engineer (2–5 years)

1. Contact details
2. Profile summary (optional)
3. Technical skills
4. Work experience
5. Projects (optional)
6. Certifications
7. Education

Senior cloud engineer (5+ years)

1. Contact details
2. Profile summary
3. Technical skills
4. Work experience
5. Certifications
6. Education

The most common mistakes

Listing skills you cannot discuss in an interview

This is the most common mistake on cloud CVs. Listing every tool you’ve seen in a tutorial invites interview questions you cannot answer. It also makes the skills section noisy and reduces the signal from the tools you genuinely know.

Experience bullets that describe the job rather than your contribution

Writing “Responsible for cloud infrastructure management” is not an experience bullet — it is a job description. Hiring managers want to know what specifically you did, what you changed, and what the outcome was.

Putting certifications before experience when your experience is more impressive

A mid-level engineer with two years of AWS EKS production experience who leads their CV with certifications is selling themselves short. Let your experience lead.

Using the same CV for every application

A minor tailoring effort — matching the language of the job description where honest, moving relevant tools higher in your skills section — improves both ATS matching and the hiring manager’s first impression. It doesn’t take long and it matters.

Including content from more than ten to fifteen years ago

A cloud engineering CV is not a complete employment history. Roles from a decade or more ago rarely add value unless they are directly relevant. Condense very old experience to a single line or remove it.

A quick cut list

If any of the following are on your CV, remove them:

• “References available on request”
• Full postal address
• Date of birth or age
• Photo (unless you’re in a market where this is conventional)
• Hobbies and interests (unless they demonstrate relevant technical skills)
• Soft skills listed as standalone items (“communication,” “teamwork”)
• Expired certifications listed without noting expiry
• Certification abbreviations without full names (“AWS SAA” alone)
• Generic objective statements
• Module descriptions for a degree completed more than two years ago