How I Learned Cloud Engineering and Got Hired in 90 Days (2026 Roadmap)

Five years ago, I was faced with an impossible decision. Stay in a job that was slowly crushing my soul — or quit with only 90 days of savings and bet everything on learning a skill I knew nothing about.

I went with the second option. Everyone told me I was crazy. My family was worried. My colleagues said I'd come crawling back within months.

Within 90 days, I landed my first cloud engineering role, doubled my income, and got to work from home.

But that was five years ago. If I was starting from scratch today, I'd do things differently. In this guide, I'm going to show you exactly what I would do — how to leverage AI, what projects actually matter, and how to stand out in a tougher job market. These are the same strategies that 900+ students inside Cloud Engineer Academy are using to land roles at companies like AWS, Google, Microsoft, and Deloitte, even without any prior IT experience.

Why I Quit: The Moment Everything Changed

I was working as a software engineer in London, earning a decent wage but nothing special. Commuting more than 3 hours per day — 4 hours on bad days, on packed trains where everyone looked miserable, going through the motions.

One morning, standing on that train with no seat, surrounded by people living the exact same life, something hit me: I was on a never-ending hamster wheel heading to a destination I hated. Getting 1-2% pay rises that weren't keeping up with inflation. Future prospects that looked hopeless.

That's when I realised the real problem: my skill set was limiting everything. My lifestyle, my career, the opportunities available, my future prospects in tech. If I wanted any of those things to change, I had to acquire a new skill set.

At the same time, something drastic was happening at my company. We had legacy IT systems on physical servers — massive server rooms, tons of hardware. When website traffic spiked, servers crashed because we couldn't scale fast enough. When traffic was low, we were paying for expensive hardware sitting idle.

Leadership decided to move everything to the cloud — shifting from owning physical hardware to renting computing power from companies like Amazon. Suddenly, the company was hiring a completely new type of engineer: cloud engineers.

I could see what was on the horizon. Explosive growth. Better opportunities. Remote work. That day, I handed in my resignation.

Step 1: Choose Your Cloud Provider (AWS)

My first question: which cloud provider should I focus on? AWS, Azure, or GCP?

AWS was the market leader with nearly 40% of the entire cloud market. More businesses using AWS meant more job opportunities. So I chose AWS because it gave me the best shot at landing that first job quickly.

The same logic still applies in 2026. AWS dominates with over 30% market share. They also have the most extensive free tier, giving you more resources to build projects without spending money.

Once you know one cloud platform well, picking up another is much easier — the concepts transfer, the services just have different names. Start with the one that gives you the most opportunities.

Step 2: Build the Foundation First

Before learning AWS, I needed the fundamental concepts everything is built on. Think of these as the foundation of a house — you can't build without them being rock solid.

Networking: How computers talk to each other over the internet. You need this because when you set up cloud infrastructure, you're essentially creating networks in the cloud.

Linux & Operating Systems: Most cloud servers run Linux. You need to be comfortable with the command line — the black screen with text where you type commands instead of clicking icons. It sounds scary at first, but it's just a different way of controlling a computer.

Virtualisation: This is what makes cloud computing possible. Virtualisation lets you split one physical computer into multiple virtual ones. AWS has huge physical servers and uses virtualisation to split them up and rent pieces to different customers. Understanding this means understanding what you're actually doing when you launch a cloud server.

Databases: Where information is stored. SQL databases store data in structured tables. NoSQL databases are more flexible. You need to understand when to use which type — because almost everything in the cloud involves storing and retrieving data.

I spent time learning these fundamentals, and the temptation to jump straight into AWS was real. But learning first principles first made everything else much easier because I understood what was happening under the hood.

