Working in the Cloud
The cloud job titles teams actually hire for and how to build real, provable hands-on experience with AWS, Azure, and Google Cloud without spending money.
This topic turns what you have learned across the rest of this course outward, toward the job market. You already know how the cloud works, what the service models mean, and how security and reliability get handled. This topic answers a more practical question: which job title matches the work you want to do, and how do you get real, hands-on proof you can do it before anyone pays you to.
What This Topic Covers
- the core cloud job roles teams hire for, including Cloud Engineer, Cloud Architect, DevOps Engineer, Site Reliability Engineer, and Cloud Security Engineer, and what each one owns day to day
- the boundary between a Cloud Architect's design authority and a Cloud Engineer's build-and-operate scope, the pair most job postings blur together
- what AWS, Microsoft Azure, and Google Cloud each actually give you for free, including the real difference between a time-limited trial credit and a perpetual Always Free allowance
- how to protect a free-tier account from a surprise bill with a budget alert, and which lab platforms let you practice inside a sandboxed environment instead of your own account
- how to turn free-tier access into a concrete, resume-ready first project
Why It Matters
Knowing the difference between a Cloud Engineer posting and a Cloud Architect posting tells you which jobs to apply for and which skills to highlight, instead of treating every "cloud" listing as interchangeable. Understanding DevOps and Site Reliability Engineering as software engineering applied to operations, rather than as rebranded system administration, changes how you read those postings and how you talk about the work in an interview.
None of that matters on paper alone. An interviewer wants to know you have actually launched an instance, attached storage, and scoped an IAM role, not that you read about how to do it. Every major provider gives you a real way to build that proof for free, but each one hides real limits behind the word "free," and mixing up a 90-day trial credit with a perpetual free allowance is exactly how a learner ends up with either an unexpected bill or an account that stops working mid-project. This topic gives you both halves: the map of where you fit, and the hands-on evidence to back it up.