Back to all careers
โ˜๏ธ
Cloud ยท Mid level

Cloud Engineer

Design, build, and maintain cloud infrastructure. Work with Azure, AWS, or GCP to deploy scalable and reliable systems.

Salary
$115,000
$85,000 to $155,000
Demand
Very High
Time to entry
3 to 6 months
Difficulty
Mid
A Day in the Life

What a typical day looks like

Most days start at 9 with a quick standup. The team shares what they shipped yesterday, what they will do today, and any blockers. By 9:15 I am at my desk with coffee and Slack. The first hour is usually monitoring: I check dashboards in Grafana and CloudWatch for any overnight alerts, look at error rates, and review the AWS bill anomaly notifications. If nothing is on fire, I move to the day's main work โ€” usually a Terraform pull request, a small infrastructure migration, or a security review. Around 11 I have a 1:1 with my manager. Lunch is at my desk most days while I read AWS blog posts or work on a side project. Afternoons are quieter and that is when I do deeper work โ€” designing the next migration, writing runbooks, or pair-programming with a junior. By 5:30 I am usually done. If I am on-call that week, my phone stays close at night, but typically nothing happens.

Hour-by-hour

9:00
Standup with the team. 15 minutes. What I shipped yesterday, what I'm doing today, any blockers.
9:15
Coffee. Check CloudWatch and Grafana for overnight alerts. Review AWS Cost Explorer for unexpected spikes.
10:00
Deep work block. Today: writing a Terraform module to provision a new VPC peering connection.
11:30
1:1 with manager. Career conversation about moving from Cloud Engineer to Senior Cloud Engineer.
12:00
Lunch at desk. Read the AWS announcement from re:Invent on YouTube.
13:00
Pair with a junior engineer on a tricky IAM permissions issue. Walk through the trust policy together.
14:30
Code review on a colleague's pull request. Suggest using a launch template instead of inline user-data.
15:30
Incident retrospective from yesterday's S3 misconfiguration. Document lessons learned. No blame.
16:30
Sprint planning prep. Estimate next sprint's stories. Argue gently about scoping.
17:30
Done for the day. Push my branch, write standup notes for tomorrow, log off.

Skills you need

Required

LinuxNetworkingScripting (Python/Bash)Cloud PlatformsIaC (Terraform)

Nice to have

KubernetesDockerCI/CDSecurity
Portfolio Projects

Build these to stand out

Hands-on projects beat any CV bullet point. Pick one and finish it.

Beginner 1 to 2 weekends

Multi-AZ Web App with Terraform

Deploy a simple Node.js app on AWS using EC2 Auto Scaling across 2 AZs, with an Application Load Balancer, RDS Multi-AZ database, and a Bastion host. Everything in Terraform. Public on GitHub with a clean README.

Tech: Terraform, AWS (EC2, ALB, RDS, VPC), Node.js, GitHub Actions
Why it helps

Shows you understand HA, VPCs, IaC, and basic CI/CD. Lots of recruiters will look at this.

Beginner 1 weekend

Serverless Image Resizer

Upload an image to S3, Lambda triggers automatically, resizes the image to 3 sizes, saves them back to a different S3 bucket. Set up CloudFront in front. Add monitoring with CloudWatch alarms.

Tech: AWS Lambda, S3, CloudFront, CloudWatch, Python or Node.js, Terraform
Why it helps

Demonstrates serverless thinking. Often used in interview questions.

Intermediate 2 to 4 weekends

Kubernetes Cluster on EKS

Provision an EKS cluster with Terraform. Deploy a microservices app (e.g. a simple ToDo app split into 3 services). Add Ingress, autoscaling, and Prometheus + Grafana for observability.

Tech: Terraform, AWS EKS, Kubernetes, Helm, Prometheus, Grafana
Why it helps

Shows you can operate Kubernetes end-to-end. Senior-level project.

Help someone else find this

This is free, no ads. Share with anyone preparing for the test.