Chief technology officer to integration engineer
A chief technology officer already meets 46% of what the integration engineer role asks for. The move turns on 11 required skills not yet in the profile.
66/ 100
1 How much of what an integration engineer is expected to do is already part of a chief technology officer’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 integration engineer role is recorded as needing, required and optional together. What these numbers mean.
Why this move works
An integration engineer role treats 5 of its required skills as things a chief technology officer already does. You would walk in with these on day one.
- ICT communications protocols
- ICT project management methodologies
- define technology strategy
- hardware components suppliers
- software components suppliers
What stands in the way is 11 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 44 skills that carry over, these are the ones fewest other occupations ask for. An integration engineer role needs them, and most people applying for one will not have them already. This is the part of a chief technology officer background worth leading with.
- already held software components suppliers information and communication technologies (icts)
- already held hardware components suppliers business, administration and law
- already held software components libraries information and communication technologies (icts)
- already held ICT infrastructure engineering, manufacturing and construction
- already held hardware components information and communication technologies (icts)
- already held ICT communications protocols engineering, manufacturing and construction
All 44 carried skills, including the 5 the integration engineer role treats as required.
Table 3 · What you may need to learn
The 43 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.
- still to learn design component interfaces required
- still to learn analyse network bandwidth requirements required
- still to learn deploy ICT systems required
- still to learn integrate system components required
- still to learn use scripting programming required
- optional, not held implement a firewall optional
- optional, not held implement anti-virus software optional
- optional, not held use an application-specific interface optional
- optional, not held utilise computer-aided software engineering tools optional
- optional, not held use back-up and recovery tools optional
- still to learn ICT system user requirements required
- still to learn inter-organisational middleware system required
- still to learn procurement of ICT network equipment required
- optional, not held Ansible optional
- optional, not held Apache Maven optional
- optional, not held Cisco optional
- optional, not held ICT debugging tools optional
- optional, not held ICT network routing optional
- optional, not held ICT recovery techniques optional
- optional, not held ICT system integration optional
- optional, not held ICT system programming optional
- optional, not held Jenkins (tools for software configuration management) optional
- optional, not held Puppet (tools for software configuration management) optional
- optional, not held STAF optional
- optional, not held Salt (tools for software configuration management) optional
- optional, not held Vagrant optional
- optional, not held information architecture optional
- optional, not held information security strategy optional
- optional, not held solution deployment optional
- optional, not held tools for ICT test automation optional
- optional, not held tools for software configuration management optional
- optional, not held systems development life-cycle optional
- still to learn apply ICT system usage policies required
- still to learn apply company policies required
- still to learn define integration strategy required
- optional, not held design computer network optional
- optional, not held adapt to changing situations optional
- optional, not held communicate with customers optional
- optional, not held embedded systems optional
- optional, not held engineering processes optional
- optional, not held interfacing techniques optional
- optional, not held model based system engineering optional
- optional, not held perform project management optional
Table 4 · Where to start
The 3 entries an integration engineer role is least likely to hire without. The ordering is computed from the skill data, not from what pays.
- 01 design component interfaces practise this
- 02 ICT system user requirements study this
- 03 analyse network bandwidth requirements 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 44 skills that carry over
- already held ICT communications protocols knowledge
- already held ICT project management methodologies knowledge
- already held define technology strategy skill
- already held hardware components suppliers knowledge
- already held software components suppliers knowledge
- already held ABAP knowledge
- already held AJAX knowledge
- already held APL knowledge
- already held ASP.NET 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 Common Lisp knowledge
- already held Groovy knowledge
- already held Haskell knowledge
- already held ICT infrastructure 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 Swift (computer programming) knowledge
- already held Visual Basic knowledge
- already held computer programming knowledge
- already held hardware components knowledge
- already held lean project management knowledge
- already held software components libraries knowledge
32 supplementary skills, helpful but not required
- optional, not held Ansible optional
- optional, not held Apache Maven optional
- optional, not held Cisco optional
- optional, not held ICT debugging tools optional
- optional, not held ICT network routing optional
- optional, not held ICT recovery techniques optional
- optional, not held ICT system integration optional
- optional, not held ICT system programming optional
- optional, not held Jenkins (tools for software configuration management) optional
- optional, not held Puppet (tools for software configuration management) optional
- optional, not held STAF optional
- optional, not held Salt (tools for software configuration management) optional
- optional, not held Vagrant optional
- optional, not held design computer network optional
- optional, not held embedded systems optional
- optional, not held engineering processes optional
- optional, not held implement a firewall optional
- optional, not held implement anti-virus software optional
- optional, not held information architecture optional
- optional, not held information security strategy optional
- optional, not held interfacing techniques optional
- optional, not held solution deployment optional
- optional, not held tools for ICT test automation optional
- optional, not held tools for software configuration management optional
- optional, not held use an application-specific interface optional
- optional, not held utilise computer-aided software engineering tools optional
- optional, not held adapt to changing situations optional
- optional, not held communicate with customers optional
- optional, not held model based system engineering optional
- optional, not held perform project management optional
- optional, not held systems development life-cycle optional
- optional, not held use back-up and recovery tools optional
39 held skills the integration engineer role does not ask for
- not needed by the target role CoffeeScript knowledge
- not needed by the target role Erlang knowledge
- not needed by the target role ICT project management knowledge
- not needed by the target role ICT quality policy knowledge
- not needed by the target role Smalltalk (computer programming) knowledge
- not needed by the target role TypeScript knowledge
- not needed by the target role VBScript knowledge
- not needed by the target role administer ICT system skill
- not needed by the target role analyse ICT system skill
- not needed by the target role attack vectors knowledge
- not needed by the target role build business relationships skill
- not needed by the target role business intelligence knowledge
- not needed by the target role business strategy concepts knowledge
- not needed by the target role carry out strategic research skill
- not needed by the target role coordinate technological activities skill
- not needed by the target role decision support systems knowledge
- not needed by the target role digital systems knowledge
- not needed by the target role ensure adherence to organisational ICT standards skill
- not needed by the target role ensure information privacy skill
- not needed by the target role establish an ICT customer support process skill
- not needed by the target role identify processes for re-engineering skill
- not needed by the target role implement ICT coding conventions skill
- not needed by the target role implement corporate governance skill
- not needed by the target role industrial research and development knowledge
- not needed by the target role information structure knowledge
- not needed by the target role internet governance knowledge
- not needed by the target role lead technology development of an organisation skill
- not needed by the target role maintain plan for continuity of operations skill
- not needed by the target role maintain relationship with customers skill
- not needed by the target role manage budgets skill
- not needed by the target role monitor ICT research skill
- not needed by the target role monitor technology trends skill
- not needed by the target role optimise choice of ICT solution skill
- not needed by the target role oversee development of software skill
- not needed by the target role perform business analysis skill
- not needed by the target role review development process of an organisation skill
- not needed by the target role scientific research methodology knowledge
- not needed by the target role use e-services skill
- not needed by the target role utilise decision support system skill
26 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 ICT system user requirements required
- still to learn inter-organisational middleware system required
- still to learn procurement of ICT network equipment required
- optional, not held Ansible optional
- optional, not held Apache Maven optional
- optional, not held Cisco optional
- optional, not held ICT debugging tools optional
- optional, not held ICT network routing optional
- optional, not held ICT recovery techniques optional
- optional, not held ICT system integration optional
- optional, not held ICT system programming optional
- optional, not held Jenkins (tools for software configuration management) optional
- optional, not held Puppet (tools for software configuration management) optional
- optional, not held STAF optional
- optional, not held Salt (tools for software configuration management) optional
- optional, not held Vagrant optional
- optional, not held embedded systems optional
- optional, not held engineering processes optional
- optional, not held information architecture optional
- optional, not held information security strategy optional
- optional, not held interfacing techniques optional
- optional, not held solution deployment optional
- optional, not held tools for ICT test automation optional
- optional, not held tools for software configuration management optional
- optional, not held model based system engineering optional
- optional, not held systems development life-cycle optional
Other moves recorded from chief technology officer
Common questions about this move
Can a chief technology officer become an integration engineer?
Yes, and it is a substantial move. A chief technology officer already covers 46% of what an integration engineer is expected to do: 44 skills carry over, 5 of which the integration engineer role treats as required.
What skills does a chief technology officer need to become an integration engineer?
11 required skills are missing, plus 32 optional ones. They fall into 6 areas of the ESCO skill hierarchy, led by working with computers. The single most important is design component interfaces.
How hard is the move from chief technology officer to integration engineer?
Its learning distance is 66 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.