How to Write an Effective Job Description

A job description is one of the most useful documents in an organisation’s HR system.

It explains what a position exists to achieve, what responsibilities the employee is expected to perform and what knowledge, skills and experience are required.

A well-written job description can support recruitment, onboarding, performance management, training and organisational planning.

A poorly written job description can create confusion from the beginning. Employees may not understand what is expected of them, managers may struggle to assess performance and recruitment teams may attract candidates who are unsuitable for the position.

A job description should therefore be more than a list of tasks.

It should provide a clear picture of the role and its contribution to the organisation.

What Is a Job Description?

A job description is a document that explains the main purpose, responsibilities and requirements of a position.

It describes the role, rather than the individual currently occupying it.

A typical job description may contain:

• Job title;
• Department;
• Reporting relationship;
• Job purpose;
• Key responsibilities;
• Required qualifications;
• Required experience;
• Skills and competencies;
• Working environment; and
• Performance expectations.

The exact format can differ between organisations.

Why Are Job Descriptions Important?

A job description can support several areas of HR.

Recruitment

Recruiters can use the document to determine what type of candidate is required.

Selection

Interviewers can assess candidates against the requirements of the position.

Onboarding

New employees can use the job description to understand their responsibilities.

Performance Management

Managers can use the role’s responsibilities and expected outcomes when discussing performance.

Training and Development

The organisation can identify gaps between the skills required by the role and the employee’s current capabilities.

Workforce Planning

Job descriptions can help HR understand the skills and capabilities available within the organisation.

Job Description vs Job Specification

These terms are sometimes confused.

A job description focuses primarily on the position and its responsibilities.

A job specification focuses on the characteristics required from the person performing the role.

For example:

Job description:
Responsible for processing monthly payroll and maintaining accurate payroll records.

Job specification:
Requires payroll experience, attention to detail and knowledge of payroll systems.

Both can be included in one document.

Start With the Purpose of the Role

The job purpose should explain why the position exists.

A useful purpose statement should answer:

Why does this job exist?

For example:

To provide accurate and timely payroll administration while supporting employees and management with payroll-related queries.

This is more useful than simply writing:

Responsible for payroll.

The first statement explains the broader purpose of the position.

Keep the Job Purpose Concise

The purpose statement does not need to be several paragraphs long.

One or two clear sentences are often sufficient.

A good job purpose should help someone unfamiliar with the organisation understand the role.

Define the Key Responsibilities

The responsibilities section should explain the major areas of work.

For example, an HR Officer may have responsibilities relating to:

• Employee records;
• Recruitment administration;
• Leave administration;
• Employee relations;
• HR reporting;
• Payroll inputs;
• Training administration; and
• HR compliance support.

The responsibilities should reflect the actual work performed.

Avoid Creating a Task List

A job description should not necessarily contain every minor task performed by an employee.

For example, instead of listing:

• Open emails;
• Answer telephone;
• File documents;
• Send emails;
• Print documents;
• Attend meetings;

a better description may group related activities:

Provide effective administrative support to the HR function, including maintaining employee records, processing documentation and responding to routine HR queries.

This makes the document easier to maintain.

Use Clear Language

Job descriptions should be easy to understand.

Avoid unnecessary jargon and complicated wording.

For example:

Instead of:

Facilitate the optimisation of organisational human-capital administrative deliverables.

Use:

Maintain accurate employee records and provide timely HR administration.

Clear language makes expectations easier to understand.

Distinguish Responsibilities From Outcomes

A responsibility describes what the employee does.

An outcome describes what the organisation expects that work to achieve.

For example:

Responsibility:

Manage recruitment administration.

Expected outcome:

Recruitment documentation is processed accurately and vacancies progress within agreed timelines.

Including outcomes can make a job description significantly more useful for performance management.

Include Reporting Lines

The job description should normally indicate who the employee reports to.

Depending on the organisation, it may also identify:

• Direct reports;
• Functional reporting relationships;
• Key internal stakeholders; and
• Key external stakeholders.

This helps establish accountability.

Identify Decision-Making Responsibilities

Some roles require significant decision-making authority.

Others primarily execute established processes.

A job description should provide an appropriate indication of the employee’s level of authority.

For example:

Approves departmental expenditure within the approved delegation.

This is different from:

Recommends expenditure for management approval.

The distinction matters.

Include Qualifications Carefully

Qualifications should be relevant to the position.

For example, a position requiring professional accounting knowledge may reasonably require an accounting qualification.

However, employers should avoid adding qualifications simply because they sound impressive.

Unnecessary requirements can reduce the number of potentially suitable candidates.

The question should always be:

Is this qualification genuinely relevant to performing the job?

