Skip to content
A fox in open snow under a wide sky, representing cloud development

Roadmaps

Cloud Developer Roadmap

A cloud development roadmap for 2026 for developers who want to design, deploy and operate cloud-native applications - from Linux and networking to containers, serverless, Terraform, security and cost control.

  • 9 stages
  • 10-15 months part time
  • Provider agnostic

Realistic timeline

10-15 months at 10-15 hours per week

Stages

9 in order

Starting point

Basic programming helps

A cloud developer writes applications designed to run on cloud platforms such as AWS, Microsoft Azure or Google Cloud, and takes responsibility for how they are deployed, secured, scaled and paid for. It sits between backend development and DevOps: you still write code, but you also define the infrastructure it runs on.

This cloud developer roadmap assumes you can already program a little. If not, work through the early stages of the backend developer roadmap first, because cloud skills are most valuable when you have an application worth deploying.

Overview

The cloud computing roadmap at a glance

Nine stages from Linux basics to production-ready cloud applications.

Select a stage to see what it covers. Filter by level to focus.

1. Programming and Linux essentials

6-8 weeks

Write simple services and work comfortably on a Linux server.

  • Linux shell, permissions and processes
  • SSH and key management
  • Bash scripting basics
  • One backend language
  • A small REST API
  • Git and GitHub

Done when: A small API running on a Linux virtual machine that you set up yourself.

Full stage details

Learning order

Cloud developer learning path, stage by stage

