12 Month Cloud Roadmap: The Sustainable Full-Time Plan

Who the 12-month plan is for

This plan is for people who are employed full-time and intend to stay that way while studying. It is for parents, caregivers, and anyone whose life has genuine demands that cannot be paused for a career transition. It is also for people who tried a shorter plan and found themselves burning out — those who hit month 3 of an intensive schedule and realised they were producing poor-quality work and dreading every study session.

Eight to twelve hours per week might feel modest compared to the 6 month roadmap’s fifteen to twenty hours, or the 3 month plan’s thirty-five plus hours. But accumulated over a full year, 10 hours per week equals over 500 hours of study and practice. That is a substantial investment in your skills — more than many formal part-time courses deliver. The question is never whether you are studying enough hours in a single week. The question is whether you can sustain the effort across a full year.

One thing this plan does not do: compress everything into a shorter timeline. If you follow the 12-month plan but then suddenly have more time available, you can accelerate. But trying to follow the 12-month plan at 5 hours per week means it becomes an 18 or 24-month plan. Be honest about the hours you can actually commit.

Why consistent slow beats intense and short

There is a strong argument that 12 months of consistent 10-hour weeks produces a better cloud engineer than 3 months of 35-hour weeks, even though the total hours are similar. The reason is how memory and skill consolidation actually work.

When you learn something and then come back to it a week later, your brain has processed and partially consolidated it. You review it, apply it differently, and the knowledge becomes more durable. When you cram the same material in a single long session, you perform well on a test the next day, but retention drops off sharply within a week. This is why someone who studied Terraform over three months and built four different projects with it will outperform someone who did an intensive two-week Terraform bootcamp, even if the bootcamp person passed the same exam.

There is also the practical application effect. If you are studying over 12 months, you have more opportunities to encounter real-world situations — news stories, incidents at your current job, conversations with colleagues — that connect to what you are learning. You have time to experiment, break things, fix them, and understand why they broke. That kind of tacit knowledge is what makes the difference between someone who can recite cloud architecture patterns and someone who can troubleshoot a broken deployment at 11pm.

The 12-month learner typically arrives at their first cloud job with broader, more durable knowledge. They often ramp up faster and feel less overwhelmed in the first 90 days.

Q1 (Months 1–3): Foundations that actually stick

Weekly hours: 8–12. Goal: Build genuine fluency with Linux and networking fundamentals, understand the core services of your chosen cloud platform, pass a foundational certification, and develop good study and Git habits.

Month 1 — Linux and the command line. Start here, not in the cloud console. The time you invest in Linux in month 1 pays dividends across every subsequent quarter. Focus on: navigating the file system, file permissions and ownership, SSH key authentication, basic shell scripting (loops, conditionals, reading variables), package management with apt or yum, and reading system logs. Use a Linux VM running locally or a free-tier cloud instance. Aim to spend at least half of your study sessions actually at a terminal rather than reading or watching.

Month 2 — Networking fundamentals and cloud orientation. Cover the networking concepts that underpin cloud infrastructure: IP addressing, subnets and CIDR notation, DNS resolution, routing, network address translation, and how HTTP/HTTPS work at a basic level. Then begin your cloud platform orientation: what regions and availability zones are, how IAM works, the shared responsibility model, and the main service categories. Set up a free-tier account, configure a billing alert immediately, and explore the console without deploying anything yet.

Month 3 — Core cloud services and foundational certification. Learn the foundational services in depth: compute (instances, instance types, and when to use what), object storage, managed databases at a high level, and networking within the platform (VPC, subnets, security groups, internet gateways). Prepare for and sit either AWS Cloud Practitioner or GCP Cloud Digital Leader. Alongside certification prep, manually deploy a static website to object storage and configure it with a custom domain. Commit your notes and configuration files to a GitHub repository — start the version control habit early.

Q2 (Months 4–6): Core cloud skills and your first real project

Weekly hours: 8–12. Goal: Learn Terraform and Docker to a working level, build one complete portfolio project, and begin preparing for an associate-level certification.

Month 4 — Terraform fundamentals. Infrastructure as code is a core cloud skill, not an optional extra. Work through the official HashiCorp tutorials methodically. The foundational concepts to master: writing resource blocks, understanding state and why it matters, using variables and output blocks, and organising code into modules. Do not just follow the tutorials — modify them. Delete a resource and recreate it. Change an attribute and observe what Terraform does. Break the state file on purpose and fix it. Hands-on problem-solving at this stage is more valuable than completing more tutorials.

Month 5 — Docker and containerisation. Learn Docker by building and running containers, not just reading about them. Write a Dockerfile for a simple application from scratch. Build the image, run it locally, push it to Docker Hub or a cloud container registry. Understand image layering and why it matters for image size. Learn basic Docker Compose for running multi-container setups locally. Deploy a containerised application to a managed container service on your cloud platform.

Month 6 — First complete portfolio project. Use this month to build one cohesive project that combines what you have learned. A good option: a containerised web application with its infrastructure fully defined in Terraform, deployed to your cloud platform, with all code in a well-structured GitHub repository. The application itself does not need to be impressive — a simple to-do list or blog is fine. What matters is that the infrastructure is real, reproducible, and documented. Write a thorough README. This is the project you will describe in your first interviews.

