Career Switcher’s Guide to Cloud & DevOps (No CS Degree Needed)

Two years ago I was an English teacher in Lyon. I had a whiteboard, thirty teenagers who didn’t want to be there, and a vague sense that I was supposed to do something with my life that involved fewer conjugation tables.

Today I deploy infrastructure with Terraform, troubleshoot Kubernetes clusters, and argue about CIDR ranges in pull request reviews. No CS degree. No bootcamp. No rich uncle at AWS.

I’m not special. Plenty of people have made this switch — from marketing, accounting, logistics, teaching, nursing. The path is real. But it’s also longer and messier than the LinkedIn success stories suggest. This is the honest version.

Why Cloud & DevOps Is Unusually Good for Career Switchers

Most tech roles have gatekeeping problems. Software engineering interviews still ask you to invert binary trees on a whiteboard. Data science wants a master’s degree and three years of Python.

Cloud and DevOps is different, for a few structural reasons.

The talent gap is real. Companies need cloud engineers faster than universities can produce them. A 2025 report from Gartner showed that through 2028, over 70% of enterprises will struggle to fill cloud-related roles. That shortage doesn’t care about your degree.

Skills-based hiring is actually happening here. More than other tech fields, cloud roles are screened by certifications and demonstrable projects. An AWS Solutions Architect cert with a solid GitHub portfolio will get you past resume filters that a CS degree alone won’t.

Remote-friendly by default. Cloud infrastructure is, by definition, not in your office. Most cloud and DevOps roles were remote before the pandemic and stayed that way. That’s a massive advantage for career switchers who might not live near a tech hub.

The work is tangible fast. Unlike spending six months on algorithms before you build anything, you can spin up real infrastructure on day one. That feedback loop keeps people going through the hard middle months.

The Honest Timeline (6-12 Months)

Here’s where I lose some people. The “become a cloud engineer in 30 days” crowd won’t like this.

A realistic timeline for someone studying part-time while working another job:

Months 1-3: Foundations. Linux basics, networking fundamentals, one cloud provider’s core services. This is where you’re building the floor. It’s not exciting. Do it anyway.

Months 4-6: First certification + hands-on projects. Take your first cert exam. Build two or three real projects. Start making your GitHub look like someone who actually does this.

Months 7-9: Deeper skills + second cert. Pick up infrastructure as code (Terraform), CI/CD pipelines, containers. Your second certification should be more specialized.

Months 10-12: Job search + continued building. Apply while you’re still learning. You’ll never feel ready. Apply anyway.

Some people move faster. Some slower. I took about ten months, studying two hours most weekday evenings and bigger blocks on weekends. The point is: it’s not a weekend project, but it’s not a four-year degree either.

What to Learn First (And What to Skip)

The biggest trap for career switchers is the “learn everything” spiral. You open a cloud roadmap, see 47 services, and freeze.

Here’s the order that worked for me and most people I’ve talked to:

Start here:

• Linux command line. Not expert-level. Navigating directories, editing files, reading logs, understanding permissions. Two weeks of consistent practice.
• Networking basics. IP addresses, subnets, DNS, HTTP/HTTPS, ports. You don’t need a CCNA. You need to understand what happens when you type a URL into a browser.
• One cloud provider. Pick AWS, Azure, or GCP. I’d recommend AWS because it has the biggest market share and the most learning resources. Don’t try to learn all three.

If you want a structured starting point, this guide walks through the fundamentals from zero.

Then add:

• Infrastructure as Code (Terraform or CloudFormation)
• Containers (Docker first, then basic Kubernetes)
• CI/CD (GitHub Actions or GitLab CI — build a real pipeline)
• Monitoring basics (CloudWatch, Prometheus, or similar)

Skip for now:

• Advanced Kubernetes (you’ll learn it on the job)
• Multi-cloud architecture (nobody hires juniors for this)
• Serverless deep dives (useful later, not a hiring priority)
• Machine learning ops (specialization, not foundation)

Certifications: Yes or No?

Yes. Emphatically yes — but for the right reason.

Certifications don’t prove you can do the job. Hiring managers know that. What they do is get your resume past the initial filter. When you’re a career switcher with no relevant work experience, a certification is the fastest credibility signal you can earn.

Start with: AWS Cloud Practitioner or AZ-900 (Azure Fundamentals). Low difficulty, broad coverage, gets you familiar with exam formats.

Then: AWS Solutions Architect Associate or AZ-104 (Azure Administrator). This is the one that actually opens doors. It tells employers you understand how to design and deploy real infrastructure.

Optional but valuable: Terraform Associate, Kubernetes (CKA), or a DevOps-specific cert.

Not sure which path to take? This decision tree helps you pick the right certification for your situation.

