Job analysis

Job analysis is the structured study of a role: what the work actually involves, under what conditions, and what a person needs in order to do it well. It is research about the job, not about whoever currently holds it, and it produces the raw material that job descriptions, pay grades and interview scorecards are all built from.

Skipping it is why so many hiring processes go wrong quietly. A role that was never analysed gets a description copied from somewhere else, a level assigned by feel, and a salary set by whatever the last person earned.

Job analysis, job description and job evaluation

These three are constantly confused and they run in sequence:

• Job analysis gathers the facts about the work.
• The job description is the document those facts are written into.
• Job evaluation then compares that role to others to decide its relative worth, which feeds grading and job classification.

Run them out of order and you end up evaluating a description of work nobody verified.

Methods

Most analyses combine three or four of these:

• Interviews with the people doing the job and with their manager, separately. The two accounts rarely match, and the gap is itself useful information.
• Observation of the work as it happens, which catches the routine steps nobody bothers to mention.
• Questionnaires across several holders of the same role, useful when the role exists in multiple teams or locations.
• Task and output analysis: what is produced, how often, to what standard, and what happens when it is late or wrong.
• Critical incidents: examples of the job done exceptionally well and exceptionally badly, which reveal what really separates performance levels.

What it produces

A complete analysis answers five questions: the core duties and how time is split across them; the knowledge, skills and abilities required, separated into what must be present on day one and what can be learned; the behavioural competencies that distinguish good performance; the level and reporting line; and the working conditions, including tools, physical setting and any legal requirements. That output feeds straight into competency mapping and into a defensible salary band via salary benchmarking.

Where it gets used

• Hiring. The scorecard for a structured interview should come from the analysis, not from the interviewer's intuition about the vacancy.
• Pay. Grading and internal equity rest on comparable descriptions of comparable work.
• Development. A training needs analysis and any skills gap assessment need a baseline of what the role requires.
• Org design. Workforce planning and redesigning overlapping roles depend on knowing where duties actually sit, which is often not what the org chart implies.

How to run one

1. Define the scope: one role, or a family of similar roles across teams.
2. Collect from at least two sources, one of which is the person doing the work.
3. Write the duties as observable outputs rather than activities. "Closes the monthly reporting cycle by the third working day" beats "responsible for reporting".
4. Separate requirements into essential and desirable, and justify every essential one. Most inflated requirements die at this step.
5. Have the manager and a current holder review the draft, then attach it to the level and pay band.
6. Revisit when the role changes materially, not on a fixed calendar.

Common mistakes

The most frequent error is analysing the person instead of the job, which produces a description that fits exactly one human being and becomes unusable the moment they leave. Close behind: inflating requirements to make the role sound senior, which narrows the candidate pool for no gain; and treating the analysis as a one-time document, so that after two years the written role and the real one have nothing in common.

Job analysis in PeopleForce

In Recruit, the vacancy request is where an analysis becomes a decision. The request captures the job title, employment type, department, division, location, legal entity, job description, seniority, position, number of openings, start date, priority, salary, skills and tags, and then routes the whole thing through approval, so the level and the budget are agreed before the role is published rather than after a candidate has been promised something.

The competency side lives in Perform, where competency models and company values are defined once and then reused in review cycles, so the requirements written during the analysis are the same ones people are later assessed against. Core HR holds the structural context around it: positions, divisions, reporting lines and an org chart by people or by department, which is usually where duplicated duties across two roles become visible.