Begin associate-level certification study in parallel during month 6. AWS Solutions Architect Associate or GCP Associate Cloud Engineer are both appropriate. Start with the official exam guide to understand the scope — you will not finish it this quarter, but starting early means you have time to consolidate.

Q3 (Months 7–9): Containers in depth, CI/CD, and the associate cert

Weekly hours: 8–12. Goal: Pass an associate-level certification, understand Kubernetes well enough to deploy to a managed cluster, and build a CI/CD pipeline.

Month 7 — Kubernetes fundamentals. Kubernetes is the standard for container orchestration in production environments, and it appears in a large proportion of cloud engineer job descriptions. You do not need to administer a Kubernetes cluster — you need to understand how applications run on one. Core concepts: pods and why they exist, deployments and how rolling updates work, services and how they expose applications, namespaces, and basic resource limits. Use a managed Kubernetes service — Amazon EKS, GKE, or AKS — and deploy your containerised application from Q2 to it. Use kubectl exclusively; avoid graphical dashboards for now.

Month 8 — CI/CD pipelines and cloud networking depth. Build a CI/CD pipeline using GitHub Actions that runs on push, builds your Docker image, and deploys it to your cluster or container service. Then deepen your cloud networking knowledge: VPC design, public and private subnets, NAT gateways, load balancers (application versus network), and VPC peering. These concepts appear heavily in associate-level exams and are regularly discussed in cloud engineer interviews. Build a multi-tier networking architecture in Terraform — a VPC with public and private subnets, a load balancer in the public tier, and application instances in the private tier.

Month 9 — Associate certification. Concentrate the majority of this month’s study hours on passing your associate cert. Use a structured course, the official documentation, and a large bank of practice exams — aim to complete at least 200 to 300 practice questions before sitting. Practice exams for associate-level certs require you to reason through multi-service scenarios, not just recall facts. When you get a question wrong, study why the correct answer is correct and why your answer was not. Sit the exam by the end of month 9.

Q4 (Months 10–12): Specialist skills, portfolio polish, and active job search

Weekly hours: 8–12. Goal: Add one specialist area to your profile, complete your portfolio, and spend the final weeks actively applying and preparing for interviews.

Choosing a specialist direction. By month 10, you should have a sense of which cloud engineering direction interests you most. Three common paths:

• DevOps / platform engineering — deepen Kubernetes (Helm, ArgoCD), add monitoring with Prometheus and Grafana, explore GitOps workflows
• Cloud security — IAM policy design in depth, secrets management (AWS Secrets Manager or HashiCorp Vault), compliance frameworks, security groups and NACLs
• Data and ML infrastructure — managed data services (BigQuery, Redshift, Databricks on cloud), data pipeline basics, cloud storage patterns for large datasets

You do not need to become an expert in your chosen direction. Two months of focused study produces enough knowledge to speak intelligently about it in an interview and to have one project demonstrating it.

Month 11 — Portfolio review and second project. Review all your GitHub repositories with fresh eyes. The test: could a hiring manager who knows cloud look at each repository, read the README, and understand what you built, why, and how? Tighten any READMEs that are thin. Add architecture diagrams — even rough ones made in draw.io or Excalidraw — to your main project repositories. Build a second substantial portfolio project in your specialist direction. Update your CV and LinkedIn to reflect your two certifications, your projects, and your tools.

Month 12 — Active job search. By month 12 you have over 400 hours of study and practice behind you, two certifications, and at least two solid portfolio projects. This is a strong profile for junior cloud engineer and cloud support engineer roles. Start applying actively — aim for five to ten applications per week. Prepare for technical interviews by practising explaining your portfolio projects out loud. Review the cloud engineer skills guide to ensure your CV accurately reflects the skills interviewers expect to see.

Expect the job search to take two to four months of active applications. Use the realistic cloud career timeline to calibrate your expectations for this phase — the search process has its own rhythm and timeline that is separate from the learning phase.

Staying consistent across 12 months

Twelve months is a long time to sustain deliberate effort in one direction. Some things that help:

Track your hours. A simple spreadsheet or even a paper log of study hours per week serves two purposes: it shows you patterns (when do you study well, when do you not), and it gives you evidence of your consistency that you can point to in interviews. “I studied for 10 hours every week for a year” is a statement that signals commitment to a potential employer.

Plan for gaps. Life will interrupt your schedule. Holidays, illness, work projects, family crises — these are predictable in the aggregate even if not in the specific. Build the expectation of occasional missed weeks into your plan. A two-week gap in month 7 does not derail a 12-month plan. It becomes a problem only if you let the gap compound by not restarting.

Revisit earlier material. At month 6 and month 9, spend a session going back to something you learned early on — your Terraform code from month 4, your first networking notes from month 2 — and see how much more you understand now. This is motivating in a concrete way: it shows you the progress that is otherwise invisible when you are in the middle of learning something difficult.