Field entry, published 2026-11-03T00:00:00.000Z, updated 2026-11-03T00:00:00.000Z. Group: Digital and technology occupations
How are software developers classified in general terms?
| Major group | Major Group 2: Professionals |
|---|---|
| Skill level | 4 |
| Code ladder | General ladder only: major group, then sub-major group, then minor group, then unit group for ICT professionals |
Classification only, not a job decision
This is a general description of a kind of work in a classification. It does not assign any reader to a group or suggest a job change.
In general terms, software developers are classified with ICT professionals when their main work is designing, writing, testing, and maintaining software. The defining activity is the creation of programs that carry out a specified function, whether that function serves a business process, a scientific calculation, a game, or a device. A job counts in this broad family because software creation dominates its duties, not because the employer sells software or because the job title contains the word developer.
That distinction matters because software touches almost every workplace. A person who mainly configures an existing package for users, without designing or building new software, is doing different central work, even if the package is complex. A person who mainly writes reports from data, or mainly answers user questions, is also doing different central work. Classification follows the software building itself, in its full cycle, rather than proximity to software.
What tasks define software development in this broad sense?
The cycle usually begins with understanding what a program must do. Developers may study a specification, clarify requirements with analysts or users, and decide how a program should be structured so that its parts work together. Design choices at this stage shape later work, because they settle how data will move, how errors will be handled, and how the program will be maintained.
Writing code is the most visible part, but testing and revision belong to the same centre. Developers test programs against expected behaviour, trace faults, and revise code so that it runs reliably. They may also write documentation that explains how a program works, review the work of colleagues, and adapt existing programs when requirements change. Maintenance is therefore not a separate world from development. Adapting, improving, and correcting software over time is part of keeping a program fit for its purpose.
Some developers work mainly on applications that people use directly, while others work mainly on the underlying systems that support those applications, such as operating systems or tools used by other developers. That difference reflects specialisation within software work. It does not, on its own, move a job out of the professional software family, provided that building software remains the main activity.
How does this family relate to neighbouring work?
Systems analysts often work close to developers, and the two kinds of work can overlap in a single team. The general difference lies in emphasis. Analysis centres on studying a problem, defining requirements, and designing a system in broad terms, while development centres on turning that design into working software and keeping it working. A job that moves between the two still needs a judgement about which emphasis defines it, based on its main duties rather than on team labels.
Database and network specialists are neighbours in a different sense. Their central specialisations are data structures and connectivity, rather than software creation as such. A developer who also looks after a database may still belong in the software family when software building dominates, just as a database specialist who writes some code may still belong with data work when data design dominates. Overlap in daily tasks does not erase the distinction between specialisations.
Management is another neighbour to keep in view. Leading a development team, setting priorities, and reporting on progress can sit alongside coding, but a job becomes managerial in classification terms only when managing is its main work. Technical leadership that stays centred on software design and review is different from a job whose centre has shifted to people, budgets, and strategy.
What does not change the broad grouping?
Programming language, by itself, does not change the grouping. Languages come and go, and a developer may use several in one project, yet the kind of work remains software creation. The sector of the employer does not change it either. Software built for health care, finance, education, or transport remains software work when building software is the main duty, even though knowledge of the sector helps the developer understand requirements.
Seniority words in a title also do not settle the matter. Junior, senior, lead, and principal can mean different things in different organisations, and they can reflect pay, experience, or internal hierarchy rather than a change in the kind of work performed. A more senior developer may still be doing professional software work, with greater complexity and responsibility, while a job that has moved mainly into management has changed in kind, not merely in seniority.
In short, software developers sit with ICT professionals in general terms because their work centres on creating and sustaining software at professional depth. The test is always the main tasks, the complexity of those tasks, and the field of knowledge they require, rather than the language, the sector, or the title attached to the job.
Sources checked
Back to the Digital and technology occupations group or browse all occupations.