Table 1Transition record

IoT developertodata engineer

A IoT developer already meets 20% of what the data engineer role asks for. The move turns on 18 required skills not yet in the profile.

From IoT developer

20%

Overlap1

To data engineer

5 Skills carried over

18 Required, not held

79.2 Difficulty2

adjacent 0–30

moderate 30–55

substantial 55–75

career change 75–100

this move, 79.2

This move: 79.2 of 100 · career change

1 Share of the data engineer role’s weighted skill requirement already met by the IoT developer 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.

Table 2

Table 2 · What you already bring

Of the 5 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 IoT developer background worth leading with.

Skill the target role also needs Area

already held perform dimensionality reduction working with computers
already held establish data processes working with computers
already held use data processing techniques working with computers
already held computer science information and communication technologies (icts)
already held digital data processing working with computers

All 5 carried skills, including the 5 the data engineer role treats as required.

Table 3

Table 3 · What you would need to learn

The 23 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.

Skill to acquire Tier

01 information and communication technologies (icts) 7 required, 2 supplementary

required, not held data warehouse required
required, not held cloud technologies required
required, not held data models required
required, not held data storage required
required, not held database management systems required
required, not held unstructured data required
required, not held data analytics required

optional, not held SAS Data Management optional
optional, not held Teradata Database optional

02 working with computers 5 required

required, not held develop data processing applications required
required, not held implement data warehousing techniques required
required, not held manage quantitative data required
required, not held store digital data and systems required
required, not held use databases required

03 information skills 4 required, 2 supplementary

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
optional, not held create data models optional

04 communication, collaboration and creativity 2 required

required, not held design database in the cloud required
required, not held manage ICT data architecture required

05 natural sciences, mathematics and statistics 1 supplementary

optional, not held statistics optional

Table 4

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.

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

Appendix

Appendix · The rest of the record

All 5 skills that carry over

Skill Type

already held computer science knowledge
already held digital data processing skill
already held establish data processes skill
already held perform dimensionality reduction skill
already held use data processing techniques skill

5 supplementary skills, helpful but not required

Skill to acquire Tier

optional, not held SAS Data Management optional
optional, not held Teradata Database optional
optional, not held analyse pipeline database information optional
optional, not held create data models optional
optional, not held statistics optional

17 held skills the data engineer role does not ask for

Skill Type

not needed by the target role ICT architectural frameworks knowledge
not needed by the target role ICT software specifications knowledge
not needed by the target role ICT system programming knowledge
not needed by the target role Internet of Things 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 computer technology knowledge
not needed by the target role design information system skill
not needed by the target role develop ICT workflow skill
not needed by the target role hardware testing methods knowledge
not needed by the target role machine learning knowledge
not needed by the target role mechatronics knowledge
not needed by the target role mobile device software frameworks knowledge
not needed by the target role perform online data analysis skill
not needed by the target role principles of artificial intelligence knowledge
not needed by the target role task algorithmisation knowledge
not needed by the target role utilise machine learning skill

10 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 acquire Tier

required, not held data warehouse required
required, not held cloud technologies required
required, not held data models required
required, not held data storage required
required, not held database management systems required
required, not held unstructured data 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

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.