Is Switching to Cloud Engineering at 35 Realistic?

Here’s my two cents: First off, focus on practical skills rather than titles. Mastering languages like Python, Terraform, and getting familiar with Linux and networking will definitely help. You should aim to understand how to move applications efficiently and securely. Once you nail those basics, you can dive into more advanced topics like CI/CD pipelines and cloud infrastructure.

I completely relate to this! At 38, I switched from warehouse work to IT, and it was a game changer. My salary tripled in just six months! If you’re just getting started, don’t hesitate to reach out. I can share what I did to make the transition.

Entering the cloud engineering field can take some time—think more than a year, especially if you start from the ground up. I moved into cloud after several years of help desk experience. Cloud support roles are a bit rare, but getting a solid foundation in Linux systems and basic cloud management is key. Expect to be on call quite often, too, as issues can arise any time of day. It’s much more about understanding systems than just following job descriptions.

I made my switch at 35, and I have no regrets! I began as a trainee with a cloud consulting firm after getting my Azure certifications. While they may not directly help with daily tasks, they show potential employers you have a grasp of the basics and are motivated to learn. Just keep in mind that this career requires genuine interest and a lot of self-study, but if you're passionate about it, you can really excel!

Many think AI will take over tech roles, but from my experience, organizations are still cautious about fully relying on it, especially for critical setups. You’ll still need to understand the theory and processes behind things like pipeline automation. AI can assist but knowing how to manually configure and troubleshoot is invaluable.