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.

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 practiceThe route
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.
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.
Build the foundations
Build literacy and lab habits. These are study options, not mandatory exams; choose the platform relevant to your target work.
A short account of what you can already do and the next gap to investigate.
In focus AWS Cloud Practitioner · AZ-900
Demonstrate readiness
Explore Junior Cloud Engineer / Cloud Support responsibilities. Check the supervision and prior experience expected; demonstrate the relevant work before increasing your scope.
An architecture sketch, access table and recovery checklist; optionally add a small lab build and test record.
In focus Junior Cloud Engineer / Cloud Support
Demonstrate reliable practice
Take on a scoped responsibility, test your decisions and collect feedback. Add a credential only where it supports that work.
A test record and feedback showing how you improved a piece of work.
In focus AWS Solutions Architect Associate · AZ-104
Broaden responsibility
Cloud Architect or Principal Engineer. System-of-systems judgement, not more YAML.
Examples of broader ownership, with the scope and responsibility agreed.
In focus AWS Solutions Architect Pro
The work itself
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
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?
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.
Study options, not a checklist. Choose for the work you need to demonstrate, then check the provider’s current requirements and renewal terms.
Explore these first
Compare the subject with the work you want to do. Check eligibility before committing.
For a particular platform or gap
Choose one when its syllabus addresses a gap you need to practise.
As your responsibility grows
Revisit when your scope changes. Experience and renewal requirements still apply.
Produce something you can explain, test and improve with feedback.
A scoped starting exercise
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.
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.
Check these assumptions against the course, vacancy or team you are considering.
That a title or credential establishes readiness by itself. Compare deployment, access, networking and recovery responsibilities with your evidence.
Compare deployment, access, networking and recovery responsibilities with your evidence. A supervised junior role and an independent engineering role require different levels of ownership.
What this is based on
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