Artificial intelligence engineer to software architect
An artificial intelligence engineer already meets 47% of what the software architect role asks for. The move turns on 13 required skills not yet in the profile.
65.4/ 100
1 How much of what a software architect is expected to do is already part of an artificial intelligence engineer’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 software architect role is recorded as needing, required and optional together. What these numbers mean.
Why this move works
A software architect role treats 6 of its required skills as things an artificial intelligence engineer already does. You would walk in with these on day one.
- analyse business requirements
- build business relationships
- business process modelling
- define technical requirements
- design process
- systems development life-cycle
What stands in the way is 13 required skills the profile does not yet cover. Table 3 groups them; Table 4 says which to take first.
Table 2 · What you already bring
Of the 47 skills that carry over, these are the ones fewest other occupations ask for. A software architect role needs them, and most people applying for one will not have them already. This is the part of an artificial intelligence engineer background worth leading with.
- already held apply ICT systems theory working with computers
- already held design database scheme communication, collaboration and creativity
- already held task algorithmisation information and communication technologies (icts)
- already held design process communication, collaboration and creativity
- already held analyse business requirements information skills
- already held business process modelling business, administration and law
All 47 carried skills, including the 6 the software architect role treats as required.
Table 3 · What you may need to learn
The 42 missing skills fall into 7 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.
- still to learn object-oriented modelling required
- still to learn system design required
- still to learn tools for software configuration management required
- still to learn unified modelling language required
- optional, not held ABAP optional
- optional, not held AJAX optional
- optional, not held APL optional
- optional, not held ASP.NET optional
- optional, not held Ansible optional
- optional, not held Apache Maven optional
- optional, not held Jenkins (tools for software configuration management) optional
- optional, not held Puppet (tools for software configuration management) optional
- optional, not held SPARK optional
- optional, not held STAF optional
- optional, not held Salt (tools for software configuration management) optional
- optional, not held WildFly optional
- optional, not held systems theory optional
- optional, not held web programming optional
- still to learn align software with system architectures required
- still to learn analyse software specifications required
- still to learn use an application-specific interface required
- optional, not held develop software prototype optional
- optional, not held do cloud refactoring optional
- optional, not held implement data warehousing techniques optional
- optional, not held use markup languages optional
- optional, not held use query languages optional
- optional, not held utilise computer-aided software engineering tools optional
- optional, not held perform ICT troubleshooting optional
- still to learn create software design required
- still to learn define software architecture required
- still to learn create flowchart diagram required
- optional, not held design cloud architecture optional
- optional, not held design database in the cloud optional
- optional, not held provide ICT consulting advice optional
- still to learn collect customer feedback on applications required
- still to learn provide cost benefit analysis reports required
- optional, not held perform resource planning optional
- optional, not held perform risk analysis optional
- still to learn oversee development of software required
- optional, not held manage staff optional
- optional, not held ICT security legislation optional
1 further area in the appendix
Table 4 · Where to start
The 3 entries a software architect role is least likely to hire without. The ordering is computed from the skill data, not from what pays.
- 01 align software with system architectures practise this
- 02 analyse software specifications practise this
- 03 create software design practise this
Each entry opens a course search for that skill. Career Overlap earns nothing from these links.
Appendix · The rest of the record
All 47 skills that carry over
- already held analyse business requirements skill
- already held build business relationships skill
- already held business process modelling knowledge
- already held define technical requirements skill
- already held design process skill
- already held systems development life-cycle knowledge
- already held Agile project management knowledge
- already held Assembly (computer programming) knowledge
- already held C# knowledge
- already held C++ knowledge
- already held COBOL knowledge
- already held CoffeeScript knowledge
- already held Common Lisp knowledge
- already held Erlang knowledge
- already held Groovy knowledge
- already held Haskell knowledge
- already held ICT project management methodologies knowledge
- already held Java (computer programming) knowledge
- already held JavaScript knowledge
- already held Lisp knowledge
- already held MATLAB knowledge
- already held ML (computer programming) knowledge
- already held Microsoft Visual C++ knowledge
- already held Objective-C knowledge
- already held OpenEdge Advanced Business Language knowledge
- already held PHP knowledge
- already held Pascal (computer programming) knowledge
- already held Perl knowledge
- already held Process-based management knowledge
- already held Prolog (computer programming) knowledge
- already held Python (computer programming) knowledge
- already held R knowledge
- already held Ruby (computer programming) knowledge
- already held SAP R3 knowledge
- already held SAS language knowledge
- already held Scala knowledge
- already held Scratch (computer programming) knowledge
- already held Smalltalk (computer programming) knowledge
- already held Swift (computer programming) knowledge
- already held TypeScript knowledge
- already held VBScript knowledge
- already held Visual Basic knowledge
- already held apply ICT systems theory skill
- already held computer programming knowledge
- already held design database scheme skill
- already held lean project management knowledge
- already held task algorithmisation knowledge
The 1 learning area not shown above
- optional, not held security engineering optional
29 supplementary skills, helpful but not required
- optional, not held ABAP optional
- optional, not held AJAX optional
- optional, not held APL optional
- optional, not held ASP.NET optional
- optional, not held Ansible optional
- optional, not held Apache Maven optional
- optional, not held ICT security legislation optional
- optional, not held Jenkins (tools for software configuration management) optional
- optional, not held Puppet (tools for software configuration management) optional
- optional, not held SPARK optional
- optional, not held STAF optional
- optional, not held Salt (tools for software configuration management) optional
- optional, not held WildFly optional
- optional, not held design cloud architecture optional
- optional, not held design database in the cloud optional
- optional, not held develop software prototype optional
- optional, not held do cloud refactoring optional
- optional, not held implement data warehousing techniques optional
- optional, not held provide ICT consulting advice optional
- optional, not held systems theory optional
- optional, not held use markup languages optional
- optional, not held use query languages optional
- optional, not held utilise computer-aided software engineering tools optional
- optional, not held web programming optional
- optional, not held manage staff optional
- optional, not held perform ICT troubleshooting optional
- optional, not held perform resource planning optional
- optional, not held perform risk analysis optional
- optional, not held security engineering optional
42 held skills the software architect role does not ask for
- not needed by the target role LINQ knowledge
- not needed by the target role N1QL knowledge
- not needed by the target role SPARQL knowledge
- not needed by the target role algorithms knowledge
- not needed by the target role analyse big data skill
- not needed by the target role apply systemic design thinking skill
- not needed by the target role artificial neural networks knowledge
- not needed by the target role assess ICT knowledge skill
- not needed by the target role build predictive models skill
- not needed by the target role build recommender systems skill
- not needed by the target role business analytics knowledge
- not needed by the target role business intelligence knowledge
- not needed by the target role computer simulation knowledge
- not needed by the target role computer vision knowledge
- not needed by the target role create data sets skill
- not needed by the target role creatively use digital technologies skill
- not needed by the target role data mining knowledge
- not needed by the target role data models knowledge
- not needed by the target role data science knowledge
- not needed by the target role database development tools knowledge
- not needed by the target role deep learning knowledge
- not needed by the target role deliver visual presentation of data skill
- not needed by the target role design application interfaces skill
- not needed by the target role develop creative ideas skill
- not needed by the target role develop statistical software skill
- not needed by the target role digital data processing skill
- not needed by the target role identify processes for re-engineering skill
- not needed by the target role information architecture knowledge
- not needed by the target role information categorisation knowledge
- not needed by the target role information extraction knowledge
- not needed by the target role information structure knowledge
- not needed by the target role manage ICT data classification skill
- not needed by the target role manage ICT semantic integration skill
- not needed by the target role manage business knowledge skill
- not needed by the target role operational research knowledge
- not needed by the target role perform dimensionality reduction skill
- not needed by the target role principles of artificial intelligence knowledge
- not needed by the target role resource description framework query language knowledge
- not needed by the target role unstructured data knowledge
- not needed by the target role use data processing techniques skill
2 further entries not listed here
20 gaps that are knowledge rather than practice
Knowledge gaps usually close through study. Practical skill gaps usually need something you can point at.
- still to learn object-oriented modelling required
- still to learn system design required
- still to learn tools for software configuration management required
- still to learn unified modelling language required
- optional, not held ABAP optional
- optional, not held AJAX optional
- optional, not held APL optional
- optional, not held ASP.NET optional
- optional, not held Ansible optional
- optional, not held Apache Maven optional
- optional, not held ICT security legislation optional
- optional, not held Jenkins (tools for software configuration management) optional
- optional, not held Puppet (tools for software configuration management) optional
- optional, not held SPARK optional
- optional, not held STAF optional
- optional, not held Salt (tools for software configuration management) optional
- optional, not held WildFly optional
- optional, not held systems theory optional
- optional, not held web programming optional
- optional, not held security engineering optional
Other moves recorded from artificial intelligence engineer
Common questions about this move
Can an artificial intelligence engineer become a software architect?
Yes, and it is a substantial move. An artificial intelligence engineer already covers 47% of what a software architect is expected to do: 47 skills carry over, 6 of which the software architect role treats as required.
What skills does an artificial intelligence engineer need to become a software architect?
13 required skills are missing, plus 29 optional ones. They fall into 7 areas of the ESCO skill hierarchy, led by information and communication technologies (icts). The single most important is align software with system architectures.
How hard is the move from artificial intelligence engineer to software architect?
Its learning distance is 65.4 out of 100, which is the substantial band. That accounts for both how much is missing and how specialised those skills are.
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.