|
Hello Reader, There are three kinds of cloud jobs right now. One of them is being automated as you read this, and most people doing it have no idea. After sitting on the hiring side for over 300 interviews this year, the questions have genuinely changed. Here is exactly which zone your role falls into, and the three moves that get you to green. Red zone: your work can be described as a ticketL1 cloud support: password resets, access requests, known-issue lookups, all run-book driven, all backed by documentation someone already wrote. This is not speculation. Salesforce's Benioff said on the Logan Bartlett show that they took support headcount from roughly 9,000 to 5,000 because AI agents absorbed a chunk of that work. A human-handled ticket costs $8 to $12. Nobody approving that budget picks the human. Next: QA and testing that is purely execution, go to this page, click this, check the result matches. That is a job description for an agent, not a person. Yellow zone: the numbers can look worse than red, and that's not a contradictionYellow has three roles, and the first one has the strongest data in this entire breakdown: the sysadmin moving into cloud. US Bureau of Labor Statistics projects minus 4% for network and computer system administrators from 2025 to 2035, a loss of over 13,000 jobs in a field assumed to be safe. There are still roughly 13,400 openings a year, but none of them come from growth. They come from attrition, retirement, people leaving. PagerDuty's SRE agent runs diagnostics on its own and executes approved fixes. AWS's DevOps agent cut incident resolution from an estimated 2 hours to 28 minutes on a live production disruption at Western Governors University. So why is this yellow and not red, given the numbers are worse? Because zones are defined by the shape of the work, not the severity of the statistics. A sysadmin still makes judgment calls: two patches land the same day, which goes first, what's the rollback plan, do you page someone at 3am or wait for standup. That cannot go on a ticket. That's the path across. Second yellow role: data analysts and engineers who run queries without connecting them to the business. Writing the SQL query is exactly what these models are good at. Knowing that revenue is 20% higher because sales changed how they tagged deals in July, something no model can infer from the data alone, is the other half, and it is not getting automated. Third: cloud program managers who cannot read an architecture diagram. The dividing question for every yellow role is the same: do you decide what gets built, or do you execute what someone already decided? Green zone: you decide, you design, you defendThree things define every green role, and some green roles are less technical than the red ones, which surprises people. First, cloud security engineer. Prompt injection, hallucination, tool poisoning are everywhere with agents right now, and nobody is going to let an agent sign off on whether another agent is safe to deploy. That accountability has to sit with a person. Second, platform and DevOps engineers, the people building the infrastructure every agent actually runs on. More agents deployed means more platform work, not less, because someone has to decide which agents get access to which internal APIs, and that is an architecture decision with a blast radius. Accenture posted a DevOps role requiring 4 years of CI/CD and Terraform plus a year of LangGraph or CrewAI specifically to build the framework the agents run on. Third, solutions architect and similar roles such as FDE. More model and service options means more ambiguity, not less, and deriving scope from that chaos is the job. Every design has competing trade-offs you have to defend, and once it's live, you own the outcome. GenAI has been out for 3 years, and there are more solutions architect roles open now than before it landed, not fewer. One more thing about green: the skills overlap. Forward deployed engineer, one of the hottest roles right now, is essentially coding plus solutions architect skills plus GenAI knowledge. The same skill set pivots into management, since a good architect already has the executive communication and technical depth that role requires. You are not picking one green role. You are picking a skill set that opens several. The three moves, sorted by zoneIf you're red, you have 90 days. Learn infrastructure as code, Terraform or CloudFormation, pick one. Ship one real AI agent project on AWS, not a tutorial. Learn to read a security finding well enough to understand what the scanner is telling you. And yes, pass Solutions Architect Associate, not because certificates get you hired, but because for red zone roles specifically it is the screening filter that gets you past the recruiter. Everything else on this list is what gets you through the actual interview. If you're yellow, you have 6 months. Do everything above, plus own one architecture decision end to end at your current job and write it down, not a ticket you closed, a decision you made with the trade-offs documented. When the system design review comes up, volunteer for that, not for fixing the ticket. If you're green, stay green. Move toward the parts of your role where you sign your name, and learn what the AI tools actually do so you are reviewing their output instead of being compared against it. Switching from mainframe to cloud in my mid-30s with none of this figured out is doable. I have watched a lot of people do it from a standing start. The map above is your 2027 roadmap. Reply with your zone, I read every one, and I'd answer the red ones first. Keep learning and keep rocking ๐, Raj P.S. If you have found this newsletter helpful, and want to dive deeper... Everything I teach on AWS, System Design, Kubernetes, and DevOps - all in one Skool classroom. Build the technical depth at your own pace, and get every new course I release: Join Hereโ ๐ฅ Free tutorials on Cloud Gen AI + interview prep on my YouTube channel: Hereโ ๐ The SA Bootcamp is the full transformation - hands-on practice through Cloud Colosseum, interview prep, mock interviews, and resume reviews, and so much more... โJoin the waitlist to be first in when the next cohort opens. |
Free Cloud Interview Guide to crush your next interview. Plus, real-world answers for cloud interviews, and system design from a top AWS Solutions Architect.
Hello Reader, I just unveiled the SA Bootcamp. The bootcamp covers everything you need to become an AWS Solutions Architect in as little as 3 months. Spoiler: itโs not just technical. New this cohort: full GenAI modules covering RAG, MCP, Agentic AI and more. Also now, including FDE - one of the hottest (and highest-paying) positions in cloud right now, and most candidates donโt even know how to start with applying. And hereโs why you need to move now. January and February are the biggest...
Hello Reader, We're just a few hours away from the LIVE SA Bootcamp Workshop! ๐ Start Time: October 17th 12pm Eastern Time Here's what's coming your way: The No-Code, No-Cert-Overload Blueprint to Becoming an AWS Solutions Architect & FDEI'm breaking down the exact system I've used to help 9 cohorts of IT professionals land AWS Solutions Architect and Gen AI roles including FDE at top companies, without writing a single line of code or drowning in certifications. Cloud migration/modernization...
Hello Reader, Are you thinking about becoming an AWS Solutions Architect and working at top companies? Data shows that Solution Architects earn between $200,000/year and $500,000+/year (screenshots below). The demand for AWS Solutions Architects has never been higher and will continue to rise because there are literally trillions of dollars worth of projects currently running on legacy technologies that need to be migrated to the cloud. When looking into becoming an SA it's really common to...