Road Mates EnterHow to become a Cloud Engineer, phase by phase: what you do in each one, how long it takes, and the proof that shows you're done.
6 phases2.5–5 years15 resources
Working daily in a Linux terminal, writing bash scripts, and studying networking basics like DNS, TCP/IP, subnets, HTTP and SSH. By the end, the person can stand up and troubleshoot a server from the command line without a GUI.
You're done when you can show
A GitHub repo of working bash scripts plus notes from configuring and debugging a self-hosted Linux server.
Resources
Picking one provider (AWS, Azure, or GCP) and hand-building real workloads: VPCs, compute, storage, IAM, load balancers, and managed databases, while studying for an associate-level certification. Produces a deployed multi-tier application and a passed exam.
You're done when you can show
An associate-level cloud certification (e.g. AWS Solutions Architect Associate) plus a live deployed app URL.
Resources
Stopping manual console clicks and rebuilding everything with Terraform or similar, adding Docker containers and a CI/CD pipeline that deploys on every commit. By the end, the whole environment can be destroyed and recreated from code.
You're done when you can show
A public GitHub repo with Terraform, Dockerfiles, and a passing CI/CD pipeline that deploys the app.
Resources
Polishing portfolio projects, writing up architecture decisions, applying to cloud, DevOps, or support-adjacent roles, and practicing system design and troubleshooting interviews. Ends with a signed offer for a role touching production cloud infrastructure.
You're done when you can show
A signed offer letter for a cloud, DevOps, or infrastructure position.
Resources
Owning real systems: handling on-call incidents, setting up monitoring and alerting, cutting costs, and hardening security under real constraints. Produces a track record of shipped infrastructure changes and resolved incidents.
You're done when you can show
A written incident postmortem or cost-reduction report you authored for a production system.
Resources
Shifting from executing tickets to designing architectures for reliability, scale, and multi-account security, and going deep in an area like Kubernetes, security, or platform engineering. Proves the ability to lead infrastructure decisions others build on.
You're done when you can show
A professional-level or specialty certification, or an architecture design doc you led that was adopted.
Resources
Walk this road with people on it.
Track each phase, post your proofs, and get matched with people in the same phase.