How to Become a Cloud Engineer Without a Degree

You want to land a cloud engineering job, but you don't have a computer science degree and you're not sure if that's a dealbreaker. The good news: it usually isn't. The path is clear, but it's not short, and you need to be strategic about where you invest your time.

Let's get the degree question out of the way. Most modern tech companies, especially startups and mid-sized SaaS firms, care far more about what you can build and prove than where you went to school. Their hiring managers are looking at your GitHub, your hands-on experience, and how you talk through problems. Big enterprise companies, government contractors, and some traditional financial institutions are different. They often have rigid HR filters that list a degree as a requirement. You can sometimes get past this with a strong internal referral, but it's an uphill battle. Your best bet is to focus on the vast market of companies that have dropped the degree requirement.

The skills you need follow a logical order. You can't design a cloud-native application if you don't understand the basics of networking or how an operating system works.

• Linux fundamentals: Command line, file systems, permissions, and basic shell scripting. This is the bedrock.
• Networking: TCP/IP, DNS, HTTP/S, firewalls, and subnets. Cloud is just networking at scale.
• One major cloud provider: Pick AWS, Azure, or GCP. AWS has the largest market share, so it's a solid default.
• Infrastructure as Code: Learn Terraform. It's the industry standard for provisioning cloud resources. Forget clicking in the console for production.
• Containers and orchestration: Docker to package your apps, and Kubernetes to manage them. You don't need to be a Kubernetes master, but you must know the basics.
• A scripting language: Python is the most versatile choice. You'll use it for automation, tooling, and interacting with cloud APIs.
• Version control: Git. Non-negotiable. Know how to branch, merge, and use pull requests.

Certs get a lot of hype. They can be useful, but be honest about what they are: a foot-in-the-door tool, not a job guarantee. The AWS Certified Cloud Practitioner is a good intro to cloud concepts and AWS terminology, but it has almost zero value for landing an engineering role. Skip it if you're on a tight budget. The AWS Solutions Architect Associate is much better. It proves you understand core AWS services and how they fit together. It's the most recognized entry-level cert for a reason. The AWS SysOps Administrator is more hands-on and operational. It's a good second cert if you want to prove you can manage and monitor systems, not just design them. A Linux cert like CompTIA Linux+ or the Linux Foundation Certified System Administrator (LFCS) can help you prove your foundational skills, especially if you're coming from a non-technical background. Don't collect certs. Get one solid cloud cert and one foundational cert, then pour your energy into building projects.

Your portfolio is your real resume. It's how you prove you can do the work. Here are three projects that show real-world skills.

1. Static Website with CI/CD Pipeline: Host a simple website (your portfolio site) on AWS S3. Use CloudFront for CDN and Route 53 for DNS. Then, build a pipeline using GitHub Actions or AWS CodePipeline that automatically deploys your site when you push changes to your main branch. This shows you understand static hosting, CDN, DNS, and basic automation.

2. Deploy a Containerized Microservice: Create a simple API (like a to-do list) with Python/Flask. Write a Dockerfile for it. Then, deploy it to a managed Kubernetes service like AWS EKS or even a simpler one like AWS ECS. Use Terraform to provision the EKS cluster and the networking (VPC, subnets) around it. This proves you know Docker, Kubernetes, Terraform, and networking.

3. Build a Serverless Data Pipeline: Create an S3 bucket. When a CSV file is uploaded to it, trigger an AWS Lambda function (written in Python) that processes the data and stores it in a DynamoDB table. Use Terraform to define all the resources: the S3 bucket, the Lambda function, the IAM roles, and the DynamoDB table. This shows you understand serverless, event-driven architecture, and IaC.

Now, how do you actually get the job? Don't just apply to "Cloud Engineer" roles. Look for titles like "Site Reliability Engineer (SRE)," "DevOps Engineer," "Platform Engineer," and "Infrastructure Engineer." These roles have huge overlap. Your first job is about getting in, not about the perfect title. Tailor your resume for each application. Use the job description decoder tool on jobrise.io to understand exactly what a company wants, then mirror that language in your resume and cover letter. Highlight your projects first, then your certs. Your experience section should frame any past work, even non-tech, in terms of problem-solving and automation. Network relentlessly. Join cloud-focused Discord or Slack communities. Engage on LinkedIn. A referral from an employee is your best weapon to bypass a missing degree.

The 6-month checklist#

This assumes you can dedicate 15-20 hours a week.

• Month 1: Master Linux and networking basics. Complete a hands-on course. Start using the command line for everything.
• Month 2: Deep dive into your chosen cloud provider (e.g., AWS). Pass the AWS Solutions Architect Associate exam.
• Month 3: Learn Git, Python scripting fundamentals, and Docker. Build your static website project.
• Month 4: Learn Terraform and Kubernetes basics. Build your containerized microservice project.
• Month 5: Build your serverless pipeline project. Polish your GitHub repos with clear READMEs. Write your resume.
• Month 6: Start applying. Apply to 10-15 tailored jobs per week. Continue networking. Practice talking through your projects.

Free tools#

• jobrise.io/en/free-ats-checker/
• jobrise.io/en/free-jd-decoder/
• jobrise.io/en/jobs/
• jobrise.io/en/blog/

FAQ#

Do I need to know all three major clouds (AWS, Azure, GCP)?

No. Pick one and go deep. Employers value depth in one platform over shallow knowledge of three. You can always learn a second cloud on the job.

How important is a portfolio website?

It's very important. It's a central place to link your GitHub, your projects, and your resume. It shows you can build and deploy something, which is the whole point.

Can I become a cloud engineer from a help desk job?

Absolutely. It's one of the most common paths. You already have troubleshooting skills and understand IT systems. Use your time to automate parts of your help desk job and build the projects on the side.

What's the realistic salary for a first cloud engineer role in the US?

Ranges vary widely by location and company. A typical range for a junior role might be $75,000 to $110,000. Research current salaries on sites like Levels.fyi and Glassdoor for your specific area.

Should I get a cloud cert or build projects first?

Do both in parallel. Start with foundational learning and a cert, but begin your first project as soon as you have the basics. The cert gets you the interview; the projects get you the job.