Electrical engineer — skills, knowledge and links

How it connects#

O*NET also lists (no page here yet): Electronics Engineers, Except Computer · Electrical and Electronic Engineering Technologists and Technicians · Electrical and Electronics Repairers, Commercial and Industrial Equipment · Mechanical Engineering Technologists and Technicians · Electrical and Electronics Repairers, Powerhouse, Substation, and Relay · Mechatronics Engineers · Solar Energy Systems Engineers · Microsystems Engineers

In the official classification#

In Europe, internationally and in Singapore

What O*NET rates highest#

From O*NET 17-2071.00 (Electrical Engineers). Ordered by O*NET's importance rating; the words are O*NET's own scale anchors.

Each task in O*NET's terms#

O*NET describes work as detailed activities. Each of this page's 5 tasks is matched only against the activities O*NET lists for this occupation, with a stated fit; 5 match at least one. The alignment and its fit are this site's judgement, made task by task by its AI agent (Claude) on 2026-09-26; O*NET does not align tasks like ours. The activity names are O*NET's, the translations ours.

• Requirements and system design
  Analyze design requirements for computer or electronics systems.the closest O*NET has, not the same · Analyzing Data or Information · O*NET 31.0
  Determine operational criteria or specifications.covers part of this task · Drafting, Laying Out, and Specifying Technical Devices, Parts, and Equipment · O*NET 31.0
• Circuit, board and chip design
  Create schematic drawings for electronics.the closest O*NET has, not the same · Thinking Creatively · O*NET 31.0
  Design electronic or computer equipment or instrumentation.covers part of this task · Drafting, Laying Out, and Specifying Technical Devices, Parts, and Equipment · O*NET 31.0
  Create electrical schematics.covers part of this task · Thinking Creatively · O*NET 31.0
• Power studies and grid interconnection
  Design electrical equipment or systems.the closest O*NET has, not the same · Drafting, Laying Out, and Specifying Technical Devices, Parts, and Equipment · O*NET 31.0
• Testing, commissioning and faults
  Test products for functionality or quality.the closest O*NET has, not the same · Inspecting Equipment, Structures, or Materials · O*NET 31.0
  Investigate system, equipment, or product failures.covers part of this task · Getting Information · O*NET 31.0The same activity in: Mechanical engineer
• Codes and signing off installations
  Communicate technical information to suppliers, contractors, or regulatory agencies.the closest O*NET has, not the same · Coordinating the Work and Activities of Others · O*NET 31.0

Rules that bind this work#

Laws, regulations, court rules, regulators' guidance and collective agreements that this page's verified records read — each with the verb that matters and whom it binds. Read from each record by this site's AI agent (Claude) on 2026-09-26. Official names stay in their own language.

Our task judgements#

Sources and rules#

• Each block says where it comes from: this site's own judgements, O*NET, the U.S. Department of Education's CIP–SOC crosswalk, the European ESCO classification and its official crosswalk to O*NET, the ILO's ISCO-08, Singapore's SSOC 2024, or something computed mechanically from those. Nothing on this page is a rating we made up.
• O*NET's importance ratings are used only to order and shorten the lists. They are never combined with this site's impact index or evidence counts.
• The fit between our page and an O*NET occupation is our judgement and is stated per code: same job, broader, part of it, or only the closest there is.
• The ESCO and ISCO-08 fits are derived mechanically from the official ESCO–O*NET crosswalk; where we override it, we say why in our data (for example, the crosswalk pairs radiologists with radiographers, which is a different job). The SSOC 2024 fit is our reading of the Singapore Department of Statistics' own titles and definitions. Official names are shown as their publishers write them; we do not translate them.
• Each task is matched only against the detailed work activities O*NET lists for the codes this page maps to. Where nothing fits, the page says why instead of forcing a match: work O*NET does not describe yet (used only for tasks we judge to be emerging), or nothing in O*NET's list for this occupation. An alignment never changes a task's direction, its basis or the impact index.
• Rules are read only from this site's verified records. A rule's official name must appear word for word in a record that reads it, so no name is made up; a policy mandate is read only as 'must', 'must not' or 'funds', because 'should' and 'in principle' are not a mandate. Reading a rule never changes a task's direction, its basis or the impact index.
• How these pieces fit together — objects, links and the actions that change them — is drawn as one diagram: The VOLO ontology
• ESCO (European Commission), occupation records from the ESCO API; CC BY 4.0. ESCO–O*NET crosswalk, ESCO Secretariat with the U.S. Department of Labor/ETA, version 1 (Sep 2022), O*NET-SOC 2019 ↔ ESCO v1.1.0; CC BY 4.0. Singapore Department of Statistics, Singapore Standard Occupational Classification 2024 and its correspondence with ISCO-08.
• O*NET 31.0 Database, August 2026 release, U.S. Department of Labor/Employment and Training Administration, CC BY 4.0. O*NET® is a trademark of USDOL/ETA. The translations of O*NET descriptors on this page are ours, not O*NET's.