Learn one provider deeply. The concepts carry over to the others.

  1. Foundation · Beginner

    Programming and Linux essentials

    6-8 weeks

    Write simple services and work comfortably on a Linux server.

    Cloud workloads run mostly on Linux. Learn the shell, file permissions, processes, package management and SSH. Pair this with one programming language commonly used in the cloud - Python, JavaScript/TypeScript, Go, Java or C# - and build a small HTTP API you can deploy in later stages.

    Skills

    • Linux shell, permissions and processes
    • SSH and key management
    • Bash scripting basics
    • One backend language
    • A small REST API
    • Git and GitHub

    Milestone

    A small API running on a Linux virtual machine that you set up yourself.

    Project ideas

    • A URL shortener API deployed to a VM
  2. Foundation · Beginner

    Networking and cloud concepts

    4-6 weeks

    Understand how traffic reaches your application and what the cloud actually provides.

    Many cloud problems are networking problems in disguise. Learn IP addressing, subnets, DNS, HTTP and HTTPS, TLS certificates, load balancers and firewalls. Then learn the cloud models - IaaS, PaaS, SaaS and serverless - along with regions, availability zones and the shared responsibility model for security.

    Skills

    • IP addresses, CIDR and subnets
    • DNS, HTTP, HTTPS and TLS
    • Load balancers, proxies and CDNs
    • Firewalls and security groups
    • IaaS, PaaS, SaaS and serverless
    • Regions, availability zones and shared responsibility

    Milestone

    Serve your API over HTTPS on a custom domain, and explain every hop a request makes.

    Project ideas

    • Put your API behind a reverse proxy with TLS
  3. Core skills · Beginner

    Core services of one cloud provider

    8-10 weeks

    Use the core compute, storage, database and identity services of one provider.

    Choose AWS, Azure or Google Cloud - ideally the one most common in job adverts where you live - and learn its fundamentals: identity and access management, virtual machines, object storage, managed databases, virtual networks and monitoring. Set up billing alerts on day one; unexpected bills are a rite of passage you can avoid.

    Skills

    • Identity and access management and least privilege
    • Virtual machines and autoscaling
    • Object storage and static hosting
    • Managed relational and NoSQL databases
    • Virtual networks and private subnets
    • Billing alerts and budgets

    Milestone

    Deploy your API with a managed database in a private subnet, using least-privilege permissions.

    Project ideas

    • A static site on object storage with a CDN
    • An API with a managed database
  4. Tools · Intermediate

    Containers and Docker

    4-6 weeks

    Package applications so they run the same everywhere.

    Containers are the standard unit of cloud deployment. Learn to write efficient Dockerfiles, use multi-stage builds, manage images in a registry and run multi-container setups locally with Docker Compose. Then deploy containers to a managed container service on your chosen provider.

    Skills

    • Dockerfiles and multi-stage builds
    • Images, layers and registries
    • Docker Compose for local environments
    • Environment configuration and secrets
    • Managed container services
    • Image scanning basics

    Milestone

    Your API and database running with Docker Compose locally and as containers in the cloud.

    Project ideas

    • Containerise a multi-service app
  5. Frameworks · Intermediate

    Serverless and cloud-native design

    6-8 weeks

    Build event-driven applications that scale automatically.

    Serverless functions, managed queues, event buses and NoSQL databases let you build systems that scale to zero and handle spikes without servers to manage. Learn when serverless fits and when it does not - cold starts, execution limits and cost at high volume all matter. Study cloud-native design principles such as statelessness, idempotency and loose coupling.

    Skills

    • Serverless functions and triggers
    • API gateways
    • Queues, pub/sub and event-driven design
    • NoSQL data modelling
    • Idempotency and retries
    • Twelve-factor app principles

    Milestone

    An event-driven workflow where an upload triggers processing and a notification, with retries handled.

    Project ideas

    • An image processing pipeline triggered by uploads
  6. Frameworks · Intermediate

    Infrastructure as code and CI/CD

    6-8 weeks

    Create and change infrastructure through reviewed code and automated pipelines.

    Clicking through a console does not scale or repeat. Learn Terraform (or OpenTofu, its open-source fork) or your provider's native tool to define infrastructure as code. Build CI/CD pipelines that test, build images, scan them and deploy automatically, with separate environments for development and production.

    Skills

    • Terraform or OpenTofu basics
    • State management and modules
    • Provider-native IaC tools
    • CI/CD with GitHub Actions or similar
    • Environment separation
    • Secrets management services

    Milestone

    Tear down and recreate your whole environment from code in one command.

    Project ideas

    • Full infrastructure for your API defined in Terraform with a deploy pipeline
  7. Advanced topics · Advanced

    Kubernetes and orchestration

    6-8 weeks

    Deploy and operate containerised applications on Kubernetes.

    Kubernetes is widely used for running many containers reliably. Learn pods, deployments, services, ingress, config maps, secrets and autoscaling, and use a managed Kubernetes service rather than building clusters by hand. Be honest about whether a project needs it - many teams run happily on simpler managed container platforms.

    Skills

    • Pods, deployments and services
    • Ingress and service exposure
    • ConfigMaps, secrets and volumes
    • Health checks and autoscaling
    • Helm charts
    • Managed Kubernetes services

    Milestone

    Deploy a multi-service application to managed Kubernetes with health checks and autoscaling.

    Project ideas

    • Migrate your containerised app to a managed Kubernetes cluster
  8. Advanced topics · Advanced

    Observability, security and cost

    6-8 weeks

    Run cloud systems that are visible, secure and affordable.

    Production readiness means knowing what is happening and keeping it safe and within budget. Learn logs, metrics, traces and alerting; security practices such as encryption, network isolation, secret rotation and vulnerability scanning; and FinOps basics: tagging, rightsizing, reserved capacity and spotting waste.

    Skills

    • Logs, metrics, traces and dashboards
    • Alerting and on-call basics
    • Encryption at rest and in transit
    • Security scanning and posture tools
    • Cost tagging, budgets and rightsizing
    • Backups and disaster recovery

    Milestone

    Dashboards, alerts, a backup plan and a monthly cost breakdown for your project.

    Project ideas

    • A cost and security review of your own cloud project
  9. Job ready · Advanced

    Certification, portfolio and interviews

    6-8 weeks

    Prove your skills through projects and, optionally, a recognised certification.

    Cloud is one of the few areas where certifications are commonly requested. An associate-level developer or architect certification from your chosen provider is a sensible target. Pair it with real projects defined in code, and practise explaining architecture diagrams and design trade-offs.

    Skills

    • Provider certification preparation
    • Architecture diagrams
    • Well-architected framework principles
    • Scenario-based design questions
    • Troubleshooting walkthroughs

    Milestone

    An associate-level certification or equivalent project evidence, and a documented reference architecture.

    Project ideas

    • A write-up of your architecture with diagrams and cost estimates

Progression

Cloud development skills by level

What each level looks like in practice, so you know where you stand.

Beginner

Months 0-4

You understand Linux, networking and the core services of one provider.

Focus on

  • Linux and SSH
  • DNS, HTTP and TLS
  • IAM and core services
  • Billing alerts

You can: Deploy a simple app securely to the cloud.

Intermediate

Months 4-10

You build containerised and serverless apps with infrastructure as code.

Focus on

  • Docker
  • Serverless and events
  • Terraform
  • CI/CD pipelines

You can: Recreate your environment from code.

Advanced

Months 10-15+

