32, Philosophy Degree, 18 Months to a $90K Junior Cloud Role: Here Is the Spreadsheet

I tracked every dollar and every hour of this transition before sitting down to write it. Starting from a philosophy degree, six years as an HR coordinator, and zero IT background, the path to a $90,000 junior cloud engineer offer took 18 months and $3,100 in direct costs. Those numbers are the headline. The rest of this article is what the numbers look like up close: which months were productive, which were wasted, what the rejection spreadsheet actually says, and the single move that shortened the job search more than any certification did.

Where I started: philosophy grad, HR coordinator, 32

My starting point was a philosophy BA from a mid-tier state university, six years as an HR and administrative coordinator at a nonprofit, and a salary of $52,000 with a realistic ceiling of about $65,000. I had read enough about cloud engineering salaries to understand the gap was worth bridging, and I had enough systems-thinking and writing background to believe the field was learnable. What I did not have was any clear idea which certifications to take, in which order, or how long the switch would realistically take. Most of the content I found online either assumed I already knew what AWS was or was written by people selling courses. This article is the version I needed. For what the cloud engineering role actually looks like day to day, start at /careers/cloud-architect before committing to the path.

Month 1-3: choosing a direction without wasting money

The first real decision was AWS vs. Azure vs. Google Cloud. For a career switcher starting in 2024, the answer was AWS, because it held roughly 31% of cloud market share (Gartner 2025) and because the AWS Solutions Architect Associate (SAA-C03) exam was consistently the most-cited credential in US cloud engineer job postings. Azure is equally valid for roles at Microsoft-heavy enterprises, but AWS has broader job market coverage for someone without an existing employer ecosystem to build around. I arrived at this after scanning about 60 cloud engineer job postings on LinkedIn over two weeks: AWS appeared in roughly two-thirds of them. For the full comparison of all three providers and which makes sense for your situation, see /learn/aws-vs-azure-vs-google-cloud-2026.

Before touching any AWS content, I spent 6 weeks on the Google IT Support Professional Certificate on Coursera ($49/month, completed in about 1.5 months). This was not strictly necessary, but it closed the foundational gap on networking basics, operating systems, and how computers communicate -- knowledge that AWS material assumes you already have. Skipping this step is a common mistake that makes Cloud Practitioner prep harder and slower than it needs to be. If you are coming from IT support or help desk, skip it and go straight to Cloud Practitioner prep. If you are coming from a fully non-technical background, the 6-week investment saves you later confusion.

The $1,019 in direct costs is meaningfully lower than the alternative I seriously considered: a coding bootcamp. In-person bootcamps averaged $13,584 in tuition in 2025 (Course Report 2025), and the better-known remote programs run $15,000-$20,000. Even the self-paced online bootcamps price at $5,000-$10,000. The certification path is not just cheaper in the abstract. It is cheaper in a way that changes the financial logic: at $90,000, the $1,019 cost recovers in roughly 6 days of post-hire pay. A $15,000 bootcamp takes nearly two years to recover at the same salary. The biggest single expense in my path was the SAA retake at $150. Tutorials Dojo practice tests, used earlier in prep, would have identified the gap before the exam. The total time investment across 18 months was 340 hours, not counting the job search itself.

Month 4-12: the AWS certification grind and the SAA failure

1. 1
   Months 1-3
   Google IT Support Certificate on Coursera. Six weeks at 8-10 hours per week. Covered networking fundamentals, operating systems, system administration, and basic troubleshooting. Cost: $73. This is the part most guides skip because it is not glamorous, but it made the AWS material legible.
   ~60 hours
2. 2
   Month 3-4
   AWS Cloud Practitioner (CLF-C02) prep and exam. Stephane Maarek Udemy course ($15) plus 20 practice questions each evening for two weeks. Passed on first attempt. This cert alone did not generate interview callbacks, but it established the AWS credential on my LinkedIn profile and removed one ATS filter.
   ~40 hours, $115 total
