In partnership with
Hey {{First Name | there}},
I had an Economics degree. No computer science background. No connections in tech. No idea how people actually broke into cloud.
But I figured it out. And the thing that changed everything wasn’t a single cert or a lucky break — it was a plan. A 4-phase plan that I’ve now used to help dozens of others make the same kind of leap.
One of my mentees went from a help desk — resetting passwords every day — to Cloud Solutions Architect. Salary more than doubled. Another went from care support work to Senior Analyst. Different starting points, same shape of path.
And before you think “well, they must be special” — they weren’t. They didn’t have connections. They didn’t go to top universities. What they had was a structure to follow and the consistency to stick with it.
Here are the 4 phases:
🟢 Phase 1: Build the Foundation
Months 1–3
Goal: Understand cloud basics and prove it with a certification.
Study for and pass AWS Cloud Practitioner (6-8 weeks if you study 1 hour a day)
Learn basic networking: what's a subnet, what's a security group, what's DNS
Set up a free AWS account and actually click around the console — don't just read about it
Follow 5-10 cloud professionals on LinkedIn (the algorithm will start showing you the right content)
Cost: £0 (AWS Skill Builder is free. The exam is ~£100–£120 including VAT.)
🔵 Phase 2: Get Your Hands Dirty
Months 3–6
Goal: Build real projects and start your second cert.
Build 2-3 projects on AWS Free Tier: a static website on S3, a serverless API with Lambda + API Gateway, a simple CI/CD pipeline
Start studying for Solutions Architect Associate — this is the cert that opens doors
Document everything on GitHub. Write short LinkedIn posts about what you're building. This is your portfolio.
Join an AWS community (AWS User Groups, r/aws, cloud Discord servers)
Cost: £0–£50 (stay within Free Tier limits. Use free study resources first.)
🟣 Phase 3: Make Yourself Visible
Months 6–9
Goal: Pass SAA, build your personal brand, and start networking.
Pass Solutions Architect Associate — put it on LinkedIn the same day
Optimise your LinkedIn profile: headline = "[Target Role] | AWS Certified | Building in Public", not "Aspiring cloud engineer"
Post 2-3 times a week about what you're learning. You don't need to be an expert — you need to be consistent.
Attend meetups, virtual events, AWS Community Days. Talk to people who have the job you want.
This is where most people stall. They have the cert. They have the projects. But nobody knows they exist. Visibility is not optional.
🔴 Phase 4: Land the Role
Months 9–12
Goal: Get interviews and convert them into offers.
Rewrite your CV using the "So what?" framework from Edition 1 — every line should show impact, not activity
Apply to 5-10 roles per week. Target: Cloud Support, Junior Cloud Engineer, Associate Solutions Architect, Cloud Operations
Prepare for scenario-based interviews: "How would you design a highly available web application?" Practice out loud.
Don't wait until you feel "ready." I applied before I felt ready — and that's how I got my first cloud role. My mentees did the same.
The job market rewards people who ship, not people who wait. Here's the lesson nobody tells you:
The path into cloud isn't hidden. It's just not linear. It's messy. You'll feel behind. You'll wonder if you're "technical enough."
You are. The fact that you're reading this means you're already ahead of 90% of people who talk about switching but never start.
None of the people I've helped had any advantage you don't have. They just followed the phases, stayed consistent, and refused to wait until they felt ready.
12 months. 4 phases. One decision to start. 🔥
💡 Your move this week:
Figure out which phase you're in right now. Be honest. If you haven't passed Cloud Practitioner yet, you're in Phase 1 — and that's completely fine.
Do ONE thing from your current phase this week. Not five things. One. Set up an AWS account. Register for an exam. Post on LinkedIn. Apply to one role.
Write down your target role and a date. "Cloud Engineer by December 2026" — stick it on your wall, your phone wallpaper, wherever you'll see it daily.
Want the full step-by-step breakdown?
I made a free PDF: "Your Roadmap to Your First Tech Job" — covering everything from choosing your path to landing the offer, with week-by-week actions and resources. No fluff. Just the plan.
Every Tuesday at 6 PM, I share one practical insight — certifications, AI, career moves, and real talk from inside AWS. Next week: we're getting hands-on.
Hit reply and tell me:
MY PATH
Where are you right now? Help desk? Student? Already in tech but want to level up? Tell me your current role and where you want to be I'll point you to the right phase.
Your path is valid,
Olushola
Hiring in 8 countries shouldn't require 8 different processes
This guide from Deel breaks down how to build one global hiring system. You’ll learn about assessment frameworks that scale, how to do headcount planning across regions, and even intake processes that work everywhere. As HR pros know, hiring in one country is hard enough. So let this free global hiring guide give you the tools you need to avoid global hiring headaches.
P.S. Know 1 person trying to break into cloud? Share your personal referral link and I'll send you my LinkedIn Profile Optimisation Checklist as a thank you.
