I'm 40 and recently lost my job after nearly 18 years in a stores issuing and receiving role involving SAP and SAP S/4HANA. I'm currently studying for AZ-900 and considering a transition into cloud or broader IT work, eventually aiming toward Azure cloud engineering or architecture.
I've been interested in technology since the DOS and 486 PC era. I've repaired and configured Windows systems, rebuilt boot records and boot loaders, built gaming PCs, solved everyday hardware and Wi-Fi problems, configured printers and home networks, removed malware from Android phones, and experimented with reinstalling mobile operating systems. My networking experience is mostly practical home troubleshooting rather than enterprise networking.
I've also started building a website that recommends software for different types of businesses. I used ChatGPT as a development aid, but the idea and project direction were my own, and I'm still completing some backend work. I'm unsure how relevant a project like this would be when applying for Azure or general IT roles.
What skills, certifications, and hands-on projects would make me a credible candidate for an entry-level or transitional IT role that could eventually lead to cloud engineering? What should I study after AZ-900, and what should I be able to demonstrate in interviews or a portfolio? I'm willing to learn Linux, networking, scripting, infrastructure as code, and other fundamentals.
I have a powerful desktop and another spare PC that I can use for Linux installations, virtual machines, and home labs. I'm a South African citizen, so I'd also appreciate guidance about working remotely for international companies and any location or work-authorization issues I should consider.
Is this career change realistic, and how should I structure my learning plan without trying to skip important steps?
3 Answers
It’s worth being realistic about the current market. Technology roles are highly competitive, with experienced people facing layoffs, outsourcing, and longer job searches. Cloud is not an automatic shortcut to employment, especially if you have financial responsibilities.
That doesn’t mean you should give up, but you should make the transition in stages, keep your expectations grounded, and consider adjacent IT or systems roles where your SAP and operational experience may give you an advantage. Build skills while applying broadly rather than waiting until you feel fully qualified for an architect title.
Cloud architect is a long-term destination rather than the best first target. Architecture usually requires substantial experience with application development, enterprise systems, infrastructure, and the trade-offs between different cloud services.
Your background may translate more naturally into cloud administration or IT operations first. Consider roles involving identity and access management, user onboarding and offboarding, application configuration, Microsoft services, integrations, support, or eventually security operations. Microsoft Learn has useful paths for these areas.
Certifications can help demonstrate direction, but they do not replace practical knowledge or experience. Present yourself as an experienced operations professional who is moving into cloud-enabled IT, rather than claiming to already be a cloud engineer. Your existing business and SAP experience could become a useful differentiator.
For a junior candidate, home labs can be valuable. If you apply for more senior positions, employers will generally focus much more on professional experience. The market is competitive, so building a realistic progression and highlighting your existing domain knowledge will matter.
Thanks for the practical advice. I’ll adjust my study plan and focus on building toward an entry-level cloud or administration role first.
It sounds like you’re trying to jump several steps ahead, so I wouldn’t make cloud architecture the immediate goal. AZ-900 is a sensible introduction, but cloud engineering still depends on traditional IT fundamentals.
Build a foundation in Linux, networking, Git, security, troubleshooting, and basic scripting. Then work hands-on with Azure services such as virtual machines, VNets, network security groups, Entra ID, storage, and monitoring. Once those feel comfortable, add Terraform and basic CI/CD.
You don’t need an expensive gaming PC for this. A modest Linux machine, virtual machines, a small VPS, or short-lived cloud resources are enough. Learning to use Terraform to create infrastructure, configure it, test it, and destroy it is more relevant than having powerful hardware.
Document your labs in a public code portfolio. Explain what you built, why you designed it that way, what failed, how you secured it, and how you fixed problems. That will be more persuasive than collecting certificates or presenting a project that was mostly generated by AI. Your age is not the main obstacle; fundamentals, demonstrable work, communication, and realistic job positioning matter more.
I appreciate the pointers. I’ll focus on fundamentals and make sure my projects are genuinely understood, documented, and explainable rather than relying on certificates alone.
Thanks for sharing the more cautious perspective. I’ll factor the market conditions into my plan and look at adjacent roles instead of relying on a single cloud-engineering target.