Career Overlap Transition record
RecordMove

Cloud architect to cloud DevOps engineer

A cloud architect already meets 47% of what the cloud DevOps engineer role asks for. The move turns on 12 required skills not yet in the profile.

Fig. 1 · Skill transfer ESCO v1.2.1 · directional
From cloud architect
47 % overlap
Partial match
To cloud DevOps engineer
13 You already bring
12 Still to learn
30 Skills in the target role2
Learning distance Substantial retraining

57.9/ 100

1 How much of what a cloud DevOps engineer is expected to do is already part of a cloud architect’s work. Directional: the figure for the reverse move differs, because moving into a speciality is not the same problem as moving out of one. 2 Every skill the cloud DevOps engineer role is recorded as needing, required and optional together. What these numbers mean.

Why

Why this move works

A cloud DevOps engineer role treats 12 of its required skills as things a cloud architect already does. You would walk in with these on day one.

  • DevOps
  • automate cloud tasks
  • cloud security and compliance
  • cloud technologies
  • deploy cloud resource
  • design cloud architecture

What stands in the way is 12 required skills the profile does not yet cover. Table 3 groups them; Table 4 says which to take first.

Table 2

Table 2 · What you already bring

Of the 13 skills that carry over, these are the ones fewest other occupations ask for. A cloud DevOps engineer role needs them, and most people applying for one will not have them already. This is the part of a cloud architect background worth leading with.

Skill the target role also needs Area
  • already held deploy cloud resource working with computers
  • already held design cloud networks communication, collaboration and creativity
  • already held plan migration to cloud working with computers
  • already held do cloud refactoring working with computers
  • already held develop with cloud services working with computers
  • already held Agile development information and communication technologies (icts)

All 13 carried skills, including the 12 the cloud DevOps engineer role treats as required.

Table 3

Table 3 · What you may need to learn

The 17 missing skills fall into 6 areas of the ESCO skill hierarchy, numbered in the order worth working in. Areas carrying the most required skills come first, and inside each one the required skills sit above the optional ones. Nothing here is a verdict on you: it is a list of what this particular job asks for that your current one does not.

Skill to pick up Tier
01 information and communication technologies (icts) 7 required, 4 supplementary
  • still to learn ICT system programming required
  • still to learn JavaScript required
  • still to learn Jenkins (tools for software configuration management) required
  • still to learn cloud monitoring and reporting required
  • still to learn integrated development environment software required
  • still to learn software frameworks required
  • still to learn system backup best practice required
  • optional, not held ASP.NET optional
  • optional, not held Eclipse (integrated development environment software) optional
  • optional, not held KDevelop optional
  • optional, not held application usability optional
02 information skills 2 required
  • still to learn implement cloud security and compliance required
  • still to learn manage cloud data and storage required
03 engineering, manufacturing and construction 1 required
  • still to learn computer engineering required
04 management skills 1 required
  • still to learn manage disaster recovery plans required
05 working with computers 1 required
  • still to learn implement ICT recovery system required
06 business, administration and law 1 supplementary
  • optional, not held ICT project management methodologies optional
Table 4

Table 4 · Where to start

The 3 entries a cloud DevOps engineer role is least likely to hire without. The ordering is computed from the skill data, not from what pays.

Each entry opens a course search for that skill. Career Overlap earns nothing from these links.

Appendix

Appendix · The rest of the record

All 13 skills that carry over
Skill Type
  • already held DevOps knowledge
  • already held automate cloud tasks skill
  • already held cloud security and compliance knowledge
  • already held cloud technologies knowledge
  • already held deploy cloud resource skill
  • already held design cloud architecture skill
  • already held design cloud networks skill
  • already held design database in the cloud skill
  • already held design for organisational complexity skill
  • already held develop with cloud services skill
  • already held do cloud refactoring skill
  • already held plan migration to cloud skill
  • already held Agile development knowledge
5 supplementary skills, helpful but not required
Skill to pick up Tier
  • optional, not held ASP.NET optional
  • optional, not held Eclipse (integrated development environment software) optional
  • optional, not held ICT project management methodologies optional
  • optional, not held KDevelop optional
  • optional, not held application usability optional
4 held skills the cloud DevOps engineer role does not ask for
Skill Type
  • not needed by the target role Agile project management knowledge
  • not needed by the target role ICT architectural frameworks knowledge
  • not needed by the target role collaborate with engineers skill
  • not needed by the target role coordinate engineering teams skill
13 gaps that are knowledge rather than practice

Knowledge gaps usually close through study. Practical skill gaps usually need something you can point at.

Skill to pick up Tier
  • still to learn ICT system programming required
  • still to learn JavaScript required
  • still to learn Jenkins (tools for software configuration management) required
  • still to learn cloud monitoring and reporting required
  • still to learn integrated development environment software required
  • still to learn software frameworks required
  • still to learn computer engineering required
  • still to learn system backup best practice required
  • optional, not held ASP.NET optional
  • optional, not held Eclipse (integrated development environment software) optional
  • optional, not held ICT project management methodologies optional
  • optional, not held KDevelop optional
  • optional, not held application usability optional
Index

Other moves recorded from cloud architect

Full index of moves from cloud architect

FAQ

Common questions about this move

Can a cloud architect become a cloud DevOps engineer?

Yes, and it is a substantial move. A cloud architect already covers 47% of what a cloud DevOps engineer is expected to do: 13 skills carry over, 12 of which the cloud DevOps engineer role treats as required.

What skills does a cloud architect need to become a cloud DevOps engineer?

12 required skills are missing, plus 5 optional ones. They fall into 6 areas of the ESCO skill hierarchy, led by information and communication technologies (icts). The single most important is ICT system programming.

How hard is the move from cloud architect to cloud DevOps engineer?

Its learning distance is 57.9 out of 100, which is the substantial band. That accounts for both how much is missing and how specialised those skills are.

Note

How this record was compiled

Both occupations are taken from ESCO, which lists the skills and knowledge each occupation is expected to have and marks every one required or optional. Nothing here is a prediction about hiring, and nothing here knows that a particular employer wants a particular certificate. Treat Table 3 as a starting point for your own research rather than a syllabus. The full method states what these figures can and cannot tell you.