Transitioning into cloud engineering through self-study, or any field for that matter, comes with a hefty dose of imposter syndrome. I’ve secured my AZ-900, AZ-104, AZ-700, and just finished grinding through the SC-300, now moving onto the AB-650. I’ve deployed an enterprise hub-and-spoke network via Terraform, built a serverless password vault using Azure Static Web Apps and Functions, and created a personal site through the Cloud Resume Challenge, expanding on the core project with my own Logic Apps implementation. But knowing how to build something from documentation is entirely different from operating in a production environment with an Agile team, ticket queues, and rigorous code reviews.
I realized that the main thing holding me back from applying with confidence was a lack of "real-world" operational experience along with that massive imposter syndrome weight. So, I decided to engineer it myself the best I could.
The Cloud Simulator
To bridge the gap between passing exams and operating in the wild, I’ve set up an ongoing, interactive simulation. I am utilizing an AI model not as a search engine, but as my Lead Cloud Architect and Project Manager.
Here is the premise: I am officially "clocked in" as a Junior Cloud/Platform Engineer. We run this just like a real Agile team:
The Daily Standup: I report on what I accomplished, what I’m tackling today, and any blockers I’m facing.
The Ticket Queue: My Lead Architect assigns me realistic, messy, Jira-style tasks. No exam style questions, just real business requirements.
Execution & PRs: I go off, research, write the Terraform configurations or automation scripts, and submit my methodology for review. To help build my knowledge and skills, no AI is allowed to be used, this must be done the old fashion way of reading documentation, and documenting every single decision and action I take on my own. I am using the standard engineer escalation protocol, Timebox and Escalate, to keep the tickets moving. Escalation is the only time I will consult with my AI model when I have reached my limit in the timebox.
Code Review: My work is graded on not only its functionality, but also evaluated for security, cost-optimization, and enterprise best practices.
What This Series Will Cover
I’m starting this blog series to document every single ticket I work on during this simulation. By treating this as a public engineering log, I want to show the unpolished reality of troubleshooting, the architecture decisions, and the iterative feedback loop that you don't always see in project tutorials.
You’ll see everything from configuring secure Azure Key Vaults with RBAC and VNet subnet rules (my first ticket you’ll be reading about here soon), to deploying CI/CD pipelines and automating administrative tasks.
If you are also self-studying your way into the cloud and are looking for a fun way to get some experience building the day-to-day troubleshooting and architectural muscles, follow along. Let's get to work.
Top comments (0)