One thing I’d push back on: don’t collect certifications like stamps. Two or three targeted certs plus real project work beats six certs with an empty GitHub.

Build Your Portfolio: Three Projects That Actually Matter

Your portfolio needs to answer one question: “Can this person build and maintain real infrastructure?”

Here are three projects that demonstrate that, roughly in order of complexity:

Project 1: Static website with full CI/CD pipeline. Host a static site on S3 (or equivalent), put CloudFront in front of it, use GitHub Actions to deploy on every push. Bonus: add a custom domain with Route 53 and SSL. This shows you understand storage, CDN, DNS, automation, and version control. It’s also genuinely useful — you can use it as your personal site.

Project 2: Containerized application on cloud infrastructure. Take any simple web app (a To-Do list is fine, nobody cares about the app itself), containerize it with Docker, deploy it to ECS or EKS, put a load balancer in front. Define all of it in Terraform. This shows containers, orchestration, infrastructure as code, and networking.

Project 3: Monitoring and alerting setup. Add CloudWatch dashboards (or Prometheus/Grafana) to Project 2. Set up alarms for CPU, memory, error rates. Create an SNS notification when something breaks. This shows you think about operations, not just deployment.

Document each project in your GitHub README. Explain what you built, why you made the choices you did, and what you’d improve. That documentation matters more than you think.

Your Previous Career Is an Asset (Not a Weakness)

This is the part career switchers underestimate the most.

Every job teaches transferable skills. Cloud and DevOps just happens to reward many of them:

• Teaching → You can explain complex systems to non-technical stakeholders. That’s rare and valuable.
• Project management → You understand timelines, dependencies, and scope. That’s literally what infrastructure planning is.
• Accounting/finance → You grasp cost optimization intuitively. Cloud cost management is a real specialty.
• Marketing → You think in metrics and outcomes. Monitoring and SLAs will feel natural.
• Healthcare → You’re used to high-stakes processes and compliance. Welcome to regulated cloud environments.

In interviews, don’t apologize for your background. Frame it. “I spent five years managing logistics for a retail chain, which means I’ve dealt with complex systems, tight deadlines, and things breaking in production — just not the digital kind.”

The Job Search: Where to Apply and How to Frame Your Resume

Where to look:

• LinkedIn with alerts for “Junior Cloud Engineer,” “Associate DevOps,” “Cloud Support.”
• Remote-specific boards: We Work Remotely, Remote OK, Flexa.
• Cloud provider job boards: AWS, Azure, and GCP all hire cloud support engineers. These are excellent first roles.
• Consulting firms and MSPs (Managed Service Providers). They’re always hiring and you’ll get exposed to many different environments fast.

Resume tips for career switchers:

• Lead with a summary that owns the switch: “Former [role] transitioning to cloud engineering. AWS Solutions Architect Associate certified. Built and deployed [X] on [Y].”
• Put certifications near the top, not buried at the bottom.
• List your projects like work experience. Each one gets a title, date, and bullet points describing what you built and what tools you used.
• Your previous career goes in a section called “Additional Experience.” Keep it to two or three lines focused on transferable skills.

Expect the timeline: First applications to first offer typically takes one to three months of active searching. The first twenty applications feel terrible. That’s normal. Keep going.

FAQ

Do I really not need a CS degree?

Really. A 2025 LinkedIn workforce report showed that over 40% of cloud practitioners hired that year did not have a traditional computer science degree. Employers care about what you can do. A certification plus a portfolio of real projects speaks louder than a diploma from ten years ago. That said, you do need to learn the fundamentals — networking, Linux, basic scripting. You just don’t need a university to learn them.

How much does the career switch actually cost?

Less than you’d think. AWS Free Tier covers most of what you’ll build in the first six months. Certification exams run $100-300 each. Linux and networking resources are free online. Total realistic budget: $300-800 over the full transition period. Compare that to a bootcamp ($10,000+) or a degree ($40,000+). The real cost is time, not money.

Should I quit my job to study full-time?

I wouldn’t. Most successful career switchers I know did it part-time. Two hours a day on weekdays, four to six on weekends. Quitting adds financial pressure that makes it harder to learn well and harder to be patient during the job search. If you can afford to reduce hours or go part-time at your current job, that’s the sweet spot.

What if I’m not “technical enough” for this?

You’re conflating “technical” with “experienced.” Every cloud engineer started by not knowing what a subnet was. If you can follow instructions, troubleshoot problems, and sit with discomfort while learning, you have the core skills. The technical stuff is learnable. The discipline to keep going when it’s confusing — that’s the actual filter, and career switchers often have more of it than fresh graduates.

Ready to plan your cloud career switch? Start with SkillRealm Learn →