3. 3
   Months 4-8
   AWS Solutions Architect Associate (SAA-C03) prep, first attempt. 90 hours of video content, roughly 200 practice questions. Failed first attempt by 7 points. The exam tests scenario judgment more than fact recall: it asks things like 'a company needs to migrate a 50TB on-premises database with minimal downtime -- which AWS service combination is most cost-effective?' My mistake was treating the exam like a memorization exercise rather than a case-judgment one.
   ~90 hours, $175 total
4. 4
   Months 8-10
   SAA retake prep. Shifted almost entirely to Tutorials Dojo timed practice exams with no open browser tabs, reviewing wrong answers in detail before taking another exam. Passed the second attempt with 783 out of 1000 (passing score is 720). The Tutorials Dojo explanations for incorrect answers were more instructive than any video course section.
   ~50 hours, $150 retake
5. 5
   Months 10-14
   Hands-on project phase on AWS free tier. Built three projects: a serverless resume website using the Cloud Resume Challenge (S3, CloudFront, DynamoDB, Lambda, CodePipeline), a custom VPC with public and private subnets, and a basic CI/CD pipeline. All three went on GitHub with README documentation explaining the architecture and what broke during build.
   ~100 hours
6. 6
   Months 14-18
   Job search: 43 applications across 16 weeks. 6 phone screens, 2 technical interviews, 1 offer at $90,000 base salary from a cloud consulting firm. The second technical interview went to a final round at a SaaS company before they selected a candidate with 2 years of prior DevOps experience.
   16 weeks active search

What most career-switch guides miss

Every cloud career-switch guide focuses on certifications. Cloud Practitioner, then SAA, then maybe CKA (Certified Kubernetes Administrator, the exam for managing Kubernetes clusters). That sequencing is correct as far as it goes. But the thing no guide told me was that certifications are the floor, not the differentiator. When I reached the technical interview stage, the question that moved both conversations forward was not 'which AWS service handles X use case?' It was 'walk me through something you actually built.' The ATS filter passes your resume to a human when you have the cert. The human schedules a phone screen. But the phone screen becomes a technical interview when you can say: 'Here is the GitHub link. Here is what broke during the VPC build, here is how I diagnosed it, here is what I changed.' The GitHub portfolio is what converts phone screens into technical rounds. Review the full day-to-day role description at /learn/what-does-a-cloud-architect-do-2026 if you want to know exactly what you are preparing for.

The second gap in most guides is the ATS reality. Of my 43 applications, 28 generated no response at all. Most were roles where AWS SAA was listed as 'preferred' rather than 'required,' and where I had no prior cloud job title in my work history. ATS systems at companies with more than 1,000 employees are pattern-matching on job titles and keyword density, not reading your cover letter. Two changes turned my callback rate around: first, I stopped applying to large enterprises and focused on cloud consulting firms and mid-size SaaS companies that review resumes manually. Second, I moved my certifications section to the top of the resume, above the work experience, after finding this advice in a thread on r/AWSCertifications. Both changes cost nothing. The callback rate went from about 7% to 21% after those two edits. The job posting volume is genuinely large -- demand for AWS-certified professionals grew 34% year-over-year (DigitalCloud Training 2026) -- but the competition at the junior level is real.

Month 11-14: the project layer that changed the trajectory

The Cloud Resume Challenge, created by Forrest Brazeal, was the single most valuable exercise in the entire 18-month path. The challenge has you build a resume website hosted on AWS S3, served through a CloudFront distribution, backed by DynamoDB for a visitor counter, and deployed via a CI/CD pipeline using CodePipeline and Lambda. It sounds complicated listed that way, but the challenge documentation walks through every service. The result is a real, publicly accessible project that touches six AWS services and demonstrates you understand how they connect. Both technical interviewers mentioned the Cloud Resume Challenge by name, and one asked detailed questions about how I handled the CloudFront cache invalidation step. The challenge is free. The AWS costs to run it are typically under $3 per month on the free tier. For what this role pays as you advance beyond the $90K starting point, see /learn/cloud-architect-salary-guide-2026.

