I was a business analyst making pivot tables in Excel when I first heard someone say "cloud engineer." That was in 2017. Two years later I was architecting infrastructure on AWS for a fintech company in Lagos, earning three times my previous salary. I did not have a computer science degree. I had never written code professionally. I had zero IT experience.
That path exists for you too. Not because cloud computing is easy — it is not — but because the industry has a structural labor shortage that rewards demonstrated skill over pedigree. There are over 3.5 million unfilled cloud computing positions globally as of Q1 2026, according to ISC2's workforce study. Employers cannot afford to filter by degree when they need someone who can configure a VPC and deploy a container by next Tuesday.
This guide is a month-by-month plan for going from zero cloud knowledge to employed cloud engineer in 12 months or less. Every timeline is based on studying 15-20 hours per week while working a full-time job. If you have more time, you can compress this. If you have less, stretch it. The sequence matters more than the speed.
What Cloud Computing Actually Is (The 60-Second Version)
Cloud computing means running software, storing data, and processing workloads on someone else's servers — typically Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP). Companies pay by the hour or by the gigabyte instead of buying their own hardware.
Cloud engineers build, maintain, and secure this infrastructure. They write automation scripts, configure networks, deploy applications, monitor systems, and respond when things break. The role sits at the intersection of system administration, networking, and software development.
You do not need to understand all of that right now. You need to understand this: companies are moving their infrastructure to the cloud at an accelerating rate, and they need people who know how to manage it. The demand far outstrips the supply.
The 12-Month Career Change Timeline
Here is the full roadmap. Each phase builds on the previous one. Do not skip phases — the knowledge compounds.
Month 1-2: Build Your Foundation (Cost: $0)
Goal: Understand core cloud concepts and basic IT fundamentals.
What to study:
- Networking basics: IP addresses, DNS, HTTP/HTTPS, TCP/UDP, subnets, firewalls. You need this before anything else. CompTIA's free Network+ study materials cover it. So does Professor Messer's YouTube channel (free).
- Linux fundamentals: The command line, file permissions, package managers, SSH, basic shell scripting. Over 90% of cloud workloads run on Linux. Use a free Ubuntu VM or Windows Subsystem for Linux (WSL) to practice.
- Cloud concepts: What is IaaS vs. PaaS vs. SaaS? What are virtual machines, containers, object storage, load balancers? AWS has a free Cloud Practitioner learning path. Azure has a free AZ-900 learning path. Both are excellent starting points.
Free resources that actually work:
- Citadel Cloud Management Free Courses — structured learning paths for AWS, Azure, and DevOps fundamentals
- AWS Skill Builder (free tier) — official AWS training
- Microsoft Learn — official Azure training, completely free
- FreeCodeCamp's cloud computing videos on YouTube
- Linux Journey (linuxjourney.com) — interactive Linux fundamentals
Time commitment: 15-20 hours per week. Two hours before work, three hours on Saturday and Sunday.
Milestone: You can explain what a VPC is, SSH into a Linux server, navigate the file system, and describe the difference between S3 and EBS without looking anything up.
Salary context at this stage: $0 additional income yet. You are investing. The average career changer spends $200-500 total on their transition (exam fees, a few months of cloud free tier overages). Compare that to a $40,000+ master's degree.
Month 3-4: Earn Your First Certification (Cost: $100-165)
Goal: Pass AWS Cloud Practitioner (CLF-C02) or Azure Fundamentals (AZ-900).
Why these exams:
Both are entry-level. Both validate that you understand cloud concepts, pricing, security basics, and core services. Both are recognized industry-wide. AWS Cloud Practitioner costs $100. Azure Fundamentals costs $165 (Microsoft often offers free exam vouchers through their Virtual Training Days — check their events page).
I recommend AWS Cloud Practitioner if you are unsure which platform to focus on. AWS holds 31% of the global cloud market as of Q1 2026. More job postings mention AWS than any other platform. But if your local job market is Azure-heavy (common in enterprise environments, government, and parts of Europe and Africa), start with AZ-900.
Study plan:
- Weeks 1-4: Work through the official learning path (AWS Skill Builder or Microsoft Learn). Take notes. Do every hands-on lab.
- Weeks 5-6: Take practice exams. Tutorials Dojo, Jon Bonso's practice tests, and Whizlabs all offer affordable practice exams ($15-30). Score 85% or higher consistently before booking your real exam.
- Weeks 7-8: Review weak areas, take the exam.
Hands-on practice: Create a free-tier AWS or Azure account. Build something — a static website on S3, a virtual machine running a web server, a simple database. Do not just read. Click through the console. Break things. Fix them.
Milestone: Certification earned. Add it to your LinkedIn profile immediately. Update your headline to "Cloud Practitioner | Career Changer | Building in Cloud." This is not vanity — recruiters search by certification names.
Salary context: Entry-level cloud support roles (help desk with cloud focus) pay $45,000-$55,000 in the US. You are not ready for these yet, but they are within reach after the next phase. In Nigeria, equivalent roles pay $8,000-$15,000. In the UK, GBP 25,000-32,000.
Month 5-6: Build Your Portfolio (Cost: $0-50)
Goal: Create 3-5 projects that prove you can do real cloud work.
This is where most career changers stall. They collect certifications but never build anything. Hiring managers have told me directly: "I would rather see three solid projects on GitHub than five certifications with no practical work."
Project ideas (pick at least three):
- Cloud Resume Challenge — Build your resume as a static website hosted on S3/CloudFront (AWS) or Blob Storage/CDN (Azure), with a visitor counter powered by a serverless function and a database. This is the single best beginner project. It touches networking, DNS, serverless, databases, CI/CD, and infrastructure as code. The challenge was created by Forrest Brazeal and has helped thousands of career changers land their first cloud role.
- Automated backup system — Write a script (Python or Bash) that backs up files to S3 on a schedule using Lambda and EventBridge. Add SNS notifications for failures. This demonstrates automation thinking.
- Three-tier web application — Deploy a web app with a load balancer, application servers, and a database. Use Terraform or CloudFormation to define the infrastructure as code. This shows you understand production architecture.
- Monitoring dashboard — Set up CloudWatch (AWS) or Azure Monitor to track the health of your three-tier app. Create alarms for CPU usage, error rates, and response times. Write a runbook for what to do when each alarm fires.
- CI/CD pipeline — Use GitHub Actions or GitLab CI to automatically test and deploy your application when you push code. This is a daily task for cloud engineers.
Documentation matters: Write a README for each project that explains what it does, why you built it, what you learned, and what you would do differently. Hiring managers read READMEs. They want to see your thinking process, not just your code.
Milestone: GitHub profile with 3-5 projects. Each has a clear README. You can walk someone through any of them in a 15-minute conversation.
Salary context: With one certification and a portfolio, you qualify for junior cloud engineer and cloud support roles. US: $55,000-$75,000. Remote roles for US companies from abroad: $30,000-$50,000. UK: GBP 30,000-40,000. Nigeria (remote for international companies): $15,000-$25,000.
Month 7-9: Get Your Associate-Level Certification and Start Applying (Cost: $150-300)
Goal: Pass AWS Solutions Architect Associate (SAA-C03) or Azure Administrator (AZ-104), and begin your job search.
Why the upgrade: The foundational cert proved you understand concepts. The associate cert proves you can design and implement solutions. This is the certification that most directly correlates with getting hired. The AWS Solutions Architect Associate is the most-requested certification in cloud job postings worldwide.
Study plan:
- Use Adrian Cantrill's courses (SAA-C03), or John Savill's YouTube series (AZ-104). Both are thorough and hands-on.
- Build labs alongside the course. Do not just watch videos.
- Practice exams from Tutorials Dojo or Whizlabs.
- Budget 8-10 weeks for preparation.
Start applying before you pass the exam. Many career changers wait until they feel "ready." You will never feel ready. Start applying at month 7. Here is why: the average job search takes 2-4 months. If you start at month 7 and land a role at month 10-11, the timing works. If you wait until month 9 to start applying, you are looking at month 12-13 before you start working.
Where to find entry-level cloud jobs:
- LinkedIn (filter by "Entry Level" + "Cloud Engineer" or "Junior DevOps")
- Indeed, Glassdoor
- Citadel Career Intelligence Collection — curated job search strategies, resume templates, and interview preparation
- We Work Remotely, Remote OK, Turing (for remote roles)
- Local meetups and cloud user groups (AWS User Groups, Azure meetups, HashiCorp meetups)
Networking is not optional. Attend virtual or in-person cloud meetups. Post about your projects on LinkedIn. Comment on other people's cloud content. 60-80% of cloud jobs are filled through referrals or networking, not cold applications.
Milestone: Associate certification earned. 20+ job applications submitted. 2-3 informational interviews completed. Active LinkedIn presence with project posts.
Salary context: Junior cloud engineer / junior DevOps engineer roles. US: $70,000-$95,000. Remote (US-based companies): $40,000-$65,000. UK: GBP 35,000-50,000. Canada: CAD 60,000-80,000. Nigeria (remote): $18,000-$35,000.
Month 10-12: Land Your First Cloud Role
Goal: Accept an offer and start your cloud engineering career.
Interview preparation:
- Technical screens: Expect questions on networking (CIDR notation, security groups, NACLs), Linux (troubleshooting a server that will not start), and cloud services (when to use which database, how to design for high availability). Practice explaining your projects clearly and concisely.
- Scenario questions: "A customer reports the website is slow. Walk me through your troubleshooting steps." "Design a system that can handle 10,000 requests per second with 99.9% uptime." These test your thinking process, not your memorization.
- Behavioral questions: "Tell me about a time you learned something new under pressure." Your entire career change story answers this. Use it. Hiring managers value resilience and learning speed.
Roles to target (easiest to hardest for career changers):
- Cloud Support Associate / Engineer — You answer tickets about cloud services. Amazon, Microsoft, and Google all hire for these roles and they are excellent entry points.
- Junior Cloud Engineer — You build and maintain infrastructure under the guidance of a senior engineer.
- Junior DevOps Engineer — Similar to cloud engineer but with more focus on CI/CD pipelines and developer tooling.
- Junior Site Reliability Engineer (SRE) — Higher bar, but some companies hire juniors for SRE rotations.
- Cloud Consultant (at an MSP) — Managed service providers often hire less experienced engineers because they need volume. The pay is sometimes lower but the breadth of exposure is massive.
What to do when you get an offer:
Negotiate. The first offer is rarely the best offer. Ask for the salary range. Counter 10-15% above their initial number if it is below market. Check levels.fyi, Glassdoor, and Payscale for your specific role and location. Even a $5,000 increase in your starting salary compounds over your career.
Milestone: Signed offer letter. You are a cloud engineer.
Salary Growth After Your First Role
The first role is the hardest to get. After that, your salary trajectory accelerates:
| Experience | US Salary Range | UK Range (GBP) | Remote (Global) |
|---|---|---|---|
| Entry (0-1 year) | $65,000-$85,000 | 30,000-42,000 | $25,000-$50,000 |
| Junior (1-2 years) | $80,000-$105,000 | 40,000-55,000 | $40,000-$65,000 |
| Mid-level (3-5 years) | $110,000-$145,000 | 55,000-80,000 | $60,000-$95,000 |
| Senior (5-8 years) | $140,000-$190,000 | 75,000-110,000 | $85,000-$130,000 |
| Staff/Principal (8+ years) | $180,000-$280,000 | 100,000-150,000 | $110,000-$180,000 |
These figures include base salary only. Total compensation at large tech companies (Amazon, Google, Microsoft) includes stock grants and bonuses that can add 20-50% on top of base.
The career changer advantage: you bring domain expertise from your previous career. A former teacher who becomes a cloud engineer understands training and documentation instinctively. A former retail manager understands operations, scheduling, and incident response. That cross-domain knowledge makes you more valuable than someone who has only ever worked in tech.
Career Change Success Stories
Maria: High School Teacher to Cloud Engineer (14 months)
Maria taught high school math in Dallas for eight years. She earned $52,000 per year. She started studying cloud computing in January 2025 using free resources — AWS Skill Builder, YouTube, and Citadel's free course library.
By March she passed the AWS Cloud Practitioner exam. By July she completed the Cloud Resume Challenge and two additional projects. She passed the Solutions Architect Associate exam in September. She applied to 47 positions over the following two months. She accepted a cloud support engineer role at a mid-size SaaS company in October for $78,000 — a 50% salary increase.
Her advice: "I told every interviewer exactly what I told my students — I learn fast, I explain things clearly, and I do not give up. Those are the same skills. The domain is different."
Eighteen months later she was promoted to cloud engineer at $98,000.
David: Retail Store Manager to DevOps Engineer (11 months)
David managed a retail electronics store in London for six years. He was responsible for inventory systems, staff scheduling, and operations — work that translates directly to infrastructure management, on-call rotations, and incident response.
He started with Azure Fundamentals because his local job market was Azure-heavy. He studied during his commute (audio courses) and evenings. He passed AZ-900 in two months, then AZ-104 in four months. He built three projects: a serverless inventory tracker, a CI/CD pipeline for a Node.js app, and a monitoring dashboard.
He joined the London Azure User Group and volunteered to give a five-minute talk about his career change. After the talk, two people in the audience offered to refer him to open positions. He interviewed at both companies and received an offer at GBP 38,000 as a junior DevOps engineer. Within two years he was earning GBP 62,000.
Amara: Call Center Agent in Lagos to Cloud Support Engineer (10 months)
Amara worked at a telecommunications call center in Lagos handling technical support tickets. She was already diagnosing network issues and guiding customers through troubleshooting steps — foundational cloud support skills.
She studied AWS Cloud Practitioner using free resources and passed in six weeks. She then studied for the Solutions Architect Associate while building portfolio projects on the AWS free tier. She applied to remote positions listed on Turing and We Work Remotely.
She was hired as a remote cloud support engineer by a US-based startup for $24,000 per year — nearly three times her call center salary. Within 18 months she transitioned to a cloud engineering role at $42,000 per year, working remotely from Lagos.
Her advice: "Do not let anyone tell you that being in Africa means you cannot get cloud jobs. The internet does not care where you sit. Your GitHub and your certifications speak for themselves."
Addressing Your Fears Directly
"Am I too old to switch careers?"
No. The average age of career changers entering cloud computing is 34, according to a 2025 survey by A Cloud Guru. I have personally met successful career changers in their 40s and 50s. Cloud computing is a knowledge-based field — what matters is what you know and what you can build, not when you were born.
The industry values maturity, communication skills, and professional experience. A 42-year-old with 15 years of project management experience who can also configure AWS infrastructure is more valuable than a 22-year-old who only knows AWS. Your age is a strategic asset, not a liability.
"Do I need a computer science degree?"
No. According to a 2025 HackerRank survey, 37% of working cloud engineers do not have a CS degree. Many have degrees in unrelated fields — education, business, biology, music. Some have no degree at all.
What you need instead: certifications (which prove technical knowledge), a portfolio (which proves practical skill), and communication ability (which proves you can work with teams). These three things together are more convincing to most hiring managers than a CS degree alone.
That said, if you want to progress to senior architectural roles at large tech companies (FAANG-level), having some formal CS knowledge helps — particularly data structures, algorithms, and operating systems. You can learn these through free resources like MIT OpenCourseWare or paid platforms like Coursera. But you do not need them to get started.
"Can I do this from Africa?"
Yes. Unambiguously yes. Remote work has permanently changed the hiring landscape. Companies like Andela, Canonical, GitLab, Automattic, Toptal, and Turing actively recruit cloud talent from Africa.
The challenges are real: power reliability, internet stability, and timezone management require planning. Invest in a UPS battery backup and a secondary internet connection (mobile hotspot). Schedule your availability around your employer's core hours. These are solvable problems.
The career development resources at Citadel include specific guidance for building a cloud career from Africa, including remote job boards, salary negotiation for international roles, and infrastructure recommendations.
Read our deep-dive: Cloud Engineering Careers in Africa 2026 for salary benchmarks across Lagos, Nairobi, Johannesburg, and Accra.
"I have no IT experience at all. Is that really okay?"
It is okay. Most cloud skills are learnable in months, not years. The 12-month timeline in this guide assumes zero prior IT experience. You will not be competing against people with decades of systems administration experience for the same junior roles — the hiring pipeline is different.
What transfers from non-IT careers: troubleshooting (call center, retail, teaching), documentation (education, administration), process management (operations, logistics, project management), client communication (sales, customer success, consulting). Identify which of these you already have and emphasize them.
"What if I invest time and money and it does not work out?"
The total financial investment for this path is approximately $300-600 (two certification exams, practice tests, maybe one paid course). The time investment is 800-1,000 hours over 12 months. Compare that to a university degree (4 years, $40,000-$200,000) or a coding bootcamp (3-6 months, $10,000-$20,000).
If you follow this plan and discover cloud engineering is not for you, the skills you have learned — Linux, networking, automation, infrastructure as code — transfer directly to cybersecurity, data engineering, site reliability engineering, and dozens of other technical roles. This is not a dead-end investment.
Frequently Asked Questions
Which cloud platform should I learn first — AWS, Azure, or GCP?
Start with AWS if you are unsure. AWS holds the largest market share (31% as of Q1 2026), has the most job postings, and has the most mature certification program. If your local job market is heavily Microsoft-oriented (government, enterprise, healthcare), start with Azure. GCP is a strong third choice, particularly for data engineering and machine learning roles, but has fewer entry-level positions.
How much does the full career transition cost?
Budget $300-600 total: $100-165 for the foundational certification exam, $150-300 for the associate exam, and $30-50 for practice tests. All learning resources can be free (AWS Skill Builder, Microsoft Learn, YouTube, Citadel's free courses). Cloud practice stays within free-tier limits if you are careful to shut down resources when you are not using them.
Can I do this while working a full-time job?
Yes. The timeline assumes 15-20 hours per week of study alongside full-time employment. That is roughly two hours per day on weekdays and three hours per day on weekends. Many career changers study during lunch breaks, commutes, and early mornings. Consistency matters more than marathon sessions.
Do I need to learn programming?
You need basic scripting ability, not software engineering expertise. Learn Python or Bash to a comfortable level — enough to write automation scripts, read code, and modify existing tools. You do not need to build full applications. Most cloud engineering roles require scripting fluency, not software development mastery. Expect to spend 50-80 hours learning Python basics — loops, functions, file handling, API calls.
How long before I earn more than my current salary?
The median career changer sees a salary increase within 12-18 months of starting their transition. The specific timeline depends on your current salary, your target market, and how aggressively you job search. In the US, entry-level cloud roles start at $65,000-$85,000. If your current salary is below that range, you will likely see an increase with your first cloud role.
What if I fail a certification exam?
Retake it. The pass rate for first-time AWS Cloud Practitioner test-takers is approximately 75%. If you fail, you get a detailed score breakdown showing which domains need more study. Wait two weeks, study the weak areas, and try again. The retake fee is the same as the original exam. Failure is a data point, not a verdict.
Is cloud computing going to be replaced by AI?
AI is changing how cloud engineers work, but it is not replacing the role. AI tools like GitHub Copilot, Amazon CodeWhisperer, and infrastructure automation assistants are making cloud engineers more productive — they can configure environments faster and troubleshoot more efficiently. But someone still needs to design the architecture, make security decisions, manage costs, and respond to incidents. AI is a tool for cloud engineers, not a replacement for them. In fact, the rise of AI has increased demand for cloud infrastructure — every AI model needs compute, storage, and networking.
Your Next Step
You have the roadmap. You have the timeline. You have proof that people with no IT background have done this before you.
The gap between where you are now and your first cloud role is not talent or intelligence — it is hours of practice. Twelve months from now, you could be writing Terraform configurations, deploying containers, and troubleshooting production systems. Or you could be in the same job, wishing you had started.
Start today. Open an AWS or Azure free-tier account. Watch the first module of a Cloud Practitioner course. Install WSL on your laptop and type your first Linux command.
If you want structured guidance, browse our free cloud courses for step-by-step learning paths. If you are ready to accelerate, the career development collection includes resume templates, interview preparation guides, and salary negotiation playbooks designed specifically for career changers entering cloud computing.
The cloud does not care about your degree. It does not care about your age. It does not care where you live. It cares whether you can build things that work. Start building.