Back to Blog

IT Technician to Cloud Engineer: My 2-Year Roadmap

Transitioning from an IT Technician role to Cloud Engineering is a journey I'm actively pursuing. It's not just about learning a specific cloud provider; it's about building a solid foundation in systems engineering.

The Strategy

The consensus from industry experts is clear: Cloud Engineering is just Systems Engineering adapted for the cloud.

Skipping the fundamentals of Linux and networking to jump straight into AWS or Azure often leads to gaps in knowledge. That's why my roadmap is structured to bridge the gap through a dedicated Linux Sysadmin phase.

Phase 1: The Foundation (Current)

My immediate focus is on the core infrastructure skills that every engineer needs, regardless of platform.

  1. Networking: CompTIA Network+ (Completed). Understanding subnets, DNS, TCP/IP, and routing is non-negotiable.
  2. Linux Mastery: Red Hat Certified System Administrator (RHCSA). This isn't just about learning commands; it's about understanding how the OS works, managing services, storage, and security.
  3. Scripting: Bash and Python. Moving from "clicking buttons" to "writing code" to solve problems.

Phase 2: Linux Sysadmin

The goal for 2026 is to transition into a Junior Linux Sysadmin role. This role is pivotal for:

  • Gaining real-world experience with server management.
  • Learning configuration management tools like Ansible.
  • Understanding enterprise-scale infrastructure.

Phase 3: The Cloud

Once the Linux foundation is solid, the transition to cloud becomes a natural evolution rather than a steep learning curve. The target technologies for this phase include:

  • AWS Solutions Architect Associate
  • Terraform for Infrastructure as Code (IaC)
  • Docker & Kubernetes for container orchestration

Why Linux First?

Linux runs the cloud. Whether it's EC2 instances, containers, or serverless functions, there is almost always a Linux kernel underneath. By becoming a proficient Linux administrator first, I'm future-proofing my career and ensuring I understand the "how" and "why" behind the cloud services I'll be managing.

This journey is a marathon, not a sprint. I'm documenting it here to keep myself accountable and hopefully help others on a similar path.