ICT information and knowledge managertodata engineer
A ICT information and knowledge manager already meets 26% of what the data engineer role asks for. The move turns on 17 required skills not yet in the profile.
26%
74.4/ 100
1 Share of the data engineer role’s weighted skill requirement already met by the ICT information and knowledge manager profile. Required skills count in full, supplementary skills at 0.35. Directional: the figure for the reverse move differs. 2 Combines what is missing with how specialised it is, so a gap of general skills scores easier than the same number of narrow ones.
Why this move works
A data engineer role treats 6 of its required skills as things a ICT information and knowledge manager already does. These are the ones it depends on most.
- data models
- data storage
- implement data warehousing techniques
- manage ICT data architecture
- unstructured data
- use databases
What stands in the way is 17 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 7 skills that carry over, these are the ones fewest other occupations ask for. A data engineer role needs them, and most people applying for one will not have them already. This is the part of a ICT information and knowledge manager background worth leading with.
- already held implement data warehousing techniques working with computers
- already held manage ICT data architecture communication, collaboration and creativity
- already held create data models information skills
- already held data models information and communication technologies (icts)
- already held use databases working with computers
- already held unstructured data information and communication technologies (icts)
All 7 carried skills, including the 6 the data engineer role treats as required.
Table 3 · What you would need to learn
The 21 missing skills fall into 5 areas of the ESCO skill hierarchy, numbered below in the order worth working in: the areas carrying the most required skills come first, and inside each one the required skills sit above the supplementary ones.
- required, not held develop data processing applications required
- required, not held digital data processing required
- required, not held establish data processes required
- required, not held manage quantitative data required
- required, not held perform dimensionality reduction required
- required, not held store digital data and systems required
- required, not held use data processing techniques required
- required, not held data warehouse required
- required, not held cloud technologies required
- required, not held database management systems required
- required, not held computer science required
- required, not held data analytics required
- optional, not held SAS Data Management optional
- optional, not held Teradata Database optional
- required, not held manage data required
- required, not held create data sets required
- required, not held manage research data required
- required, not held process data required
- optional, not held analyse pipeline database information optional
- required, not held design database in the cloud required
- optional, not held statistics optional
Table 4 · Where to start
The 3 entries a data engineer role is least likely to hire without. The ordering is computed from the skill data, not from what pays.
- 01 data warehouse knowledge · occupation specific
- 02 develop data processing applications skill · occupation specific
- 03 cloud technologies knowledge · sector specific
Each entry opens a course search for that skill. Career Overlap earns nothing from these links.
Appendix · The rest of the record
All 7 skills that carry over
- already held data models knowledge
- already held data storage knowledge
- already held implement data warehousing techniques skill
- already held manage ICT data architecture skill
- already held unstructured data knowledge
- already held use databases skill
- already held create data models skill
4 supplementary skills, helpful but not required
- optional, not held SAS Data Management optional
- optional, not held Teradata Database optional
- optional, not held analyse pipeline database information optional
- optional, not held statistics optional
35 held skills the data engineer role does not ask for
- not needed by the target role analyse the context of an organisation skill
- not needed by the target role assess ICT knowledge skill
- not needed by the target role assess informational needs skill
- not needed by the target role attack vectors knowledge
- not needed by the target role business intelligence knowledge
- not needed by the target role business processes knowledge
- not needed by the target role coordinate technological activities skill
- not needed by the target role data mining knowledge
- not needed by the target role data protection knowledge
- not needed by the target role data quality assessment knowledge
- not needed by the target role decision support systems knowledge
- not needed by the target role define technology strategy skill
- not needed by the target role deliver visual presentation of data skill
- not needed by the target role design information system skill
- not needed by the target role ensure information privacy skill
- not needed by the target role implement ICT security policies 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 confidentiality knowledge
- not needed by the target role information extraction knowledge
- not needed by the target role information security strategy knowledge
- not needed by the target role information structure knowledge
- not needed by the target role interact with users to gather requirements skill
- not needed by the target role interpret current data skill
- not needed by the target role keep up with the latest information systems solutions skill
- not needed by the target role manage business knowledge skill
- not needed by the target role manage cloud data and storage skill
- not needed by the target role manage data collection systems skill
- not needed by the target role manage information access aids skill
- not needed by the target role manage information sources skill
- not needed by the target role migrate existing data skill
- not needed by the target role online analytical processing knowledge
- not needed by the target role perform data mining skill
- not needed by the target role structure information skill
- not needed by the target role utilise decision support system skill
8 gaps that are knowledge rather than practice
Knowledge gaps usually close through study. Practical skill gaps usually need something you can point at.
- required, not held data warehouse required
- required, not held cloud technologies required
- required, not held database management systems required
- required, not held computer science required
- required, not held data analytics required
- optional, not held SAS Data Management optional
- optional, not held Teradata Database optional
- optional, not held statistics optional
Other moves recorded from ICT information and knowledge manager
- chief data officer 41% covered · substantial
- data analyst 31% covered · career change
- information manager 25% covered · substantial
- ICT business analysis manager 20% covered · career change
Full index of moves from ICT information and knowledge manager
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.