Define Experience Requirements

Experience requirements should also be realistic.

A job description might specify:

Two to three years’ relevant HR administration experience.

This is more useful than:

Must have extensive experience.

Where experience is not essential, employers should consider whether it should be listed as a requirement at all.

Skills and Competencies

A good job description can identify the skills required to perform the role.

These may include:

• Communication;
• Problem-solving;
• Planning;
• Computer literacy;
• Technical skills;
• Customer service;
• Leadership;
• Analytical thinking; and
• Attention to detail.

The competencies should reflect the actual role.

Technical Skills vs Behavioural Competencies

These are different.

Technical Skills

These relate to what the employee needs to know or be able to do.

Examples include:

• Payroll processing;
• Financial reporting;
• Programming;
• Machine operation;
• Data analysis; or
• HR administration.

Behavioural Competencies

These relate to how the employee applies their skills.

Examples include:

• Communication;
• Teamwork;
• Accountability;
• Adaptability;
• Problem-solving; and
• Professionalism.

A strong job description can include both.

Include Key Performance Areas

For some roles, it is useful to identify key performance areas.

For example, an HR Business Partner might have:

Employee Relations

People Analytics

Talent Management

Performance Management

HR Strategy

These areas provide a useful foundation for later performance discussions.

Job Descriptions and KPIs

A job description should not necessarily contain every KPI.

However, it should provide enough information to establish what the employee is responsible for.

KPIs can then be developed from those responsibilities.

For example:

Job responsibility:

Manage recruitment processes.

Possible KPI:

Average vacancy turnaround time within the agreed recruitment target.

The job description establishes the responsibility while the KPI measures performance.

Job Grade and Level

Some organisations include the job grade or level.

For example:

• Grade 5;
• Management Level;
• Specialist Level;
• Entry Level; or
• Executive Level.

This can help establish the position within the organisation’s structure.

Where job grading is used, the grading should be consistent with the organisation’s broader job-evaluation framework.

Salary Information

A job description does not always need to contain the employee’s actual salary.

Remuneration can be managed separately through employment documentation and the organisation’s remuneration structure.

However, the job’s level and grading may be relevant to remuneration decisions.

Physical and Working Requirements

Some positions have specific working requirements.

For example:

• Standing for extended periods;
• Working shifts;
• Travelling;
• Working outdoors;
• Operating machinery; or
• Working at different locations.

These requirements should be accurately described where relevant.

Remote and Hybrid Roles

Job descriptions for remote or hybrid positions should explain the nature of the working arrangement where appropriate.

The document may indicate:

• Remote;
• Office-based;
• Hybrid;
• Client-site based; or
• Travel requirements.

Clear expectations can prevent misunderstandings later.

Avoid Gendered Job Descriptions

Job descriptions should focus on the requirements of the position.

Employers should be careful about wording that unnecessarily suggests that a particular gender is preferred.

For example, phrases such as:

“Looking for a young energetic lady”

may create unnecessary discrimination concerns.

A more appropriate approach is to describe the actual requirements:

“The role requires strong communication skills and the ability to work effectively in a fast-paced environment.”

Avoid Unnecessary Age Requirements

Age should not normally be used as a recruitment requirement unless there is a legitimate and lawful reason.

Instead of:

Must be under 30.

the employer should identify the actual requirement.

For example:

Requires the ability to work rotating shifts.

The focus should be on the job rather than assumptions about the candidate.

Job Descriptions and Organisational Structure

Job descriptions should make sense within the organisation’s structure.

For example:

HR Manager

↓

HR Business Partner

↓

HR Officer

↓

HR Administrator

Each role should have clearly differentiated responsibilities.

If every job description contains the same responsibilities, employees may struggle to understand accountability.

Avoid Excessive Responsibilities

A job description containing fifty unrelated responsibilities may indicate that the role has not been properly defined.

For example, combining:

• HR;
• Payroll;
• IT;
• Marketing;
• Procurement;
• Reception; and
• Finance

into one position may create an unrealistic role unless the organisation genuinely requires such a broad position.

A job description should reflect the actual structure and needs of the business.

Review Job Descriptions Regularly

Jobs can change.

Technology, organisational structures, legislation and business requirements can all affect what employees do.

Job descriptions should therefore be reviewed periodically.

A review may be appropriate when:

• An employee is promoted;
• Responsibilities significantly change;
• A department is restructured;
• New technology is introduced;
• The organisation expands; or
• A vacancy is being advertised.

Job Description Changes

A manager should not simply add significant new responsibilities without considering the implications for the employee and employment relationship.

Where a substantial change occurs, HR should assess whether:

