For students and early-career professionals

Cloud Engineer

Designs and operates cloud infrastructure used to run apps and store data.

12 chapters · About 3 months · 15–30 min a day

Start this plan free →

Chapter 1 is free.

Skills

14 skills, and what you'll learn in each

Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.

Core to the job

Chapter 2

Cloud platforms

Read a cloud bill and find which services cost most

What you'll learn

  • Core cloud services
  • Identity and permissions
  • Service tradeoffs
  • Cloud cost drivers
  • Well-Architected review

Practice

  • Find 3 wasted cloud resources from a sample bill20 min
  • Forecast capacity for a growing service25 min
  • Split ten cloud failures between the provider and you15 min

Chapter 2

Infrastructure as code

Read server-building code and find where the real setup differs

What you'll learn

  • Desired state
  • Plan diff
  • State file
  • Module boundary
  • Configuration drift

Practice

  • Read a Terraform Config and Describe What It Builds15 min

Chapter 2

Networking fundamentals

Trace a web request and write rules for app connections

What you'll learn

  • Request path
  • Subnet range
  • Network layers
  • Network access controls
  • Cloud network placement
  • Joining networks

Practice

  • Place a three-tier app into a cloud network and write the rules between the parts25 min
  • Find the three rules that let too much in20 min

Chapter 3

Access management

Choose the least access that works and flag broad permissions

What you'll learn

  • Identity and access
  • Least privilege
  • Role-based access
  • Multi-factor authentication
  • Federation trust
  • Access audit

Practice

  • Audit a sample IAM permissions set20 min
  • Evaluate an Urgent Access Request Using Least Privilege15 min

Chapter 3

Security fundamentals

Spot phishing emails and fix a system's weak security settings

What you'll learn

  • CIA triad
  • Least privilege
  • Defense in depth
  • Attack surface

Practice

  • Check your own laptop against a basic hardening checklist25 min

Chapter 6

Git

Save clear changes to a project's history and request review

What you'll learn

  • Change states
  • Short-lived branches
  • Merge conflict
  • Useful commit message
  • Pull request review

Practice

  • Practise a small Git branching workflow30 min

8 more in the plan

Automation mindsetPitch automating a repetitive task, naming its benefit and limitsCh 6

What you'll learn

  • Toil test
  • Automation value
  • Safe defaults
  • Maintenance cost

Practice

  • Pitch an Automation Idea for a Repetitive Process30 min
LinuxManage files and who can open them using short commandsCh 6

What you'll learn

  • Filesystem map
  • File permissions
  • Pipes and filters
  • Process signals

Practice

  • Complete 10 Linux File and Permission Tasks20 min
  • Solve 5 Linux command-line puzzles25 min
Incident responseBuild an incident timeline from logs and write plain updatesCh 7

What you'll learn

  • User impact first
  • Mitigate before root cause
  • Blameless post-mortem
  • Incident command roles

Practice

  • Write a blameless post-mortem for a small incident30 min
Problem solvingTest each possible cause of a problem instead of guessingCh 7

What you'll learn

  • Problem vs symptom
  • Clean problem splits
  • Root cause
  • Deciding under uncertainty
Troubleshooting systemsWork through a website fault in order instead of guessingCh 7

What you'll learn

  • USE method
  • Testable hypothesis
  • One variable
  • Symptom timeline

Practice

  • Walk Through a Systematic Website Troubleshooting10 min
CommunicationRewrite an update for two different readers, cutting extra linesCh 8

What you'll learn

  • Lead with the point
  • Match detail to the reader
  • Said versus heard
  • Specific feedback

Practice

  • Write a Six-Line Delay Message10 min
Working with othersContribute to group work, ask for help and credit teammatesCh 8

What you'll learn

  • Early team friction
  • Clear ownership
  • Challenge ideas, not people
  • Lead or follow

Practice

  • Write a Request That Makes It Easy to Say Yes10 min
Adapting to changeTry a new tool and describe how you handled changeCh 8

What you'll learn

  • Change vs your response
  • The messy in-between
  • Not there yet
  • Real change vs a feeling

Your plan

Chapter by chapter.

12 chapters, in this order. Chapter 1 is free.

1~1 wk

See what cloud engineer work involves

