How to become a Cloud Engineer / Solutions Architect
A complete, honest roadmap for the skills cloud engineers and solutions architects actually use, from networking and core services through infrastructure as code, security, reliability, scaling, cost, containers, architecture trade-offs, communication, and AI. It runs top to bottom, foundational to advanced, so you always know what comes next. Free to read, no signup required.
How to use this: tap a step on the map to open its details, skill pills, and guidance in a side panel. Work down the spine in order; each stage assumes the ones above it. The cloud is learned by building on it, so use a real account as you go, because the concepts only stick once you’ve deployed them.
Design and deploy a real architecture
Nothing proves cloud ability like an architecture you designed, deployed, and can defend. A project that ties the pieces together is the most convincing thing you can show, because you can explain every trade-off you made.
Deploy a small app on a cloud, provisioned entirely with infrastructure as code from your repo.
Make it reliable: spread it across availability zones and add a load balancer and autoscaling.
Lock down access with least-privilege IAM and private networking, and encrypt data at rest.
Draw the architecture diagram and write a short note on your reliability, security, and cost choices.
Keep an eye on the bill and tear it down when you’re done. Being able to explain your trade-offs, and why you didn’t over-build, is exactly what an architecture interview looks for.
Frequently asked questions
They overlap. Cloud engineers lean toward building, automating, and operating cloud infrastructure hands-on. Solutions architects lean toward designing systems, weighing trade-offs, and working with stakeholders, often at a higher level and more customer-facing. Many people do both, and the titles vary by company, which is why this roadmap covers the shared foundation.
There’s real overlap in cloud, automation, and infrastructure. DevOps and SRE emphasise the pipeline, automation, and keeping running systems reliable, while cloud engineering and architecture emphasise designing and building the cloud infrastructure itself. In smaller teams one person may do all of it; in larger ones the focus differs.
Any of the major ones. AWS has the largest market share, but Azure and Google Cloud are widely used and share the same concepts. Learn one deeply enough to understand core compute, storage, networking, and identity, and most of it transfers to the others.
They can help, especially for getting past hiring filters and giving your study a structure, and cloud certifications are among the more respected in tech. That said, they’re no substitute for having actually built and run things. Treat a certification as a way to organise learning, not the finish line.
It depends far more on hands-on practice than any fixed timeline. Many people move in from software, operations, or system administration by adding cloud, infrastructure as code, and architecture skills. Building and deploying real systems on a cloud you can practise on is what accelerates it.
No. Networking, core services, infrastructure as code, security, and architecture fundamentals are the core. Deep cost optimization, specific services, and the architect communication skills you deepen as your role demands, and cloud engineering and architecture roles emphasise different parts.
Ready to prepare for real interviews with a personalized plan?
This roadmap is the map. When you’re ready to actually get hired, Interview Ready turns it into a personalized 30-day plan built around your resume and a specific target role: real practice in the right order (cloud fundamentals, architecture design, security/IAM/networking, cost and migration), a guided Build-a-Project track alongside it, and progress tracking the whole way. Start free.
