Career Overlap Transition record
RecordMove

ICT system architect to database designer

An ICT system architect already meets 59% of what the database designer role asks for. The move turns on 12 required skills not yet in the profile.

Fig. 1 · Skill transfer ESCO v1.2.1 · directional
From ICT system architect
59 % overlap
Partial match
To database designer
63 You already bring
12 Still to learn
103 Skills in the target role2
Learning distance Substantial retraining

57.2/ 100

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

Why

Why this move works

A database designer role treats 15 of its required skills as things an ICT system architect already does. You would walk in with these on day one.

  • ICT security legislation
  • analyse business requirements
  • apply ICT systems theory
  • assess ICT knowledge
  • business process modelling
  • database development tools

What stands in the way is 12 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 63 skills that carry over, these are the ones fewest other occupations ask for. A database designer role needs them, and most people applying for one will not have them already. This is the part of an ICT system architect background worth leading with.

Skill the target role also needs Area
  • already held Oracle WebLogic information and communication technologies (icts)
  • already held manage standards for data exchange management skills
  • 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
  • already held database development tools information and communication technologies (icts)

All 63 carried skills, including the 15 the database designer role treats as required.

Table 3

Table 3 · What you may need to learn

The 40 missing skills fall into 5 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) 4 required, 24 supplementary
  • still to learn database management systems required
  • still to learn query languages required
  • still to learn resource description framework query language required
  • still to learn database required
  • optional, not held CA Datacom/DB optional
  • optional, not held DB2 optional
  • optional, not held Filemaker (database management systems) optional
  • optional, not held IBM Informix optional
  • optional, not held LDAP optional
  • optional, not held LINQ optional
  • optional, not held MDX optional
  • optional, not held MarkLogic optional
  • optional, not held Microsoft Access optional
  • optional, not held MySQL optional
  • optional, not held N1QL optional
  • optional, not held ObjectStore optional
  • optional, not held OpenEdge Database optional
  • optional, not held Oracle Relational Database optional
  • optional, not held PostgreSQL optional
  • optional, not held SPARQL optional
  • optional, not held SQL Server optional
  • optional, not held Teradata Database optional
  • optional, not held TripleStore optional
  • optional, not held XQuery optional
  • optional, not held data models optional
  • optional, not held unstructured data optional
  • optional, not held data engineering optional
  • optional, not held data science optional
02 working with computers 3 required, 3 supplementary
  • still to learn migrate existing data required
  • still to learn operate relational database management system required
  • still to learn perform data analysis required
  • optional, not held define database physical structure optional
  • optional, not held use access control software optional
  • optional, not held use databases optional
03 communication, collaboration and creativity 3 required, 1 supplementary
  • still to learn create database diagrams required
  • still to learn create software design required
  • still to learn write database documentation required
  • optional, not held design database backup specifications optional
04 information skills 1 required
  • still to learn create data sets required
05 management skills 1 required
  • still to learn develop automated migration methods required
Table 4

Table 4 · Where to start

The 3 entries a database designer 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 63 skills that carry over
Skill Type
  • already held ICT security legislation knowledge
  • 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 database development tools knowledge
  • already held define technical requirements skill
  • already held design database scheme skill
  • already held information structure knowledge
  • already held manage database skill
  • already held manage standards for data exchange skill
  • already held systems development life-cycle knowledge
  • already held systems theory knowledge
  • 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 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 Oracle WebLogic 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 technical communication skills skill
  • already held build business relationships skill
  • already held computer programming knowledge
  • already held design database in the cloud skill
  • already held lean project management knowledge
  • already held manage cloud data and storage skill
  • already held perform resource planning skill
