Cloud Engineer

5 stops · self-paced · a common path, not the only one

1. 📍

   You are here

   Today — wherever you're starting from

2. 🌐
   ConnectNext stop →

   Learn the basics of Linux and networking

   Linux and networking basics come first — the cloud is just someone else's Linux machines on a network. Skip this and everything later is shaky.

   ⏱ self-paced · 💵 free–low cost

3. 📍
   Milestone

   Get comfortable with one cloud (AWS, Azure, or GCP)

   Go deep on one cloud (AWS, Azure, or GCP) rather than skimming all three — the concepts transfer, and depth is what gets you hired.

4. 🎓
   Education

   Earn an entry cloud certification (e.g., AWS Cloud Practitioner → Associate)

   An entry cert (like AWS Cloud Practitioner → Associate) proves your basics and gives a clear study path. Respected and affordable.

   ⏱ ~2 years · 💵 lower-cost than a 4-year degree

5. 📚
   Learn

   Learn a scripting language and infrastructure-as-code (Terraform)

   Scripting plus infrastructure-as-code (Terraform) is what separates a cloud engineer from a cloud user — automation is the actual job.

   ⏱ self-paced · 💵 free–low cost

6. 🔨
   Build skills

   Apply for cloud/DevOps roles with a few real projects to show

   A few real projects (a deployed app, an automated setup) you can talk through matter more than the cert alone when you apply.

   ⏱ self-paced · 💵 free–low cost

7. 🏁

   Cloud Engineer

   Your destination