StartFree
2~1 wk

Set up cloud networks from code

Skills
3~1 wk

Control who can reach your systems

Skills
41–2 wks

Build a Terraform setup with safe teardown

Project
5~1 wk

Talk to a working cloud engineer

People
6~1 wk

Automate repeat tasks and track changes

Skills
7~1 wk

Handle incidents and narrow down the cause

Skills
8~1 wk

Communicate and work together through change

Skills
91–2 wks

Capstone: build a pipeline that tests every commit

Project
10~1 wk

Answer the questions interviewers ask

Interview
11~1 wk

Decide how you will get in

Decide
12on your timeline

Send your first applications

Apply

The job

What a Cloud Engineer does

Builds and runs cloud systems so teams can deploy apps safely, scale smoothly, and keep data available.

The work

  • Design cloud networks, compute, storage, and access controls for new services
  • Build infrastructure using code so environments are repeatable and easy to change
  • Set up monitoring, alerts, and dashboards to spot issues before users notice
  • Improve reliability by fixing outages, removing bottlenecks, and planning capacity
  • Harden systems with least-privilege access, encryption, and secure configurations
  • Automate deployments and backups to reduce manual work and human error
  • Coordinate with developers to choose cloud services and troubleshoot releases
  • Document standards and runbooks so others can operate systems consistently

A typical day

  1. Check alerts and dashboards, then handle any incidents or performance drops
  2. Review planned changes, update infrastructure code, and test in a staging setup
  3. Meet with app teams to plan deployments, costs, and reliability requirements
  4. Apply security updates, rotate secrets, and verify backups and recovery steps
  5. Write notes and runbooks, then review pull requests from teammates

Tools

Cloud platforms: AWS, Microsoft Azure, Google CloudInfrastructure as code: Terraform, AWS CloudFormationContainers: Docker, KubernetesCI CD: GitHub Actions, GitLab CI, JenkinsMonitoring: Prometheus, Grafana, CloudWatchScripting: Python, BashVersion control: GitSecrets and keys: HashiCorp Vault, cloud key management

Ways in

There is more than one route.

Ways to study

  • Bachelor degree in computer science, IT, software engineering, or networking
  • Diploma or certificate in cloud computing, systems administration, or DevOps
  • Bootcamp focused on cloud, Linux, networking, and automation fundamentals
  • Self-study with labs plus an industry cloud certification and a portfolio

How people get their first job

  • Build a small cloud lab project and publish the code and setup notes
  • Start in IT support or systems administration and move into cloud operations tasks
  • Apply for DevOps or site reliability internships that include cloud deployments
  • Earn an entry cloud certification and practice with hands-on labs
  • Contribute to internal tooling or automation scripts in a part-time tech role

How the work is changing

What AI is doing to this role

How AI is changing this role · one of 6 tasks we track

Set up cloud networks, servers and storage

Sped up a lot

What AI does

AI drafts the setup. Clicking through the console is nearly gone.

Still yours

You choose the region, the size and the network shape.

Reviewed September 2026

In the app · Premium

The rest is in the app

  • How AI affects the other 5 tasks
  • Whether this job is growing or shrinking
  • How hard the first job is to get
  • Similar roles that are easier to get into
  • Updated every month, with sources
See it in the app →

How we rate a job →

Already working

Already a Cloud Engineer?

Plan your move to Senior Cloud Engineer: 12 chapters that end with a strong case for your next review.

Grow in the role →

Other roles in IT & Cloud Infrastructure

Questions

Questions about this plan

How long does it take to become a cloud engineer with Welica?

The plan is 12 chapters, 3 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.

Do I need a degree?

Not always. Common routes are bachelor degree in computer science, IT, software engineering, or networking, diploma or certificate in cloud computing, systems administration, or DevOps, bootcamp focused on cloud, Linux, networking, and automation fundamentals, or self-study with labs plus an industry cloud certification and a portfolio.

What is free?

Chapter 1, See what cloud engineer work involves, is free for good. Premium unlocks the rest of the plan.

Start the Cloud Engineer plan.

Chapter 1 free. About 15 to 30 minutes a day.

Start on web Continue your session Download for MacMac Get the iPhone appiPhone Get it on Google PlayAndroid