Overview
A step-by-step roadmap for moving from tier-one helpdesk into a six-figure cloud architect role — with the CompTIA, AWS, and Azure certifications that actually move the needle.
On this page · 19 sections
- Quick Snapshot
- Year 1: Build the Foundation
- Months 1–4: CompTIA A+
- Months 5–8: CompTIA Network+
- Months 9–12: CompTIA Security+
- Year 2: Pick Your Cloud and Get In the Door
- AWS Solutions Architect — Associate
- Building Real-World Experience
- Year 3: Specialize and Architect
- AWS Solutions Architect — Professional
- Optional: Specialty or Multi-Cloud
- Salary Trajectory
- Time and Cost Estimates
- Common Mistakes to Avoid
- Frequently Asked Questions
- Can I compress this into 2 years?
- What if my current employer doesn't use cloud?
- Should I learn Linux, Terraform, or Python first?
- Is the AWS Cloud Practitioner cert worth it?
Most people we talk to who want to "get into cloud" already have a foot in IT. They're answering Tier 1 tickets, swapping laptops, resetting passwords, and watching the cloud engineers in the next room earn twice their salary. The path forward exists — it's just rarely documented end-to-end.
This is the roadmap we hand to motivated helpdesk technicians and entry-level IT generalists. It's three years, four to six certifications, and a clear set of milestone projects. Follow it and you'll be a competitive Cloud Architect candidate by the end.
Quick Snapshot
| Year | Focus | Target Salary |
|---|---|---|
| Year 1 | Foundations + Security+ | $50–70k |
| Year 2 | Cloud Associate + first cloud job | $85–110k |
| Year 3 | Cloud Professional + architecture experience | $120–160k |
Year 1: Build the Foundation
Skip this year and your résumé reads "helpdesk turned cloud" and gets thrown in the no-pile. Do this year right and you'll be quoted in interviews for being well-prepared.
Months 1–4: CompTIA A+
If you don't have A+ yet, get it. It's the credential that gets you out of "show up and reset things" Tier 1 work and into broader operational roles where you'll see real infrastructure.
Months 5–8: CompTIA Network+
Cloud is networking. You will struggle every single day in your future cloud role if you don't understand subnets, routing, NAT, DNS, TLS, and the OSI model viscerally. Network+ forces this. Most students hate it while studying and love it 18 months later.
Months 9–12: CompTIA Security+
Security+ is the most-named cert in cloud job postings, and not just for security roles. Every cloud architect is expected to design with least-privilege, shared-responsibility, and compliance in mind. Get this one before you touch AWS or Azure.
Year 1 milestone project: Build a home lab. Use a refurbished tower, install Proxmox or ESXi, set up at least three VMs on a VLAN-segmented network, and document the build on a personal blog or GitHub. This single artifact carries more weight in interviews than any cert.
Year 2: Pick Your Cloud and Get In the Door
By month 12 you should have your foundations and a working home lab. Time to specialize.
AWS Solutions Architect — Associate
AWS still leads the cloud market in job postings (we cover the AWS vs Azure vs Google trade-offs here). For most students with no existing employer cloud preference, AWS SAA is the highest-leverage cert you can earn in months 13–18.
If your employer is heavily Microsoft-shop, Azure Administrator (AZ-104) is the equivalent move. If your shop is GCP-first, Google Associate Cloud Engineer is the equivalent.
Whichever you pick: stay in one cloud through year 2. Going associate-deep in one cloud beats going dabbler-shallow in three.
Building Real-World Experience
This is where many people stall. Cert without practice doesn't get hired. Spend the second half of year 2:
- Build 3 real projects in your chosen cloud and put them on GitHub. Examples: a serverless image-processing pipeline, a multi-AZ web app behind a load balancer, an event-driven data ingestion pipeline.
- Apply internally to any cloud-adjacent role at your current company. DevOps engineer, junior cloud admin, systems engineer with cloud responsibilities — all count.
- If internal isn't available, apply externally with your home lab and project portfolio. You're shooting for a $85–110k role.
Year 2 milestone: First cloud-tagged paycheck. Title doesn't matter — what matters is that you're doing cloud work, not helpdesk, for ~6+ months by the end of year 2.
Year 3: Specialize and Architect
You're now an associate-level cloud engineer or junior architect with real production exposure. Two finishing moves take you to architect.
AWS Solutions Architect — Professional
(Or Azure Solutions Architect Expert AZ-305 / Google Professional Cloud Architect.) The professional-tier exam tests architecture decisions: cost optimization, multi-region strategy, hybrid connectivity, security at scale, migration patterns. Most students take 150+ hours to prepare and many fail the first attempt — budget for one retake.
Optional: Specialty or Multi-Cloud
If you have specific career goals — security architecture, machine learning, data engineering — a specialty cert (AWS Security Specialty, Azure AI Engineer, GCP Data Engineer) signals depth. Otherwise, multi-cloud literacy beats multi-cloud certification. Knowing how Azure does what AWS does is a force multiplier in vendor-neutral architecture roles.
Year 3 milestone: Lead the design of a production system. It doesn't have to be massive. A migration of one app, a re-architecture of an inefficient pattern, a security overhaul. Get architecture decisions on your résumé and in your interview stories.
Salary Trajectory
Rough US-based numbers (vary heavily by metro and industry):
| Role | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| Helpdesk / IT Generalist | $50k | — | — |
| Cloud Engineer | — | $95k | — |
| Cloud Architect | — | — | $145k |
The biggest jump is typically year 1 → year 2. The architect-level salary requires both the certification and the documented architecture experience.
Time and Cost Estimates
Reasonable budget over three years:
- Cert exam fees: $1,500–2,500 total
- Training and courseware: $4,000–8,000 if you self-study; $8,000–18,000 if you take instructor-led courses
- Home lab hardware: $300–1,500 (Used enterprise gear is your friend)
- Total: $6,000–22,000
Most employers reimburse a significant portion of cert and training cost — especially once you have a cloud-tagged role in year 2.
Common Mistakes to Avoid
- Collecting certs without projects. Three certs and no GitHub will lose to one cert and three documented projects.
- Skipping Network+. Always regretted.
- Jumping clouds mid-year. Stay in one ecosystem until you're solid; multi-cloud comes later.
- Studying for tests, not concepts. If you can pass the exam but can't explain VPC peering vs Transit Gateway in plain English, you're not ready.
Frequently Asked Questions
Can I compress this into 2 years?
Yes, if you can dedicate 15+ hours per week to study and have an employer who'll move you internally. Most working adults can't sustainably do this without burning out.
What if my current employer doesn't use cloud?
Build your own. Home lab + personal AWS account + open-source contributions. Your portfolio becomes the proof; the next employer doesn't care that your current one is on-prem.
Should I learn Linux, Terraform, or Python first?
All three matter for an architect. Linux first (you'll use it daily), Terraform second (every interview will ask), Python third (sufficient scripting ability is plenty).
Is the AWS Cloud Practitioner cert worth it?
For someone with no IT background, sure. For someone with A+ and Network+, no — skip straight to Solutions Architect Associate.
Need an accelerated start? Our AWS-track courses are sequenced specifically for IT professionals moving into cloud. Check the course calendar for upcoming cohorts.
