Job

Academy synthesis

A reusable definition of a role: what the role is, what it reports to, and its job family. A job can exist with nobody in it.

Why the distinction matters

Jobs are configuration. Positions are employment. Conflating them makes reorganisations change pay and reporting for people who did not move.

Not to be confused with

Position
A position is one instance of a job occupied by one worker on one assignment, with its own location, manager and dates.

Also called

Job definition
Job profile

Synonyms are searchable, so searching either spelling finds this entry.

Worked example

Defining "Payroll Analyst" once as a job, then creating three positions — one in the UK entity, one in Ireland, one covering two cost centres — is the normal pattern. Creating three jobs instead duplicates the role definition and makes reporting by job family wrong.

Illustrative example authored by HCM Studio to show the configuration pattern. It is not taken from a customer implementation.

Evidence

This entry is academy synthesis. It describes how the term is used rather than restating an Oracle definition, so no claim backs it. Where Oracle documents a specific behaviour, that behaviour is recorded as a claim elsewhere in the curriculum.