Cloud CV Cheatsheet: What to Include and What to Avoid
A cloud CV has one job before anything else: get you through the screening stage. That means a recruiter or hiring manager who may spend 30 seconds on the first pass can immediately see that you have relevant skills and something real to show. Everything else is secondary.
This cheatsheet is a fast reference for what to include, how to write it, and what to cut.
Must-Have Checklist#
Before you send a CV, verify each of these:
- Clear role title at the top (Cloud Engineer, DevOps Engineer, Platform Engineer — be specific)
- Skills section listing cloud platforms, tools, languages — organised so it can be scanned in seconds
- Certifications listed with full official name, issuing body, and year obtained or expiry year
- Experience bullets that describe outcomes, not just responsibilities
- Projects section (essential if you have limited work experience)
- GitHub link if it contains real, public work
- Contact info: professional email, LinkedIn URL, GitHub URL, city/country
CV Sections Reference#
| Section | Required or optional | Notes |
|---|---|---|
| Contact info | Required | Email, LinkedIn, GitHub, location. No phone unless standard in your region. |
| Role title / headline | Required | Be specific. “Cloud Engineer” or “DevOps Engineer” is better than “IT Professional”. |
| Skills | Required | List platforms, tools, languages. Group them logically. Skip skill bars or percentages. |
| Experience | Required if you have it | Bullet point achievements. Action verb + what + measurable outcome. |
| Projects | Required if limited experience | Real work. Link to GitHub. Describe what it demonstrates technically. |
| Certifications | Required if you have them | Full official names, not abbreviations. Include provider and year. |
| Education | Required | Keep it brief. Not the focus for most cloud roles unless recently graduated. |
| Summary / profile | Optional | Only include if it says something specific and relevant. Skip generic objectives. |
How to Write Good Experience Bullets#
Use this formula: action verb + what you did + measurable result
The result does not have to be a percentage — it can be a time saved, a problem solved, or a scale reached. Anything concrete is better than nothing.
Bad: “Worked with AWS”
Good: “Deployed containerised microservices to AWS ECS using Terraform, reducing deployment time from 2 hours to 12 minutes”
Bad: “Responsible for monitoring”
Good: “Configured Prometheus and Grafana dashboards for a 12-service Kubernetes cluster, reducing mean time to recovery from 40 minutes to under 10”
Bad: “Helped the team with infrastructure tasks”
Good: “Migrated three legacy EC2-based services to AWS Lambda, cutting infrastructure cost by 60% and removing the need for patching those instances”
Bad: “Used CI/CD pipelines”
Good: “Built a GitHub Actions pipeline that ran unit tests, built a Docker image, pushed to ECR, and deployed to ECS on every merge to main — cutting manual deployment steps from 7 to 0”
If you are struggling to write outcome bullets because your role was purely task-based, think about: did anything you do speed something up? Make something more reliable? Reduce manual work? Even small improvements count.
What NOT to Put on a Cloud CV#
Every technology you have ever touched. A skills list with 40 items and no depth is a red flag. List things you can genuinely discuss in an interview.
Skill bars or star ratings. “Python ★★★☆☆” means nothing to a hiring manager. Cut them entirely.
Generic objectives. “Seeking a challenging role where I can grow and contribute to a dynamic team” says nothing. If you include a summary, make it role-specific.
Task-list bullets with no outcomes. “Managed EC2 instances” or “Monitored system performance” does not tell anyone what you actually did or what impact it had.
Acronyms without meaning. SDLC, AGILE, JIRA — these can be mentioned in context but listing them as standalone skills signals filler content.
Outdated or irrelevant experience. A 2010 Windows Server admin role does not need 5 bullet points if you are applying for a cloud engineering role in 2026.
How to List Certifications#
Use the full official name — not abbreviations. Abbreviations alone are meaningless to automated screening tools and to any recruiter who is not deeply technical.
| Do this | Not this |
|---|---|
| AWS Certified Solutions Architect – Associate (Amazon Web Services, 2025) | AWS SAA-C03 |
| Google Cloud Associate Cloud Engineer (Google, expires 2027) | GCP ACE |
| HashiCorp Certified: Terraform Associate (003) (HashiCorp, 2025) | Terraform cert |
| Certified Kubernetes Administrator (CNCF, 2025) | CKA |
List certifications in a dedicated section, ordered by relevance or recency.
How to Present Projects#
Projects are especially important if you are entering cloud from another field or do not have direct commercial cloud experience. Each project entry should include:
- Project name — give it a simple, descriptive name
- Brief description — one or two sentences on what it does
- Technologies used — specific tools, not generic terms
- What it demonstrates — the cloud skill it proves
- Link to repository — a public GitHub repo with a decent README
Example:
Cloud Infrastructure Lab — Deployed a three-tier web application (VPC, EC2, RDS, ALB) on AWS using Terraform, with a GitHub Actions pipeline for infrastructure updates. Demonstrates hands-on IaC, cloud networking, and CI/CD automation. [github.com/yourname/cloud-infra-lab]
One Page or Two?#
- Under 5 years of relevant experience: aim for one page
- More than 5 years of relevant experience: two pages is fine
- Never pad content to fill space; never cut important content to hit one page if it makes the CV worse
Tailoring Your CV#
Check the job specification for the cloud provider and tools the role uses. Mirror that language in your CV where it is honest to do so. If the role mentions Azure and you have AWS experience, you can note that — but if you have any Azure experience, make sure it appears clearly.
Applicant tracking systems often filter by keywords. If the job spec says “Terraform”, “Kubernetes”, and “Azure DevOps” and none of those appear in your CV, it may not make it past automated screening even if you are a strong candidate.