Junior Cloud Engineer CV: Example Structure and What to Include

The core challenge of a junior cloud CV

Most job advice assumes you have a solid employment history. A junior cloud engineer CV often doesn’t — especially if you’re a career changer or self-taught. The challenge is demonstrating capability through what you do have: certifications, self-built projects, training, and transferable experience from previous roles.

The goal is to give the hiring manager enough signal to invite you to interview. You don’t need to look like a mid-level engineer — you need to look like someone who can learn fast, has already started learning, and won’t be a liability in a technical environment.

Honesty matters here more than you might expect. Hiring managers who interview junior candidates are used to limited experience. What they’re not used to is being misled. A CV that overstates experience creates problems in interviews that cannot be recovered from easily.

Annotated example structure

Below is a realistic junior cloud engineer CV structure with commentary on each section. This is not a template to copy word for word — it is an example to understand how the sections work together.

Header

Alex Chen
Manchester | alex.chen@email.com | +44 7700 900123
linkedin.com/in/alexchen | github.com/alexchen-cloud

Commentary: City is enough — you don’t need a full address. Include LinkedIn and GitHub only if both are presentable. A GitHub with three empty repos is worse than no GitHub link.

Summary (2–3 sentences)

AWS-certified cloud practitioner with hands-on Terraform and Kubernetes projects and a background in network support. Currently completing the AWS Solutions Architect – Associate certification. Looking for an entry-level infrastructure or platform engineering role where I can grow alongside an experienced team.

Commentary: This summary is specific — it mentions the certification, the tools, the background, and the goal. It does not use vague phrases like “results-driven” or “passionate professional.” That kind of language is filtered out immediately.

Core skills

Cloud platforms: AWS (EC2, S3, IAM, VPC, RDS, Lambda)
Infrastructure as code: Terraform, CloudFormation
Containers: Docker, Kubernetes (minikube)
CI/CD: GitHub Actions
Scripting: Python (basic), Bash
Monitoring: CloudWatch, Prometheus (learning)

Commentary: The grouped format is easier to read than a flat comma-separated list. Note the “(basic)” and “(learning)” qualifiers — this is honest and much better than claiming full proficiency. Hiring managers will ask about listed skills. Only include what you can discuss.

Projects (place this before work history if your work experience is unrelated to cloud)

AWS Three-Tier Web Application | github.com/alexchen-cloud/aws-three-tier
Deployed a Python Flask application to AWS using Terraform. Architecture includes VPC with public and private subnets, ALB for load balancing, EC2 instances in an Auto Scaling Group, and RDS for database. CI/CD pipeline via GitHub Actions deploys to staging on pull request and to production on merge. README documents architecture decisions and teardown steps.

Kubernetes Home Lab Deployment | github.com/alexchen-cloud/k8s-lab
Built a local Kubernetes cluster using kind and deployed a containerised web application with health checks, resource limits, and ConfigMaps for environment management. Wrote manifests for Deployment, Service, Ingress, and HorizontalPodAutoscaler resources.

Commentary: Two solid, real projects are better than six shallow ones. Each project entry explains what was built, what technologies were used, and what engineering decisions were made. The GitHub links mean the hiring manager can actually look at the work.

Work experience

Network Support Technician — Nexus IT Solutions, Manchester
March 2022 – Present

• Managed network infrastructure for 40+ clients including firewall configuration, VLAN segmentation, and VPN setup
• Troubleshot connectivity issues across Windows Server and Linux environments, reducing average resolution time from 4 hours to under 90 minutes
• Supported migration of three clients to AWS, assisting with VPC setup and IAM policy configuration

Commentary: The role is not a cloud role, but the bullets extract the most relevant elements — networking, Linux, and actual AWS exposure. The metric (resolution time improvement) makes the experience feel concrete. The migration involvement is flagged because it’s directly relevant.

Certifications

AWS Cloud Practitioner (Amazon Web Services, October 2025)
HashiCorp Certified: Terraform Associate (HashiCorp, January 2026)
AWS Solutions Architect – Associate (in progress, expected April 2026)

Commentary: Full official names, dates, and issuing bodies. Noting an in-progress cert is fine — it signals what you’re actively working on. Don’t list certs you started but haven’t passed.

Education

BSc Computer Science — University of Sheffield, 2018–2021

Commentary: Brief. No module descriptions needed once you have work experience. If your degree is not in a technical field, still include it but keep it to one line.

Length and format for a junior CV

Aim for one page. If your projects section is genuinely substantial and takes the CV slightly over one page, two pages is acceptable — but do not pad to fill space. A tight, one-page CV that says something real is better than a two-page CV with repeated phrases and empty bullet points.

Use a clean, plain layout. Standard fonts (Calibri, Arial, Helvetica), 10–12pt body text, and clear section dividers. Avoid coloured headers, skill bars, infographic-style layouts, and multi-column formats — these can confuse ATS systems and often look more cluttered than professional.

Send the CV as a PDF so it renders consistently on every system.

Common mistakes in junior cloud CVs

Listing tools without context

Writing “AWS, GCP, Azure, Kubernetes, Terraform, Ansible, Docker, Jenkins, Python, Go” in your skills section looks impressive until someone asks you a question about any of them and you cannot answer with depth. List what you know well enough to discuss. If you’ve only done tutorials on something, it does not belong in your skills section yet.

Putting certifications at the top when you have good projects

A common mistake is structuring the CV as: contact details → certifications → skills → projects. The certifications end up at the top because they feel like the most impressive thing. But a hiring manager who can see a real AWS project will find that more credible than a certification. Lead with what demonstrates capability.

Describing tutorials as projects

Following a course that walks you through deploying an EC2 instance is not a project — it is a tutorial. If the architecture decisions, the code, and the README were mostly someone else’s, it belongs in your learning notes, not your CV. Hiring managers can tell, and more importantly, you will be asked about it in an interview and struggle to answer questions that go beyond the tutorial’s scope.

Including everything you’ve ever touched

A CV that lists 40 technologies across three pages for a candidate with one year of experience signals unfamiliarity with how hiring works, not impressive breadth. Tighter and more credible is better.

What employers actually want from junior candidates

At the junior level, employers are not expecting deep expertise. They are looking for evidence of three things:

• You can learn independently. Self-built projects, certifications, and a clear learning path show this better than a degree alone.
• You can think technically. The ability to explain how your project works, what went wrong, and what you would do differently signals genuine understanding.
• You won’t break production. Some awareness of production environments, error handling, security basics, and the difference between “it works on my machine” and “it works reliably” goes a long way.

The CV does not need to prove all of this on its own — it just needs to be strong enough to get the interview. The interview is where you demonstrate the detail.

If you are not sure whether your CV is ready to submit, the question to ask is: “Could a hiring manager reading this CV have a 30-minute technical conversation with me based on what is written here?” If the answer is yes, you are probably ready.

Getting your CV in front of people

For junior cloud engineering roles, where you apply matters as much as how your CV is written. See the best job boards for cloud roles for a breakdown of where junior roles are posted and which platforms are worth prioritising.

Also consider how to apply for cloud jobs without experience — it covers the specific challenges that come before the CV is even seen, including getting past screening tools that filter for years of experience.