I'm 40 and recently lost my job after nearly 18 years working in stores issuing and receiving, including SAP and SAP S/4HANA responsibilities. I'm currently studying for AZ-900 and exploring whether a transition into Azure or another cloud-related role is realistic.
I've been interested in technology since the DOS and 486 PC era. Over the years I've learned to troubleshoot Windows systems, repair boot records, build gaming PCs, solve basic networking and Wi-Fi problems, configure printers, remove malware from phones, and reinstall or customize operating systems. I also have some experience creating a small website as a side project, using AI tools to help with development while learning along the way.
My long-term goal is to move toward cloud engineering or eventually cloud architecture, but I'm open to starting with a more realistic entry point such as cloud administration, technical support, infrastructure, or security operations. What skills, certifications, and home lab projects would make me a credible candidate? Should I focus on Linux, networking, scripting, Terraform, CI/CD, Azure services, or something else first?
I have a powerful desktop and another spare computer that I can use for Linux installations, virtual machines, and lab environments. I'm also a South African citizen, so I'd appreciate advice about preparing for remote work and becoming employable internationally. Is this career change feasible, and what would a practical study and project roadmap look like?
3 Answers
Cloud architect is probably too distant as a first target. Architecture usually comes after years of working with infrastructure, applications, networking, security, and enterprise systems. Given your background, cloud administration or infrastructure support may be a better starting point. You could build toward identity and access management, application onboarding, integrations, Microsoft 365 or Azure administration, and eventually security or a SOC role.
Certifications can help show direction, but they are not a substitute for practical ability. Your SAP and operations background is valuable, so present yourself as an experienced operations professional moving into cloud implementations rather than as a senior cloud engineer from day one. The market is competitive, so use your existing domain experience as part of your advantage.
It’s worth acknowledging that the technology job market is difficult right now. There are many experienced candidates competing for roles, while layoffs, outsourcing, and automation have reduced some opportunities. A career change is still possible, but it may take longer than a short certification-focused timeline and could involve applying broadly to support, infrastructure, systems, or junior administration roles first.
Before committing fully, make a realistic financial and time plan. Keep your existing operational and SAP experience central to your job search, because combining that background with cloud skills may be more valuable than competing directly with people who already have years of cloud engineering experience.
You’re likely trying to skip several important steps. AZ-900 is a useful introduction, but cloud engineering still depends heavily on traditional IT fundamentals. Prioritize Linux, networking, Git, security basics, troubleshooting, and scripting. Then build hands-on Azure labs involving virtual machines, VNets, network security groups, Entra ID, storage, backups, and monitoring. After that, learn Terraform and basic CI/CD.
Document your projects in a public code repository. Explain the design decisions, costs, security considerations, failures, and troubleshooting process. A lab where you provision infrastructure with Terraform, configure it, monitor it, and then tear it down will usually demonstrate more than simply collecting certificates. You do not need an expensive gaming computer; virtual machines, a modest VPS, or carefully managed cloud resources are enough.
Being 40 is not the main obstacle. Building solid fundamentals, gaining demonstrable experience, and presenting your previous work effectively matter much more. Also be transparent about where AI helped with a project and make sure you understand and can maintain everything you submit.
That makes sense. I’ll adjust my plan toward fundamentals and a realistic first role instead of aiming straight for architecture. I’ll also make sure I can explain and maintain anything I build.