The hands-on project phase also locked in knowledge that video courses alone could not. When I built the VPC project, I misconfigured the route table and a private subnet instance lost internet access. Diagnosing that error -- tracing route table rules, reading VPC Flow Logs, checking security group inbound rules -- taught me more about AWS networking than 20 hours of lecture content. The SAA exam asks exactly this kind of scenario question: a company's application in a private subnet cannot reach the internet; which configuration change resolves this? I had lived that question. The answer was not abstract anymore.

Month 14-18: the job search by the numbers

The job search ran 16 weeks. Total applications: 43. Of those, 28 received no response (65%). Nine received a polite rejection email (21%). Six received a phone screen invitation (14%). Of the 6 phone screens, 4 ended after the first call -- typically after I confirmed I had no prior cloud job title -- and 2 advanced to technical interview rounds. Of the 2 technical interviews, 1 produced a final-round offer at $90,000 base salary from a cloud consulting firm, and 1 went to a final round at a SaaS company that ultimately chose a candidate with 2 years of DevOps experience. The junior cloud market has 7,000+ open roles at any given time (LinkedIn 2026), but the market is more competitive than it was in 2021-2022 -- larger employers are now running multi-stage processes and favoring candidates with adjacent IT experience. For the full ROI breakdown on the SAA certification including which employers value it most, see /certifications/aws-solutions-architect.

“The AWS Solutions Architect Associate is the single credential that signals readiness for a first cloud role to most hiring managers. It is not sufficient on its own, but without it, non-traditional candidates are nearly invisible to the ATS systems at companies above 200 employees.”

Forrest Brazeal, AWS Community Builder and creator of the Cloud Resume Challenge

The $22,000 average premium figure (Global Knowledge 2025) understates the gain for career switchers coming from non-technical roles, because the starting point is lower. My administrative coordinator salary was $52,000. The first cloud offer came in at $90,000, a jump of $38,000. The $20,000-$35,000 range that Global Knowledge documents for career switchers who pair the SAA with hands-on project experience matches what the community reports consistently across r/AWSCertifications and similar forums. The early-career median (1-4 years of cloud experience) rises to $113,666 in total compensation (PayScale 2025), which means the $90,000 first-year offer is likely to grow meaningfully in years 2-3 without requiring additional certifications beyond what is already on the resume. The ceiling is real: senior cloud engineers at mid-market companies earn $140,000-$165,000, and at large enterprises $180,000+ with equity is common.

The tools that actually moved the needle, ranked

• Tutorials Dojo SAA-C03 practice exams by Jon Bonso (Udemy, about $15 at udemy.com on sale): the closest simulation of actual SAA exam conditions available. Use these timed, in exam mode, for the final 4 weeks of prep. Wrong answer explanations are as useful as the questions.
• Stephane Maarek's AWS Solutions Architect Associate course (Udemy, udemy.com): the clearest structured overview of the services and concepts tested on the exam. Start here, but do not stop here.
• The Cloud Resume Challenge (free at cloudresumechallenge.dev): the most impactful hands-on project for career switchers. Build it before you apply anywhere. Every interviewer recognizes it. Two asked follow-up architecture questions.
• AWS free tier (free): 12 months of real AWS console access at no cost for most services. Build everything here. The small overages from forgotten instances are cheap tuition for learning not to forget.
• Google IT Support Certificate on Coursera (coursera.org, $49/month): optional but valuable for the completely non-technical switcher. Closes the networking and operating systems gap before you hit AWS material that assumes that knowledge.
• r/AWSCertifications on Reddit (free): the most realistic community for exam difficulty feedback, study resource quality, and job search reality checks. Search before posting.

For a side-by-side breakdown of Coursera and Udemy as study platforms for this specific path, see /compare/coursera-vs-udemy. The short version: Coursera works better for structured certificates with official completion records (the Google IT Support cert matters), and Udemy works better for exam-specific prep courses (Maarek and Tutorials Dojo dominate this use case). Both serve different stages of the path.