• The job description needs updating;
• The employee’s KPIs need changing;
• Training is required;
• Job grading should be reviewed; or
• Contractual issues need to be considered.

Who Should Write the Job Description?

HR can coordinate the process, but the hiring manager should provide substantial input.

The manager understands the operational requirements of the position.

HR can then help ensure that the document is:

• Clear;
• Consistent;
• Structured;
• Appropriate for recruitment; and
• Aligned with the organisation’s HR practices.

When Should a Job Description Be Created?

Ideally, the job description should exist before recruitment begins.

This allows the organisation to define the position before advertising it.

Creating the job description after an employee has already been hired can result in expectations being established too late.

Job Description Template Structure

A simple structure can include:

Position Details

Job Title:
Department:
Reports To:
Location:
Employment Type:

Job Purpose

A short explanation of why the position exists.

Key Responsibilities

The major areas of work associated with the role.

Required Qualifications

Relevant educational or professional requirements.

Required Experience

Relevant previous experience.

Technical Skills

Role-specific knowledge and capabilities.

Behavioural Competencies

The behaviours required to perform effectively.

Key Performance Areas

The main areas against which performance may be evaluated.

Working Requirements

Relevant hours, travel, shift or workplace requirements.

Review

Date on which the job description should next be reviewed.

Common Job Description Mistakes

Copying an old job description

The document may no longer reflect the actual role.

Listing every minor task

This makes the document unnecessarily long and difficult to use.

Using vague language

Employees need clear expectations.

Adding unnecessary qualifications

Requirements should have a genuine connection to the job.

Ignoring performance outcomes

Responsibilities should ideally connect with measurable results.

Failing to update the document

A role can change significantly over time.

Making the document about the employee

A job description should describe the position rather than the personality of the current employee.

Giving every role identical responsibilities

Different levels should have appropriately differentiated accountability.

Job Description Review Checklist

Before approving a job description, HR and management can ask:

☐ Is the job title accurate?

☐ Is the purpose of the role clear?

☐ Are the main responsibilities included?

☐ Are unnecessary tasks excluded?

☐ Is the reporting line clear?

☐ Are decision-making responsibilities appropriate?

☐ Are qualification requirements genuinely necessary?

☐ Are experience requirements realistic?

☐ Are technical skills identified?

☐ Are behavioural competencies relevant?

☐ Are working requirements clear?

☐ Can the responsibilities support performance management?

☐ Does the role fit within the organisational structure?

☐ Has the document been reviewed recently?

Final Thoughts

A job description is a basic HR document, but its value extends far beyond recruitment.

It can help an organisation define accountability, establish expectations, support performance management and identify development needs.

The best job descriptions are clear without being unnecessarily complicated.

They describe what the role exists to achieve, what responsibilities sit within it and what capabilities are required.

A job description should also evolve as the organisation changes.

When properly maintained, it becomes a useful reference for HR, managers and employees throughout the employment relationship.

A good job description ultimately answers three important questions:

Why does this position exist?

What is the employee responsible for?

What does successful performance look like?

If those three questions can be answered clearly, the organisation has a strong foundation for managing the role effectively.

Frequently Asked Questions

What is the purpose of a job description?

A job description explains the purpose, responsibilities, requirements and expectations associated with a position.

Who should create a job description?

HR can coordinate the process, but the relevant manager should provide input because they understand the operational requirements of the role.

Should every employee have a job description?

Maintaining job descriptions for positions across the organisation can improve clarity, consistency and HR administration.

How often should job descriptions be reviewed?

There is no single review period that applies to every organisation. They should be reviewed when roles change and periodically to ensure that they remain accurate.

Should salary be included in a job description?

Not necessarily. Salary and remuneration can be managed through the employment contract and remuneration structure.

Should KPIs be included?

Key performance areas can be included, but detailed KPIs may be managed separately through the organisation’s performance-management process.

Can an employer change an employee’s job description?

Job responsibilities can evolve, but significant changes should be assessed carefully, particularly where they materially change the nature of the position or employment arrangement.

What is the difference between a job description and a job specification?

A job description focuses on the position and its responsibilities, while a job specification focuses on the qualifications, experience, skills and competencies required from the person performing the role.

Disclaimer

This article is provided for general informational and educational purposes and does not constitute legal advice. Employment practices and requirements depend on the circumstances of the organisation, applicable legislation, employment contracts and workplace policies. Employers should obtain appropriate professional or legal advice where a matter is complex or may have significant employment or compliance consequences.

Devhulon Business & People Solutions provides HR consulting and people-management support to businesses seeking practical assistance with HR strategy, recruitment, employee relations, performance management, employment documentation and broader people-management processes.