Field entry, published 2026-11-03T00:00:00.000Z, updated 2026-11-03T00:00:00.000Z. Group: Major Group 2: Professionals

How are ICT professionals classified?

Major groupMajor Group 2: Professionals, ISCO-08, ILO
Skill levelSkill level 4, ISCO-08, ILO
Code ladderMajor Group 2, then sub major group, minor group and unit group in ISCO-08

Classification only, not a job decision

This guide describes ICT professional classification in general terms only. It does not determine any reader's occupation or code.

ICT professionals in ISCO-08 are classified by the kind of information or communications system they design, build, analyse or manage, and by whether their main work requires professional computing judgement. The family covers software development, systems analysis, database and network design, and related work where the core task is to create or shape a computing solution rather than simply operate a tool that someone else built.

What is the core professional task in ICT?

At its heart, ICT professional work involves understanding a problem, designing a system response, building or configuring that response, testing it and improving it. A software developer designs and writes programs to meet a defined need. A systems analyst studies user needs and business processes, then specifies how a system should work. A database professional designs how data are structured, stored and retrieved. A network professional designs how systems connect and communicate securely. In each case, the professional must make choices where trade offs matter: performance against complexity, security against usability, flexibility against cost.

Those choices are what separate professional ICT work from routine ICT use. A person who uses software skillfully for another purpose, such as design, writing or accounting, is classified by that other purpose, not as an ICT professional. Skill with a tool does not make the tool the occupation. The occupation is defined by the system being built or shaped.

How do software, systems and infrastructure roles differ?

Software work centres on programs and applications. The developer or programmer in the professional sense creates, tests and maintains code as a designed solution, not as a series of isolated fixes without a design. Systems work centres on the relationship between people, processes and technology. The analyst translates needs into specifications and evaluates whether a system meets them. Infrastructure work centres on the platforms on which software runs: servers, networks, databases and security arrangements. The professional in this area designs the architecture and the rules by which the infrastructure operates.

These areas overlap in practice. A developer may also design a database. An analyst may also test software. A network professional may also advise on security policy. Classification again follows the main task. If a job is dominated by designing and building applications, software character leads. If it is dominated by analysing needs and specifying systems, systems character leads. If it is dominated by designing and managing infrastructure, infrastructure character leads. A job description that lists every technology touched is less helpful than a clear statement of the dominant design responsibility.

What about support, operations and technician work?

ICT support roles are common and often highly skilled, yet they sit in a different part of the classification when their main task is to help users, install or maintain systems to a specification, or operate equipment under professional direction. A support technician who resolves user problems, installs software and follows troubleshooting procedures is doing valuable associate professional work. A professional who designs the system that the technician supports is doing professional work. The difference lies in who originates the design and who carries professional responsibility for its architecture.

Operations work follows the same logic. Monitoring a system, responding to alerts and carrying out routine maintenance are operational tasks. Designing the monitoring system, deciding how the system should respond to failure and planning capacity for future demand are professional tasks. A single post can contain both, so the balance matters. The question is not whether operations appear at all, but whether they dominate the job or support a design role.

How should a reader approach a fast changing field?

Technology changes quickly, and new titles appear constantly. ISCO-08 classification resists chasing every new title by returning to task and knowledge. A new title for a job that designs and builds software remains software professional work in general terms. A new title for a job that mainly supports users remains support work. A title that combines data, product and engineering language still needs the same test: what system is being designed, what knowledge is indispensable, and what professional judgement is exercised?

Readers should also be careful with product names and programming languages. Knowing a language is a skill, not an occupation. Two developers who use different languages but both design and build applications belong in the same broad professional family, while a person who uses one language only to automate a small part of another job may not belong there at all. Focus on the system, the design task and the responsibility, and the ICT professional family in Major Group 2 becomes a stable map even as tools change. For finer placement, the ILO structure remains the reference, since it refines these broad areas by task in more detail than a general guide can responsibly reproduce.

Sources checked

  1. ILO ISCO-08 structure

Back to the Major Group 2: Professionals group or browse all occupations.