You operate cloud systems with orchestration, observability, security and cost control.

Focus on

  • Kubernetes
  • Monitoring and alerting
  • Security hardening
  • FinOps

You can: Run a production-ready cloud application.

Technologies

Cloud technologies roadmap

Dark chips are worth learning early. Light chips can wait until a project needs them.

Cloud providers

Learn one deeply; the others will feel familiar.

Start with

  • AWS or Azure or Google Cloud

Add later or when needed

  • A second provider
  • Cloudflare
  • Vercel or similar PaaS

Foundations

Used every day.

Start with

  • Linux
  • Bash
  • Git
  • Networking basics

Add later or when needed

  • Advanced networking
  • Service mesh concepts

Containers

The standard deployment unit.

Start with

  • Docker
  • Docker Compose

Add later or when needed

  • Kubernetes
  • Helm
  • Container security scanning

Infrastructure as code

Repeatable, reviewable infrastructure.

Start with

  • Terraform or OpenTofu

Add later or when needed

  • Provider-native IaC
  • Pulumi
  • Ansible

CI/CD

Automated testing and delivery.

Start with

  • GitHub Actions

Add later or when needed

  • GitLab CI
  • Argo CD
  • Provider pipelines

Observability

Seeing inside your systems.

Start with

  • Provider monitoring tools
  • Structured logs

Add later or when needed

  • OpenTelemetry
  • Prometheus
  • Grafana

Priorities

What to learn first, and what can wait

Focus beats coverage. These lists keep the first months pointed at what pays off.

Learn these first

  1. 1Linux command line and SSH
  2. 2DNS, HTTP, TLS and basic networking
  3. 3Identity and access management with least privilege
  4. 4Core compute, storage and database services of one provider
  5. 5Billing alerts - before you create any resources

Safe to skip at the start

  • Multi-cloud architectureRarely needed early. Depth in one provider is more employable.
  • Kubernetes from day oneLearn containers and managed services first. Kubernetes makes more sense after.
  • Service meshesAn advanced tool for large microservice estates.
  • Every managed serviceProviders offer hundreds. Learn the core dozen well.
  • Professional-level certificationsAim for associate level first, with hands-on experience behind it.

Projects

Cloud developer projects

Ordered by difficulty. Two or three finished ones beat ten half-built ones.

  • Beginner

    Static site with CDN

    Host a site on object storage with HTTPS, a custom domain and caching.

    • Storage
    • DNS
    • CDN
  • Beginner

    API on a virtual machine

    Deploy an API to a VM with a firewall, TLS and a managed database.

    • Compute
    • Networking
  • Intermediate

    Serverless file processor

    Uploads trigger functions that resize images or parse files and send notifications.

    • Serverless
    • Events
  • Intermediate

    Infrastructure as code project

    A multi-environment setup defined in Terraform and deployed by a pipeline.

    • Terraform
    • CI/CD
  • Advanced

    Kubernetes microservices

    Several services on managed Kubernetes with ingress, autoscaling and Helm charts.

    • Kubernetes
    • Helm
  • Advanced

    Production readiness review

    Add monitoring, alerts, backups, security scanning and a cost report to an existing project.

    • Observability
    • Security
    • FinOps

Avoid these

Common mistakes

Patterns that slow most learners down, and what to do instead.

  • No billing alerts

    Forgotten resources can run up surprising bills. Set budgets and alerts before creating anything.

  • Using root or admin credentials

    Everyday work should use least-privilege roles. Leaked admin keys are a serious risk.

  • Console-only infrastructure

    Manual setups cannot be reviewed or reproduced. Move to infrastructure as code early.

  • Certifications without projects

    A certificate shows knowledge; a working, documented project shows ability. Employers want both.

  • Skipping networking

    Many "the app is down" problems are DNS, routing or firewall issues. Learn the fundamentals.

  • Overengineering

    Kubernetes and microservices are not required for every app. Choose the simplest option that meets the need.

Career

Cloud developer career path

Portfolio, interviews and the checklist to review before you apply.

Cloud skills are valued across development, DevOps and platform roles. Developers who can also deploy and operate their code are especially useful in small and medium teams. Strong application skills from the backend developer roadmap make cloud work more meaningful, and AI teams increasingly need cloud expertise - see the AI engineer roadmap.

Typical job titles

  • Cloud Developer
  • Cloud Engineer
  • DevOps Engineer
  • Platform Engineer
  • Site Reliability Engineer
  • Solutions Architect