Step 3: Get Certified (But Know It's Just the Beginning)

I went after two AWS certifications: Cloud Practitioner and Solutions Architect Associate. These are entry-level certifications that give you a big-picture view of AWS and how services work together.

I used completely free resources — there are excellent videos on YouTube, including free AWS cloud engineering courses on the Tech with Soleyman channel.

The certifications gave me structure and confidence. But here's what happened next: I started applying for roles and got absolutely nowhere. No callbacks. No interviews. Nothing.

That's when I realised I was approaching this all wrong. Certifications alone aren't enough — hiring managers want to see that you've been building real projects and solving real problems. The certification is where most people think the journey ends. It's actually where it begins.

Step 4: Master the "Core Four" AWS Services

AWS has over 200 services, but the same 12-15 show up in almost every architecture. I focused on what I call the core four — the building blocks everything else is built on:

1. VPC (Virtual Private Cloud) — your own isolated network within AWS. Think of it like having your own private section of the internet where you control who can come in and who can go out.

2. IAM (Identity and Access Management) — controls permissions. Who can do what in your AWS account? Like having different keys for different rooms in a building.

3. EC2 (Elastic Compute Cloud) — renting computers in the cloud. You launch an EC2 instance — a virtual machine running in AWS's data centres.

4. S3 (Simple Storage Service) — file storage that's incredibly reliable and scales automatically. Videos, photos, documents, backups — S3 handles it all without worrying about running out of space.

I didn't just learn what these services do — I learned when to use them and why. Because in real projects, these appear constantly. Master these and you can figure out other services as you need them.

Step 5: Build Projects That Tell a Story (Not Just Tutorials)

Here's what most people get wrong about cloud projects. They think it's about what you build. Should I build a web application? Deploy something on Kubernetes? If you've been asking "what project should I build?" — I want you to think about it from a completely different perspective.

What you build matters far less than the story you tell about it.

When hiring managers asked about my projects, they didn't care that I built a web application. They cared about how I explained it:

• What problem was I solving? The business challenge. "I needed a system that could handle unpredictable traffic without crashing or wasting money on idle resources."
• Why specific decisions? What were the trade-offs? EC2 gives more control but requires more management. Lambda is simpler and hands-off but less flexible. Articulating trade-offs shows you think like an actual engineer.
• What would I do differently? What did I learn? What would I change? This shows self-awareness and continuous improvement.
• Documentation: Why this architecture? What happens at 10x traffic? How much does it cost at scale? What's the security model?

Employers see dozens of portfolios with projects. What makes you stand out is showing you understand the WHY behind what you built. That's what actually gets you hired — and that was the single biggest thing that helped me go from zero to cloud-hired in 90 days. Here's the full guide to building a portfolio that demonstrates real judgment.

Step 6: The Three Skills That Became Massive Advantages

While building projects, I focused heavily on three areas. In 2026, these are even more critical.

Security (Built In From Day One)

A security breach can cost a company millions. Companies take this incredibly seriously and want to see that you do too. In every project, show security was considered from day one — not added at the end. How are you controlling access? How is data protected? What happens if someone tries to access something they shouldn't?

Infrastructure as Code (Terraform)

Nobody clicks buttons in the AWS console to build production systems. It's fine using the console as a beginner, but as a cloud engineer you define everything in code using tools like Terraform.

The advantages are huge: every change is tracked automatically, like a complete history of everything you've ever done. If something breaks, you see exactly what changed and when. Need the same setup for a different project? Run the same code. No clicking through menus trying to remember what you did. No human errors. It works the same way every time.

CI/CD Pipelines

This is how code gets from a developer's computer to being live where customers can use it. A developer makes a change. The system automatically checks if the change breaks anything by running tests. If tests pass, the code automatically goes live — no manual deployment required.

Without automation, updating a website means manually moving files, checking everything, pushing it live — taking hours with constant mistakes. With CI/CD, this happens automatically in minutes. Some companies push updates live dozens of times a day because it's completely automated and safe.

Learn tools like GitHub Actions, GitLab CI, or AWS CodePipeline. Having this in your projects signals to employers that you think like someone who's worked in a professional environment — even if you've never worked in tech before.

The 2026 Difference: Be AI-Native From Day One

When I started, AI wasn't what it is today. In 2026, AI is fundamentally changing cloud engineering and employers want to see that you understand this shift.

In every project you build, demonstrate how you leverage AI and automation:

• Use AWS AI services like Amazon Bedrock, SageMaker, or Rekognition in your projects
• Use AI tools throughout your learning — ChatGPT, Claude, GitHub Copilot — to understand concepts faster when you're stuck
• Use AI to troubleshoot errors and suggest better architectural approaches

But fair warning: AI is an amplifier of your skill set. If you're very good, AI 10x your output. If you don't understand what you're doing, AI just makes you worse. Don't outsource your entire thinking — you'll freeze when a hiring manager asks a question and you haven't got ChatGPT open.

Most people either ignore AI completely or are intimidated by it. If you can show you're comfortable using AI and AWS AI services while demonstrating you understand the fundamentals and can think critically, you become incredibly valuable.

This is the asymmetric career bet — cloud fundamentals with AI layered on top — that makes you virtually indestructible in the 2026 job market.

Step 7: Get Hired (The LinkedIn Strategy That Actually Works)

Once I had projects built and documented, I needed interviews. I updated my LinkedIn profile and started posting daily about exactly what I was learning.

90% of recruiters go to LinkedIn to find candidates. When they find your profile and see you're actively building in public, they message you directly. Recruiters were finding their way to me with opportunities before I even applied.

When I did apply, I didn't just submit applications and hope. Every time, I found the recruiter or hiring manager on LinkedIn and sent a direct message. I'd send Loom videos with myself on camera — explaining who I am, my experience, and why I applied. Most people don't do this.

If you take nothing else from this guide, take this: reaching out directly puts you on top of the candidate pile because you've made it easy for them to notice you. Cloud Engineer Academy students are using this exact strategy to get hired at AWS right now.

In interviews, I focused on my projects — the problems I solved, the thinking behind my decisions, how I'd handle scale, security, and cost. That's what hiring managers want to see.

The Numbers That Should Excite You

In 2026, the demand for cloud engineers is exploding:

• AWS has reported a global shortage of 6 million cloud professionals
• The cloud computing market is growing from $900 billion to over $5.4 trillion in the next decade
• Cloud Engineer Academy has placed 900+ engineers in roles paying $70,000-$120,000

If you can show that you understand the fundamentals, can build real things, think like an engineer, and know how to work with AI effectively — you are exactly what companies are looking for.

I was stuck in a dead-end job, feeling hopeless about my future. The 6-step cloud engineer roadmap lays out the entire journey. The first principles approach gives you the thinking framework. And understanding what's really happening in the tech job market shows you why right now — in 2026 — is the best time to make this move.

Start today. Make that decision once and for all and don't look back.