Career Overlap Transition record
RecordMove

User interface designer to embedded system designer

A user interface designer already meets 45% of what the embedded system designer role asks for. The move turns on 13 required skills not yet in the profile.

Fig. 1 · Skill transfer ESCO v1.2.1 · directional
From user interface designer
45 % overlap
Partial match
To embedded system designer
42 You already bring
13 Still to learn
78 Skills in the target role2
Learning distance Substantial retraining

65.6/ 100

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

Why

Why this move works

An embedded system designer role treats 4 of its required skills as things a user interface designer already does. You would walk in with these on day one.

  • create software design
  • define technical requirements
  • develop creative ideas
  • task algorithmisation

What stands in the way is 13 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 42 skills that carry over, these are the ones fewest other occupations ask for. An embedded system designer role needs them, and most people applying for one will not have them already. This is the part of a user interface designer background worth leading with.

Skill the target role also needs Area
  • already held task algorithmisation information and communication technologies (icts)
  • already held create software design communication, collaboration and creativity
  • already held CoffeeScript information and communication technologies (icts)
  • already held Erlang information and communication technologies (icts)
  • already held Smalltalk (computer programming) information and communication technologies (icts)
  • already held develop creative ideas communication, collaboration and creativity

All 42 carried skills, including the 4 the embedded system designer role treats as required.

Table 3

Table 3 · What you may need to learn

The 36 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) 5 required, 15 supplementary
  • still to learn real-time computing required
  • still to learn system design required
  • still to learn tools for software configuration management required
  • still to learn digital systems required
  • still to learn systems development life-cycle required
  • optional, not held Ansible optional
  • optional, not held Apache Maven optional
  • optional, not held ICT network simulation optional
  • optional, not held ICT security standards optional
  • optional, not held ICT system integration optional
  • optional, not held Jenkins (tools for software configuration management) optional
  • optional, not held Microsoft Visual C++ optional
  • optional, not held Puppet (tools for software configuration management) optional
  • optional, not held SPARK optional
  • optional, not held STAF optional
  • optional, not held Salt (tools for software configuration management) optional
  • optional, not held network management system tools optional
  • optional, not held software components libraries optional
  • optional, not held tools for ICT test automation optional
  • optional, not held hardware components optional
02 engineering, manufacturing and construction 4 required, 5 supplementary
  • still to learn ICT communications protocols required
  • still to learn embedded systems required
  • still to learn engineering control theory required
  • still to learn signal processing required
  • optional, not held field-programmable gate arrays optional
  • optional, not held battery management systems optional
  • optional, not held engineering processes optional
  • optional, not held hardware architectures optional
  • optional, not held state estimation optional
03 communication, collaboration and creativity 2 required
  • still to learn provide ICT consulting advice required
  • still to learn create flowchart diagram required
04 information skills 1 required, 2 supplementary
  • still to learn interpret electronic design specifications required
  • optional, not held verify formal ICT specifications optional
  • optional, not held collect customer feedback on applications optional
05 working with computers 1 required, 1 supplementary
  • still to learn analyse software specifications required
  • optional, not held utilise computer-aided software engineering tools optional
Table 4

Table 4 · Where to start

The 3 entries an embedded system 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 42 skills that carry over
Skill Type
  • already held create software design skill
  • already held define technical requirements skill
  • already held develop creative ideas skill
  • already held task algorithmisation 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 Java (computer programming) knowledge
  • already held JavaScript knowledge
  • already held Lisp knowledge
  • already held MATLAB knowledge
  • already held ML (computer programming) 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 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
23 supplementary skills, helpful but not required
Skill to pick up Tier
  • optional, not held field-programmable gate arrays optional
  • optional, not held Ansible optional
  • optional, not held Apache Maven optional
  • optional, not held ICT network simulation optional
  • optional, not held ICT security standards optional
  • optional, not held ICT system integration optional
  • optional, not held Jenkins (tools for software configuration management) optional
  • optional, not held Microsoft Visual C++ optional
  • optional, not held Puppet (tools for software configuration management) optional
  • optional, not held SPARK optional
  • optional, not held STAF optional
  • optional, not held Salt (tools for software configuration management) optional
  • optional, not held battery management systems optional
  • optional, not held engineering processes optional
  • optional, not held hardware architectures optional
  • optional, not held network management system tools optional
  • optional, not held software components libraries optional
  • optional, not held tools for ICT test automation optional
  • optional, not held utilise computer-aided software engineering tools optional
  • optional, not held verify formal ICT specifications optional
  • optional, not held collect customer feedback on applications optional
  • optional, not held hardware components optional
  • optional, not held state estimation optional
