Field entry, published 2026-11-03, updated 2026-11-03. Group: Job, occupation, and unit group

How do employers and statisticians read the same job differently?

Employers and statisticians read the same job differently because they need different things from it. An employer needs to fill a post, manage a team, set pay, and get work done inside one organisation. A statistician needs to compare that job with similar jobs in other organisations, regions, and countries, using a shared vocabulary. Both readings are legitimate, and neither is a mistake. They simply serve different purposes, and confusion arises when one reading is used for the other’s job.

What does an employer see first?

An employer sees a post inside a structure: a team, a manager, a budget, a set of local priorities, and a history of who held the role before. The job description will reflect local needs, such as covering a particular client group, using a particular system, or working particular shifts. Pay and seniority will reflect internal relativities: how this post compares with neighbouring posts in the same firm, not how it compares with similar work elsewhere. A title will often be chosen to fit that internal structure, to signal rank, or to attract candidates in a local labour market.

What does a statistician see first?

A statistician sees a bundle of main tasks that can be matched to a task profile in a classification. Local details that do not change the nature of the work are set aside, while the defining tasks, purpose, and knowledge are brought forward. The job is then placed in a unit group, inside a minor group, inside a sub-major group, inside a major group, so that it can be counted alongside similar jobs elsewhere. The statistician is not interested in the internal rank of the post, the local pay band, or the branding of the title, except where those facts shed light on the tasks. The goal is comparability: the same kind of work counted the same way, wherever it is done.

Where do the two readings collide?

They collide most visibly over titles and seniority. An employer may call a role a manager because the holder coordinates a small team or owns a process, while a statistician, looking at main tasks, may place the job with direct service or production work, because management tasks are only a small share. Neither party is wrong in its own terms. The employer is describing internal responsibility, and the statistician is describing task balance for comparison. A collision also occurs over scope: an employer may combine several kinds of work into one post for practical reasons, while a statistician must still choose the single family that best fits the main tasks. The combined post is real, and the single grouping is a necessary simplification for counting.

How can the same job be described well for both audiences?

A good job description serves both audiences by separating layers. It can state the local context, team, and reporting line for internal use, and it can state the main tasks, purpose, and knowledge in plain language for external comparison. When those layers are mixed, readers mistake internal rank for task content, or local system names for the nature of the work. A description that leads with main tasks, then adds local context as a second layer, is easier to code and easier to understand. It also ages better, because tasks change more slowly than internal structures and title fashions.

Why should workers understand both readings?

Workers live in both worlds. Inside an organisation, their title, team, and pay band shape daily life. Outside it, their occupation family shapes how their experience is understood by other employers, advisers, and researchers. A worker who understands both can translate between them: explaining a grand sounding internal title in terms of main tasks when applying elsewhere, or explaining a statistical grouping in terms of local duties when discussing a role internally. That translation skill matters especially when changing jobs, because a new employer will read past experience through tasks, not through the old firm’s internal labels.

What happens when only one reading is used?

Using only the employer reading for statistics would produce counts driven by title fashion and internal structures, which vary too much for comparison. Using only the statistical reading for management would produce job descriptions stripped of local context, team relationships, and accountability, which are essential for running a workplace. Each reading fails when stretched beyond its purpose. The healthy arrangement is to keep both, clearly labelled: internal descriptions for managing work, and task based classification for comparing work. When a report, advert, or profile moves between those worlds, it should say which reading it is using, so readers do not mistake one for the other.

How can you tell which reading a document is using?

Look for its unit and its language. A document organised by teams, reporting lines, pay bands, and internal grades is speaking as an employer. A document organised by task profiles, unit groups, and broad families is speaking as a statistician. A document that lists a title without tasks is leaning on the employer reading, while a document that lists main tasks before titles is leaning on the statistical reading. Spotting that difference prevents many misunderstandings.

Sources checked

1. ILO: ISCO-08 structure

Back to the Job, occupation, and unit group group or browse all occupations.