Career Overlap Transition record
RecordMove

Data warehouse designer to knowledge engineer

A data warehouse designer already meets 67% of what the knowledge engineer role asks for. The move turns on 11 required skills not yet in the profile.

Fig. 1 · Skill transfer ESCO v1.2.1 · directional
From data warehouse designer
67 % overlap
Strong match
To knowledge engineer
65 You already bring
11 Still to learn
89 Skills in the target role2
Learning distance Real move, short list to learn

46.9/ 100

1 How much of what a knowledge engineer is expected to do is already part of a data warehouse designer’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 knowledge engineer role is recorded as needing, required and optional together. What these numbers mean.

Why

Why this move works

A knowledge engineer role treats 14 of its required skills as things a data warehouse designer already does. You would walk in with these on day one.

  • analyse business requirements
  • apply ICT systems theory
  • assess ICT knowledge
  • business process modelling
  • data science
  • database development tools

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

Table 2 · What you already bring

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

Skill the target role also needs Area
  • already held define database physical structure working with computers
  • already held create database diagrams communication, collaboration and creativity
  • already held store digital data and systems working with computers
  • already held systems theory information and communication technologies (icts)
  • already held apply ICT systems theory working with computers
  • already held assess ICT knowledge management skills

All 65 carried skills, including the 14 the knowledge engineer role treats as required.

Table 3

Table 3 · What you may need to learn

The 24 missing skills fall into 8 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) 5 required, 4 supplementary
  • still to learn information extraction required
  • still to learn principles of artificial intelligence required
  • still to learn data engineering required
  • still to learn systems development life-cycle required
  • still to learn task algorithmisation required
  • optional, not held cloud technologies optional
  • optional, not held data mining optional
  • optional, not held decision support systems optional
  • optional, not held information architecture optional
02 working with computers 2 required, 4 supplementary
  • still to learn manage ICT semantic integration required
  • still to learn use an application-specific interface required
  • optional, not held implement a virtual private network optional
  • optional, not held utilise decision support system optional
  • optional, not held manage digital documents optional
  • optional, not held use spreadsheets software optional
03 arts and humanities 1 required, 1 supplementary
  • still to learn natural language processing required
  • optional, not held visual presentation techniques optional
04 business, administration and law 1 required, 1 supplementary
  • still to learn business intelligence required
  • optional, not held ICT project management optional
05 information skills 1 required
  • still to learn create semantic trees required
06 management skills 1 required
  • still to learn manage business knowledge required

2 further areas in the appendix

Table 4

Table 4 · Where to start

The 3 entries a knowledge 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 65 skills that carry over
Skill Type
  • already held analyse business requirements skill
  • already held apply ICT systems theory skill
  • already held assess ICT knowledge skill
  • already held business process modelling knowledge
  • already held data science knowledge
  • already held database development tools knowledge
  • already held define technical requirements skill
  • already held information structure knowledge
  • already held manage database skill
  • already held resource description framework query language knowledge
  • already held systems theory knowledge
  • already held use databases skill
  • already held use markup languages skill
  • already held web programming knowledge
  • already held ABAP knowledge
  • already held AJAX knowledge
  • already held APL knowledge
  • already held ASP.NET 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 security legislation knowledge
  • already held Java (computer programming) knowledge
  • already held JavaScript knowledge
  • already held LINQ knowledge
  • already held Lisp knowledge
  • already held MATLAB knowledge
  • already held ML (computer programming) knowledge
  • already held Microsoft Visual C++ knowledge
  • already held N1QL 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 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 SPARQL 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 build business relationships skill
  • already held computer programming knowledge
  • already held create database diagrams skill
  • already held define database physical structure skill
  • already held design database scheme skill
  • already held manage cloud data and storage skill
  • already held store digital data and systems skill
  • already held unstructured data knowledge
  • already held use back-up and recovery tools skill
  • already held use query languages skill
The 2 learning areas not shown above
Skill to pick up Tier
07 social sciences, journalism and information 2 supplementary
  • optional, not held information categorisation optional
  • optional, not held cognitive psychology optional
