The non-CS cloud roadmap: from zero to a junior Azure role in 6 months
Most roadmaps are a wall of logos. This one is a calendar — what to do each month, how many hours, and the boring bridge nobody sequences: a little Git, Linux, and networking before Azure. No CS degree required.
New to cloud? CAMPUX is a free, build-first course. Start here →
Search "cloud engineer roadmap" and you get an infographic with forty logos and no order of operations — useless if you are starting from a non-technical job and cannot tell which logo comes first. This is the version that respects your situation: you have a full-time job, no computer-science degree, and about fifteen hours a week. Six months of that, sequenced properly, gets you to junior-Azure-ready. Here is the month-by-month, including the part every other roadmap skips.
You can reach junior-Azure-ready in about six months at ~15 hours a week without a CS degree — if you spend the first month on the pre-Azure bridge (a little Linux, Git, and networking), then Azure fundamentals, then two portfolio projects. Here's the part most roadmaps skip.
The pre-Azure bridge — the month everyone skips
The reason non-CS beginners stall is not Azure. It is that Azure quietly assumes three things you were never taught, and every tutorial glosses over them. You do not need mastery — you need enough. Spend month one here and the rest stops feeling like a foreign language.
| Prerequisite | Why Azure needs it | How much / where |
|---|---|---|
| Git | Everything you build is stored and shared in Git; pipelines deploy from it | Enough to commit, branch, push — Class 17 |
| Linux command line | Most cloud servers are Linux; the CLI is how you actually operate them | Enough to move around a shell — free on Microsoft Learn |
| Networking basics | Half of Azure is connecting things — IPs, subnets, DNS | Enough to read an IP and a subnet — Class 10 |
The month-by-month plan (15 hours a week)
- The bridge. Git, the Linux CLI, and networking basics — just enough of each. Deliverable: a GitHub account with a repo you can push to, and the confidence to open a terminal. Maps to Class 17 and Class 10.
- Azure fundamentals + core services. What the cloud is, the service models, identity, and the core building blocks. Start the free Azure account with the guardrails on. Deliverable: AZ-900 either passed or comfortably within reach, and your first resources deployed by hand.
- Networking, identity, and storage in depth. The AZ-104 heart: VNets, RBAC, storage accounts. Everything hands-on in your subscription. Deliverable: a small network you built and can explain.
- Infrastructure as code and CI/CD. Bicep or Terraform, plus a GitHub Actions pipeline. This is what turns "I clicked around the portal" into "I automate." Deliverable: a resource you deploy from code, not clicks.
- Two portfolio projects. The three small projects or the Cloud Resume Challenge. Deliverable: two things on GitHub you can walk a stranger through.
- Polish and apply. Resume rewritten around projects, interview answers rehearsed, applications going out to roles you match 60–70%. Deliverable: a pipeline of applications and a story you can tell.
If protecting fifteen hours is not realistic, run the same six steps over nine months at nine or ten hours. The order is what matters, not the calendar. For a paced day-by-day version, the 100 Days of Azure plan lays the whole thing out.
Translating a non-tech job into resume keywords
Your last job is not a gap — it is a source of the exact soft skills managers screen for, once you translate it into the right words. A recruiter's filter does not know what a shift lead is; it knows "incident handling" and "stakeholder communication."
| What you did | How it reads on a cloud resume |
|---|---|
| Ran a shift / managed a floor | Coordinated operations under pressure; incident handling; on-call temperament |
| Taught a class | Documentation; explaining complex systems to non-technical audiences |
| Handled customers / support | Ticket triage; troubleshooting; stakeholder communication |
| Coordinated logistics | Process automation mindset; dependency and change management |
None of this is a stretch — it is the same work, named the way hiring systems read it.
The free path — no card, ever
You can run this entire roadmap for £0. Microsoft Learn is free. The Azure free account gives you credit and always-free services — keep it that way by following the guardrails in how to practise Azure without a surprise bill. CAMPUX is free with no card. The only thing you might choose to pay for later is an exam fee, and that is optional to start applying. The barrier to this career is time and consistency, not money.
The bridge is the month everyone skips — and the reason everyone who skips it stalls.
The honest gap: certified is not hired
Notice the roadmap does not end at a certificate. It ends at projects and applications, because that is what actually gets you hired. A cert proves you can pass a test; a project a stranger can inspect proves you can do the work. Plenty of people collect three badges and wonder why the interviews do not come — it is because there is nothing behind the badges. Build the two projects. They are the difference. The full portfolio guide goes deeper.
Who this timeline is not for
Honesty hedge, because a plan that pretends to fit everyone fits no one. If you have no IT literacy at all — you are not comfortable installing software or navigating a computer — add a month at the front for that. If you genuinely cannot protect ten-plus hours a week, be kind to yourself and plan for nine to twelve months instead of six; a slower plan you finish beats a fast one you abandon. And if you are wondering whether a non-IT person can learn Azure at all — yes, and that is the exact person this roadmap was written for.
Questions people also ask
Can I become a cloud engineer without a computer science degree?
Yes. A CS degree is not a requirement for cloud work — most teams care about demonstrable skills and hands-on projects, not a diploma. Plenty of cloud engineers came from support, admin, teaching or trades. What you do need is basic IT literacy and proof you can build things, which is exactly what this roadmap and a couple of portfolio projects give you.
How many hours a week do I need to learn Azure in 6 months?
About 15 hours a week is a realistic pace to reach junior-ready in six months. That's roughly two hours on weeknights plus a longer weekend session. If you can only protect nine or ten hours, the same plan still works — it just stretches closer to nine months. Consistency matters more than intensity; a steady 15 hours beats occasional all-nighters.
What should I learn before Azure — Git, Linux, or networking?
All three, lightly, in the first month. You don't need mastery — you need enough Git to save and share code, enough Linux command line to move around a server, and enough networking (IP addresses, subnets, DNS) to understand what Azure is connecting. This bridge is the step most roadmaps skip, and it's where non-CS beginners usually stall.
Is six months realistic to get a junior cloud job?
Six months to job-ready is realistic at 15 hours a week; landing the actual offer can take a bit longer and depends on your market and applications. The honest catch is that the certificate is not the finish line — the projects are. People who finish two portfolio projects and can talk about them interview far better than people who only passed an exam.
Do I need to pay for anything to follow this roadmap?
No. Microsoft Learn is free, the Azure free account gives you credit and always-free services, and CAMPUX is free with no card. If you stay inside the free tier and the guardrails, your out-of-pocket cost can be zero. The only thing you might choose to pay for later is the exam fee itself, and even that is optional to start applying.