Workloads need to move to the cloud, but architecture and operating model are missing.
Possible approach
Translate application, operations and access requirements into cloud architecture.
Specialist role
Cloud architect
Your applications gain a clear path to maintainable cloud operations. Translate application, operations and access requirements into cloud architecture.
Understand the role
What does a Cloud architect do?
Translate application, operations and access requirements into cloud architecture.
The central objective is: Your applications gain a clear path to maintainable cloud operations.
Problem → approach
Typical situations where this role helps
Changes, outages and costs cannot reliably be assigned to a technical owner.
Cloud projects implement conflicting network and access rules.
Possible approach
Prepare acceptance and handover: Agreed architecture with an operating model, cost assumptions and migration steps.
An architecture decision requires trade-offs across cost, outages and migration.
Possible approach
Monitor operational metrics and costs.
Does this fit your situation?Five short answers turn an initial idea into a first brief.
Check the fit ↗Inside the work
From problem to a verifiable outcome
An illustrative workflow for a Cloud architect. Select a step to see what may be prepared and handed over.
Starting point
Changes, outages and costs cannot reliably be assigned to a technical owner.
- Define target architecture and access.
- Relevant systems: Microsoft Azure, Amazon Web Services, Terraform.
Delivery
Translate application, operations and access requirements into cloud architecture.
- Translate application, operations and access requirements into cloud architecture.
- Prepare acceptance and handover: Agreed architecture with an operating model, cost assumptions and migration steps.
Review
Review the work against a concrete situation
- Compare two architecture options for a concrete workload and disclose cost assumptions, failure boundaries, access and migration dependencies.
- Also review for the assignment: Workloads; Access model; Operational handover.
Handover
Agreed architecture with an operating model, cost assumptions and migration steps.
- Agreed architecture with an operating model, cost assumptions and migration steps.
- Documented platform with operational handover.
Typical projects
What an assignment could look like
Illustrative scenarios for orientation. Scope and outcomes are agreed for each assignment.
Translate application, operations and access requirements into cloud architecture.
- Starting point
- Workloads need to move to the cloud, but architecture and operating model are missing.
- Approach
- Translate application, operations and access requirements into cloud architecture.
- Possible outcome
- Agreed architecture with an operating model, cost assumptions and migration steps.
Prepare acceptance and handover: Agreed architecture with an operating model, cost assumptions and migration steps.
- Starting point
- Cloud projects implement conflicting network and access rules.
- Approach
- Prepare acceptance and handover: Agreed architecture with an operating model, cost assumptions and migration steps.
- Possible outcome
- Documented platform with operational handover.
Handover for Cloud architect
- Starting point
- An architecture decision requires trade-offs across cost, outages and migration.
- Approach
- Monitor operational metrics and costs.
- Possible outcome
- A documented working approach for Cloud architect.
Tangible deliverables
What may be delivered
Examples, not a blanket delivery promise. Choose the outputs your project actually needs.
- Agreed architecture with an operating model, cost assumptions and migration steps.
- Documented platform with operational handover.
- Review record for: Workloads.
- Documented decisions, dependencies and open issues.
- Handover materials and knowledge transfer for the internal team.
Specialist fit
How to recognise relevant experience
For a Cloud architect, a traceable working approach matters. With VB Analyst, your task becomes a search brief with verifiable essential criteria.
Make experience tangible
Compare two architecture options for a concrete workload and disclose cost assumptions, failure boundaries, access and migration dependencies.
- Connection to your assignment
- Translate application, operations and access requirements into cloud architecture
- Relevant working environment
- Microsoft Azure, Amazon Web Services, Terraform
Anonymised examples suffice for an initial assessment. References, qualifications and availability are clarified for the assignment; a tool list alone does not establish suitability.
Which seniority makes sense?
Senior experience is useful when multiple systems, long-term architecture decisions or operational risks intersect. The key is explaining trade-offs against your constraints.
Applied to: Translate application, operations and access requirements into cloud architecture.
Remote, hybrid or on-site?
Remote work is usually practical with approved access, data and contacts. On-site sessions can support kick-off or handover.
A point to resolve in the brief
Changes, outages and costs cannot reliably be assigned to a technical owner.
Career profile · concise
Responsibilities, entry routes and working environment
For reference and preparation of your search brief.
Fact sheet: Cloud architectTasks · qualifications · tools
What does a Cloud architect do?
Translate application, operations and access requirements into cloud architecture.
Tasks and responsibilities: Cloud architect
- Translate application, operations and access requirements into cloud architecture.
- Prepare acceptance and handover: Agreed architecture with an operating model, cost assumptions and migration steps.
How to recognise the outcome
Agreed architecture with an operating model, cost assumptions and migration steps.
Training and degree paths: Cloud architect
Computer science or business informatics; also vocational IT training with substantial systems, network and cloud experience.
These are possible professional routes, not a universal degree requirement. For this role we review experience with a comparable task, technical depth and the ability to document a handover. Required degrees and evidence are defined in the specific search brief.
Specific selection questions
- Workloads
- Access model
- Operational handover
Tools & technologies
Microsoft Azure ↗Organise cloud resources and services into an operating structure.Amazon Web Services ↗Build cloud infrastructure with suitable access and operating rules.Terraform ↗Describe infrastructure changes as reviewable code.
Possible working environment; the actual combination depends on the assignment.
Capability compass
Which combination moves your project forward?
Connect your task to relevant capabilities. A tool selection narrows the working environment; the results explain each professional connection.
Starting pointCloud architectSearch the full catalogue ↗
03Reasoned role selectionTask · capabilities · outcome
The professional connection becomes clear through tasks and possible outputs.
Cloud architect
Translate application, operations and access requirements into cloud architecture.
Your possible outcome
Agreed architecture with an operating model, cost assumptions and migration steps.
DevOps engineer
Connect development and operations through traceable build, test and deployment workflows.
Your possible outcome
Automated deployment with checks, logs and a recovery path.
Cloud engineer
Implement cloud resources and changes within an agreed operating model.
Your possible outcome
Documented infrastructure with access, checks and handover.
Capability profiles for orientation. An individual’s suitability is assessed against the search brief.
Refine the selection ↗Define the boundaries
When another role may fit better
This may not be the right role if your main priority lies elsewhere. These profiles help clarify the difference.
If your priority is: Implement cloud resources and changes within an agreed operating model.Cloud engineer ↗If your priority is: Connect business goals, applications and technology decisions in a shared target architecture.Enterprise architect ↗If your priority is: Connect protection goals, system access and technical controls in an actionable security design.Security architect ↗
Roles compared directly
This overview describes typical areas of responsibility. Actual scope may vary between organisations.
| Criterion | Cloud architect | Cloud engineer | Enterprise architect | Security architect |
|---|---|---|---|---|
| Core task | Translate application, operations and access requirements into cloud architecture. | Implement cloud resources and changes within an agreed operating model. | Connect business goals, applications and technology decisions in a shared target architecture. | Connect protection goals, system access and technical controls in an actionable security design. |
| Possible outcome | Agreed architecture with an operating model, cost assumptions and migration steps. | Documented infrastructure with access, checks and handover. | Architecture overview with principles, dependencies and prioritised changes. | Security design with assumptions, interfaces and documented residual risks. |
| Working environment | Microsoft Azure, Amazon Web Services, Terraform | Microsoft Azure, Terraform | UML, draw.io | draw.io, Microsoft Entra ID |
Unsure which role fits?Start with your goal and your team’s tasks.
Start the role finder ↗Divide the work sensibly
Which expertise complements this role?
Complementary roles address adjacent tasks. They are not automatic substitutes for a Cloud architect.
Cloud engineer
Implement cloud resources and changes within an agreed operating model.
Agree the interface
Discuss this combination ↗Documented infrastructure with access, checks and handover.
FinOps consultant
Assess cost structures, allocation rules and optimisation options with technical and business teams.
Agree the interface
Discuss this combination ↗Cost overview with assumptions, ownership and prioritised actions for review.
Cloud security engineer
Review and improve identities, configuration and logging against agreed protection needs.
Agree the interface
Discuss this combination ↗Documented control state with findings, prioritised actions and technical checks.
Which work can be scoped as a package?
A managed service requires defined inputs, scope and approval paths. These services provide a starting point for that definition.
Interactive fit check
Does a Cloud architect fit your project?
Five questions, a reasoned assessment and a brief for your enquiry. You can change every answer.
Your assignment with VB Analyst
Choose expertise. Define the engagement.
A capacity gap does not always require a permanent role. Choose a model by responsibility, duration and desired outcome.
Useful information for your enquiry
Cloud architect
Which workloads, mandatory constraints and existing contracts must the architecture consider?
Possible work objective
Agreed architecture with an operating model, cost assumptions and migration steps.
- Task, existing systems and scope
- Essential criteria, internal contact and approval
- Preferred start, duration, capacity and budget range
You can leave undecided details open. Non-confidential information is enough for initial contact.
Selected model: Project support
Discuss these requirements ↗View this model and its responsibilities ↗What happens next
From enquiry to a well-prepared start
- Define the requirement
We clarify the task, priority and outstanding requirements with you.
- Assess specialist fit
Relevant experience is assessed against the assignment. Open questions and working parameters remain visible.
- Agree selection and scope
You decide through specialist discussions. Capacity, terms and responsibilities are agreed.
- Prepare onboarding
Access, the first milestone, contacts and handover are established.
How soon can work start?
Timing depends on suitable availability, selection, agreement and access. For urgent needs, separate essential initial work from later tasks. A binding start date is confirmed for the specific assignment.
A useful starting point
Anything still unclear?
Short answers for your next step. We can work through your specific situation together.
Discuss my question ↗What does a Cloud architect actually do?
Translate application, operations and access requirements into cloud architecture. One possible outcome: Agreed architecture with an operating model, cost assumptions and migration steps.
How can I assess professional fit?
Compare two architecture options for a concrete workload and disclose cost assumptions, failure boundaries, access and migration dependencies.
Which tools does the specialist need?
Possible working environments include Microsoft Azure, Amazon Web Services, Terraform. The required combination depends on your assignment. Not every listed tool is a mandatory requirement.
Are the specialists available now?
The profiles describe capabilities and typical assignments. Actual people, availability, terms and engagement are assessed for your specific need.