28 supplementary skills, helpful but not required
Skill to pick up Tier
  • optional, not held CA Datacom/DB optional
  • optional, not held DB2 optional
  • optional, not held Filemaker (database management systems) optional
  • optional, not held IBM Informix optional
  • optional, not held LDAP optional
  • optional, not held LINQ optional
  • optional, not held MDX optional
  • optional, not held MarkLogic optional
  • optional, not held Microsoft Access optional
  • optional, not held MySQL optional
  • optional, not held N1QL optional
  • optional, not held ObjectStore optional
  • optional, not held OpenEdge Database optional
  • optional, not held Oracle Relational Database optional
  • optional, not held PostgreSQL optional
  • optional, not held SPARQL optional
  • optional, not held SQL Server optional
  • optional, not held Teradata Database optional
  • optional, not held TripleStore optional
  • optional, not held XQuery optional
  • optional, not held data models optional
  • optional, not held define database physical structure optional
  • optional, not held design database backup specifications optional
  • optional, not held unstructured data optional
  • optional, not held use access control software optional
  • optional, not held data engineering optional
  • optional, not held data science optional
  • optional, not held use databases optional
29 held skills the database designer role does not ask for
Skill Type
  • not needed by the target role ICT process quality models knowledge
  • not needed by the target role ICT system integration knowledge
  • not needed by the target role ICT system programming knowledge
  • not needed by the target role acquire system component skill
  • not needed by the target role align software with system architectures skill
  • not needed by the target role create data models skill
  • not needed by the target role defence standard procedures knowledge
  • not needed by the target role design cloud architecture skill
  • not needed by the target role design enterprise architecture skill
  • not needed by the target role design for organisational complexity skill
  • not needed by the target role design information system skill
  • not needed by the target role design process skill
  • not needed by the target role develop with cloud services skill
  • not needed by the target role digital systems knowledge
  • not needed by the target role hardware platforms knowledge
  • not needed by the target role image recognition knowledge
  • not needed by the target role implement ICT security policies skill
  • not needed by the target role integrate system components skill
  • not needed by the target role manage staff skill
  • not needed by the target role manage system testing skill
  • not needed by the target role model based system engineering knowledge
  • not needed by the target role plan migration to cloud skill
  • not needed by the target role provide cost benefit analysis reports skill
  • not needed by the target role security engineering knowledge
  • not needed by the target role solve ICT system problems skill
  • not needed by the target role system design knowledge
  • not needed by the target role task algorithmisation knowledge
  • not needed by the target role use an application-specific interface skill
  • not needed by the target role use object-oriented programming skill
28 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 database management systems required
  • still to learn query languages required
  • still to learn resource description framework query language required
  • still to learn database required
  • optional, not held CA Datacom/DB optional
  • optional, not held DB2 optional
  • optional, not held Filemaker (database management systems) optional
  • optional, not held IBM Informix optional
  • optional, not held LDAP optional
  • optional, not held LINQ optional
  • optional, not held MDX optional
  • optional, not held MarkLogic optional
  • optional, not held Microsoft Access optional
  • optional, not held MySQL optional
  • optional, not held N1QL optional
  • optional, not held ObjectStore optional
  • optional, not held OpenEdge Database optional
  • optional, not held Oracle Relational Database optional
  • optional, not held PostgreSQL optional
  • optional, not held SPARQL optional
  • optional, not held SQL Server optional
  • optional, not held Teradata Database optional
  • optional, not held TripleStore optional
  • optional, not held XQuery optional
  • optional, not held data models optional
  • optional, not held unstructured data optional
  • optional, not held data engineering optional
  • optional, not held data science optional
Index
FAQ

Common questions about this move

Can an ICT system architect become a database designer?

Yes, and it is a substantial move. An ICT system architect already covers 59% of what a database designer is expected to do: 63 skills carry over, 15 of which the database designer role treats as required.

What skills does an ICT system architect need to become a database designer?

12 required skills are missing, plus 28 optional ones. They fall into 5 areas of the ESCO skill hierarchy, led by information and communication technologies (icts). The single most important is create database diagrams.

How hard is the move from ICT system architect to database designer?

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