53 held skills the embedded system designer role does not ask for
Skill Type
  • not needed by the target role Adobe Illustrator knowledge
  • not needed by the target role Adobe Photoshop knowledge
  • not needed by the target role Agile development knowledge
  • not needed by the target role Agile project management knowledge
  • not needed by the target role DevOps knowledge
  • not needed by the target role GIMP (graphics editor software) knowledge
  • not needed by the target role ICT accessibility standards knowledge
  • not needed by the target role ICT project management methodologies knowledge
  • not needed by the target role ICT security legislation knowledge
  • not needed by the target role Microsoft Visio knowledge
  • not needed by the target role Process-based management knowledge
  • not needed by the target role Prototyping development knowledge
  • not needed by the target role Rapid application development knowledge
  • not needed by the target role SketchBook Pro knowledge
  • not needed by the target role Spiral development knowledge
  • not needed by the target role Synfig knowledge
  • not needed by the target role Waterfall development knowledge
  • not needed by the target role World Wide Web Consortium standards knowledge
  • not needed by the target role analyse business requirements skill
  • not needed by the target role application usability knowledge
  • not needed by the target role assess users' interaction with ICT applications skill
  • not needed by the target role augmented reality knowledge
  • not needed by the target role business process modelling knowledge
  • not needed by the target role cognitive psychology knowledge
  • not needed by the target role create website wireframe skill
  • not needed by the target role design graphics skill
  • not needed by the target role design process skill
  • not needed by the target role design user interface skill
  • not needed by the target role draw design sketches skill
  • not needed by the target role graphics editor software knowledge
  • not needed by the target role human-computer interaction knowledge
  • not needed by the target role incremental development knowledge
  • not needed by the target role interact with users to gather requirements skill
  • not needed by the target role interactive media knowledge
  • not needed by the target role iterative development knowledge
  • not needed by the target role lean project management knowledge
  • not needed by the target role manage localisation skill
  • not needed by the target role manage online content skill
  • not needed by the target role natural language processing knowledge
  • not needed by the target role perform online data analysis skill

13 further entries not listed here

29 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 real-time computing required
  • still to learn ICT communications protocols required
  • still to learn embedded systems required
  • still to learn engineering control theory required
  • still to learn signal processing required
  • still to learn system design required
  • still to learn tools for software configuration management required
  • still to learn digital systems required
  • still to learn systems development life-cycle required
  • optional, not held field-programmable gate arrays optional
  • optional, not held Ansible optional
  • optional, not held Apache Maven optional
  • optional, not held ICT network simulation optional
  • optional, not held ICT security standards optional
  • optional, not held ICT system integration optional
  • optional, not held Jenkins (tools for software configuration management) optional
  • optional, not held Microsoft Visual C++ optional
  • optional, not held Puppet (tools for software configuration management) optional
  • optional, not held SPARK optional
  • optional, not held STAF optional
  • optional, not held Salt (tools for software configuration management) optional
  • optional, not held battery management systems optional
  • optional, not held engineering processes optional
  • optional, not held hardware architectures optional
  • optional, not held network management system tools optional
  • optional, not held software components libraries optional
  • optional, not held tools for ICT test automation optional
  • optional, not held hardware components optional
  • optional, not held state estimation optional
Index
FAQ

Common questions about this move

Can a user interface designer become an embedded system designer?

Yes, and it is a substantial move. A user interface designer already covers 45% of what an embedded system designer is expected to do: 42 skills carry over, 4 of which the embedded system designer role treats as required.

What skills does a user interface designer need to become an embedded system designer?

13 required skills are missing, plus 23 optional ones. They fall into 5 areas of the ESCO skill hierarchy, led by information and communication technologies (icts). The single most important is real-time computing.

How hard is the move from user interface designer to embedded system designer?

Its learning distance is 65.6 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.