Job-ready checklist

  • You can deploy an app securely on one major provider
  • You define infrastructure as code and deploy through pipelines
  • You understand networking, IAM and encryption basics
  • You can containerise and orchestrate applications
  • You monitor systems and control costs

Portfolio guidance

  • Infrastructure code in public repositories
  • Architecture diagrams for each project
  • Cost estimates and security notes in READMEs
  • Evidence of automated deployment
  • A certification badge alongside real projects

Interview preparation

  • Designing a scalable, highly available web application
  • Networking and DNS troubleshooting scenarios
  • IAM and security questions
  • Containers, Kubernetes and CI/CD concepts
  • Cost optimisation trade-offs

Mentorship

Mentorship Details Coming Soon

If you want to connect, please WhatsApp: 3265503569

One-to-one mentorship for the roadmaps on Fox Is Happy is being set up. Sessions will cover code review, project feedback, interview preparation and a learning plan matched to where you actually are - not where a generic curriculum assumes you are.

Pricing will be reasonable and listed clearly before you book - pay per session, with student-friendly rates planned. No subscriptions and no bundles you do not need.

Register interest

3265503569

WhatsApp only. Message on WhatsApp to register interest and be told first when places open.

Mention Cloud Developer Roadmap in your message so the reply matches what you are working on.

What cloud development means today

Cloud development is less about a particular provider and more about a way of building software: automated, observable, scalable and paid for by the hour.

Cloud developer, cloud engineer or DevOps?

The titles overlap. A cloud developer focuses on building applications that use cloud services well. A cloud engineer focuses more on designing and maintaining the infrastructure. DevOps and platform engineers build the pipelines and internal platforms that let other developers ship safely. The skills in this roadmap are shared by all three, with the emphasis on the developer side.

AWS, Azure or Google Cloud?

All three are major providers with similar core services under different names. AWS has the largest market share, Azure is common in organisations that use Microsoft products, and Google Cloud is strong in data and AI services. Check job adverts in your region and pick one.

Equivalent core services across providers
ConceptAWSAzureGoogle Cloud
Virtual machinesEC2Virtual MachinesCompute Engine
Object storageS3Blob StorageCloud Storage
Serverless functionsLambdaAzure FunctionsCloud Run functions
Managed KubernetesEKSAKSGKE
Identity and accessIAMMicrosoft Entra ID and RBACCloud IAM

How long does it take to become a cloud developer?

For someone with basic programming skills, ten to fifteen months of part-time study is realistic. Experienced backend developers can often become productive in the cloud within three to six months. Hands-on practice matters more than reading - use free tiers and credits, and tear resources down when you finish.

Are cloud certifications worth it?

For cloud roles, often yes - they are frequently mentioned in job adverts and give structure to your learning. They work best combined with projects that prove you can apply the knowledge. Start with a foundational or associate-level exam, and check the provider's website for the current exam names, since they change periodically.

Where to go next

If you want to build complete products on your cloud setup, the full stack developer roadmap adds the frontend. For hosting and scaling AI systems, continue with the roadmap for AI engineers.

Frequently asked questions

What is a cloud developer roadmap?

A structured plan for learning to build and run applications on cloud platforms. This one covers Linux, networking, one major provider, containers, serverless, infrastructure as code, Kubernetes, observability, security and cost management.

Do I need programming skills to become a cloud developer?

Yes. Cloud developers write application code and infrastructure code. Python, JavaScript/TypeScript, Go, Java or C# are all common choices.

Which cloud provider should beginners learn first?

The one most requested in job adverts where you want to work. AWS is the most widely used overall, while Azure and Google Cloud are strong in particular industries. The core concepts transfer.

Is Kubernetes required for cloud development?

Not always. Many applications run well on serverless or managed container services. Kubernetes knowledge is valuable for larger systems and many job adverts, so learn it after the fundamentals.

Can I learn cloud development for free?

Largely, yes. Providers offer free tiers, credits and free training material. Set billing alerts, because some services charge beyond free limits.

What cloud projects should I build?

A static site with a CDN, a serverless event pipeline, and an application whose infrastructure is fully defined in Terraform and deployed by a CI/CD pipeline.

Keep going

Related resources

Hand-picked pages that pair well with this one.

Roadmaps

Backend Developer Roadmap

From your first HTTP endpoint to services that handle data, auth, failure and load without falling over.

Open

Roadmaps

AI Engineer Roadmap

Engineer AI systems that hold up in production: ML depth, LLM internals, RAG and agents, evaluation, fine-tuning, serving and monitoring.

Open