08 communication, collaboration and creativity 1 supplementary
  • optional, not held design application interfaces optional
13 supplementary skills, helpful but not required
Skill to pick up Tier
  • optional, not held ICT project management optional
  • optional, not held cloud technologies optional
  • optional, not held data mining optional
  • optional, not held decision support systems optional
  • optional, not held design application interfaces optional
  • optional, not held implement a virtual private network optional
  • optional, not held information architecture optional
  • optional, not held information categorisation optional
  • optional, not held utilise decision support system optional
  • optional, not held visual presentation techniques optional
  • optional, not held cognitive psychology optional
  • optional, not held manage digital documents optional
  • optional, not held use spreadsheets software optional
45 held skills the knowledge engineer role does not ask for
Skill Type
  • not needed by the target role Agile project management knowledge
  • not needed by the target role CA Datacom/DB knowledge
  • not needed by the target role DB2 knowledge
  • not needed by the target role Filemaker (database management systems) knowledge
  • not needed by the target role IBM Informix knowledge
  • not needed by the target role ICT project management methodologies knowledge
  • not needed by the target role LDAP knowledge
  • not needed by the target role MDX knowledge
  • not needed by the target role MarkLogic knowledge
  • not needed by the target role Microsoft Access knowledge
  • not needed by the target role MySQL knowledge
  • not needed by the target role ObjectStore knowledge
  • not needed by the target role OpenEdge Database knowledge
  • not needed by the target role Oracle Relational Database knowledge
  • not needed by the target role PostgreSQL knowledge
  • not needed by the target role Process-based management knowledge
  • not needed by the target role SQL Server knowledge
  • not needed by the target role Teradata Database knowledge
  • not needed by the target role TripleStore knowledge
  • not needed by the target role XQuery knowledge
  • not needed by the target role apply technical communication skills skill
  • not needed by the target role create data sets skill
  • not needed by the target role create software design skill
  • not needed by the target role data models knowledge
  • not needed by the target role data visualisation software knowledge
  • not needed by the target role data warehouse knowledge
  • not needed by the target role database knowledge
  • not needed by the target role database management systems knowledge
  • not needed by the target role design database backup specifications skill
  • not needed by the target role design database in the cloud skill
  • not needed by the target role design user interface skill
  • not needed by the target role develop automated migration methods skill
  • not needed by the target role develop reporting software skill
  • not needed by the target role identify software for warehouse management skill
  • not needed by the target role lean project management knowledge
  • not needed by the target role manage standards for data exchange skill
  • not needed by the target role migrate existing data skill
  • not needed by the target role operate relational database management system skill
  • not needed by the target role perform data analysis skill
  • not needed by the target role perform resource planning skill

5 further entries not listed here

15 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 information extraction required
  • still to learn natural language processing required
  • still to learn principles of artificial intelligence required
  • still to learn business intelligence required
  • still to learn data engineering required
  • still to learn systems development life-cycle required
  • still to learn task algorithmisation required
  • optional, not held ICT project management optional
  • optional, not held cloud technologies optional
  • optional, not held data mining optional
  • optional, not held decision support systems optional
  • optional, not held information architecture optional
  • optional, not held information categorisation optional
  • optional, not held visual presentation techniques optional
  • optional, not held cognitive psychology optional
Index

Other moves recorded from data warehouse designer

Full index of moves from data warehouse designer

FAQ

Common questions about this move

Can a data warehouse designer become a knowledge engineer?

Yes, and it is a moderate move. A data warehouse designer already covers 67% of what a knowledge engineer is expected to do: 65 skills carry over, 14 of which the knowledge engineer role treats as required.

What skills does a data warehouse designer need to become a knowledge engineer?

11 required skills are missing, plus 13 optional ones. They fall into 8 areas of the ESCO skill hierarchy, led by information and communication technologies (icts). The single most important is create semantic trees.

How hard is the move from data warehouse designer to knowledge engineer?

Its learning distance is 46.9 out of 100, which is the moderate 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.