Skip to main content
A cloud architect draws a multi-region design on a whiteboard for colleagues
Pathway

Cloud Engineer → Cloud Architect

A practical engineering route combining cloud deployment with access, reliability and cost decisions.

Explore the work, check your starting point and try one scoped task before committing to a course or exam.

Try this pathway in practice

The route

From Junior Cloud Engineer / Cloud Support to Cloud Architect

  1. Starting roleJunior Cloud Engineer / Cloud SupportRead the broader role guide
  2. Target roleCloud ArchitectRead the broader role guide

A general route, not a personal plan. Linked guides describe the broader role family; a junior or support starting point may have a narrower remit. Compare the responsibilities with the actual vacancy.

Phased progression

Build foundations, demonstrate the work, then choose how to deepen or broaden your responsibility.

Progress through demonstrated capability and agreed responsibility. These stages are not a fixed timetable or a salary ladder.

  1. Build the foundations

    Foundations

    Practical focus

    Build literacy and lab habits. These are study options, not mandatory exams; choose the platform relevant to your target work.

    Something to demonstrate

    A short account of what you can already do and the next gap to investigate.

    In focus AWS Cloud Practitioner · AZ-900

  2. Demonstrate readiness

    First role in this route

    Practical focus

    Explore Junior Cloud Engineer / Cloud Support responsibilities. Check the supervision and prior experience expected; demonstrate the relevant work before increasing your scope.

    Something to demonstrate

    An architecture sketch, access table and recovery checklist; optionally add a small lab build and test record.

    In focus Junior Cloud Engineer / Cloud Support

  3. Demonstrate reliable practice

    Specialisation

    Practical focus

    Take on a scoped responsibility, test your decisions and collect feedback. Add a credential only where it supports that work.

    Something to demonstrate

    A test record and feedback showing how you improved a piece of work.

    In focus AWS Solutions Architect Associate · AZ-104

  4. Broaden responsibility

    Deepen, lead or move sideways

    Practical focus

    Cloud Architect or Principal Engineer. System-of-systems judgement, not more YAML.

    Something to demonstrate

    Examples of broader ownership, with the scope and responsibility agreed.

    In focus AWS Solutions Architect Pro

The work itself

What you would spend time doing

Deploy services, manage access, investigate failures and control operating costs. Architecture adds decisions across services and teams, rather than simply more products.

Your starting point

What to bring to this route

Be able to explain networking, identities and a simple service before adding managed services. A supervised operations route can provide useful experience alongside labs.

Ask a course provider or employerWho owns on-call, cloud spending and recovery testing, and how are production changes reviewed?

The verdict

You have systems or networking experience you want to apply to cloud workloads. You enjoy IAM puzzles and reading other people's Terraform without crying.

Deploying a service is only part of the remit. Determine who owns incidents, spending, infrastructure changes and recovery, and how much of that ownership is supervised.

Certification sequence

Study options, not a checklist. Choose for the work you need to demonstrate, then check the provider’s current requirements and renewal terms.

Practical projects

Produce something you can explain, test and improve with feedback.

A scoped starting exercise

Try the work before choosing the route

Design a small service with a public endpoint and private data store. Identify who can access each part, one failure scenario and a spending boundary before building anything.

What to keepAn architecture sketch, access table and recovery checklist; optionally add a small lab build and test record.

Free text worksheet · no account needed. Add your checks, results and feedback as you work.

Review the evidence

  1. Can you explain what remains available when one component fails?
  2. Have you accounted for credentials, backups, costs and removal of any lab resources?

Label planned, simulated and completed work accurately. A practice exercise helps you test your interest and reasoning; it does not establish production experience or guarantee an interview.

Larger portfolio ideas for later

Choose one once you have the foundations and permissions it needs. Scope it to a task you can test and explain.

  • Multi-account AWS landing zone with Terraform
  • Three-tier app deployed via IaC + CI/CD
  • Cost-optimisation audit on a real account

Use synthetic or approved information. Keep employer, customer and account details out of public examples.

DevOps EngineerPlatform EngineerSolutions Architect
  • ·DevOps-first via developer background
  • ·Platform engineering via SRE

Realistic expectations

Check these assumptions against the course, vacancy or team you are considering.

Misconception

That a title or credential establishes readiness by itself. Compare deployment, access, networking and recovery responsibilities with your evidence.

Readiness check

Compare deployment, access, networking and recovery responsibilities with your evidence. A supervised junior role and an independent engineering role require different levels of ownership.

Editorial route and career guidance. No separate external evidence review is recorded for this assessment.

Editorial evidence review: pending · UK market. Vendor facts and prices elsewhere on this page have their own sources and check dates.

Where this fits

Explore the work behind this route.