Field entry, published 2026-11-03T00:00:00.000Z, updated 2026-11-03T00:00:00.000Z. Group: Digital and technology occupations
How are database professionals 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 guide describes database work as a classification family. It does not decide the group for any particular job or reader.
Database professionals are classified in general terms with ICT professionals when their main work is designing, building, administering, and safeguarding databases and the structures that hold an organisation’s data. Their specialisation is data itself: how it is modelled, stored, retrieved, kept consistent, and protected over time. A database that is well designed lets many different applications use the same data without duplicating it in incompatible forms, and that design task is the heart of the family.
This family is easy to confuse with neighbouring work because almost every digital job touches data. Using a database to enter records, run a report, or look up a customer is not database professional work. The professional family is defined by responsibility for the database as a system, rather than by use of a database as a tool for another occupation.
What tasks sit at the centre of database work?
Design comes first in a logical sense, even when a job also spends time on operation. Database professionals analyse what data an organisation needs, how different pieces of data relate, and what rules should govern them. They may create data models that show entities, relationships, and constraints, and they may choose structures that balance speed of retrieval, ease of updating, and integrity. A model that looks tidy on paper but fails when data grows or changes is a poor design, so professional judgement includes thinking about future use.
Building and administering follow design. Professionals may create databases, define access controls, set up backup and recovery arrangements, and monitor performance so that queries run efficiently and data remains available. They may tune a database, reorganise storage, or migrate data when a system changes. Security is part of this work in a practical sense, because access controls, permissions, and audit arrangements decide who can see or change data, and under what conditions.
Advice and problem solving complete the picture. Database professionals may advise developers on how to query data efficiently, advise managers on data quality, and investigate problems when data appears inconsistent or a system slows down. Their explanations often need to connect a technical cause, such as a missing index or a flawed constraint, to a visible effect, such as a report that cannot be trusted or a transaction that fails.
How does database work differ from software and systems work?
Software developers may write code that reads and writes data, and systems analysts may design a system that includes a database, yet neither focus makes a job a database job on its own. The distinguishing question is which specialisation dominates. When the defining work is the database structure, its integrity, its performance, and its protection, the database family is the broad home. When the defining work is creating applications, the software family is the broad home, even if the developer understands databases well.
A similar point applies to data analysis in a statistical or business sense. A person who mainly analyses data to answer business questions, build forecasts, or present findings is doing analytical work whose centre is interpretation, not database design and administration. Database professionals support that analysis by making data available, reliable, and well structured, but supporting analysis is not the same as performing it as the main duty.
Clerical data work sits further away. Entering data, checking forms, and maintaining routine records are important duties, yet they centre on handling data within a system that someone else designed and administers. Professional database work centres on the system itself, including its design and its continuing health, and that difference in centre and complexity is what places the families at different skill levels.
What marks the professional level in this field?
Professional database work typically calls for a broad and deep knowledge of data modelling, database systems, query languages, and the principles that keep data consistent and secure. Professionals are expected to make decisions that affect many users and many applications at once, because a change to a shared database can ripple far beyond one team. They must also anticipate failure, planning for recovery when hardware fails, software changes, or human error corrupts data.
That breadth of consequence is a useful test. A job that only maintains one small, self contained store under close direction, without design responsibility, may lean toward technical support work. A job that designs shared structures, sets access policy, and carries responsibility for integrity and recovery across an organisation leans toward the professional family. As always, the judgement rests on main duties, not on the size of the database or the fame of the product used to manage it.
In general terms, then, database professionals belong with ICT professionals because their work is the design, administration, and protection of data systems at professional depth. The data is the specialisation, the database is the system, and the professional level reflects the judgement needed to keep that system trustworthy for everyone who depends on it.
Sources checked
Back to the Digital and technology occupations group or browse all occupations.