Job Description vs. Job Specification — What's the Difference?

If you've spent time in HR, you've encountered both terms. If you're a job seeker, you've probably seen "job description" and "job specification" used interchangeably — and sometimes they are, in practice. But formally, they describe different things, and understanding the distinction helps you read any job posting more effectively.

What a Job Description Contains

A job description defines the role itself — what the job is and what the job does. Formally, it covers:

• Job title and reporting structure — what the role is called and where it sits in the organization
• Summary or purpose of the role — why this job exists and what it contributes
• Key responsibilities — the main functions and tasks the person in the role performs
• Working conditions — location, hours, physical demands, travel requirements
• Performance standards — how success is measured in the role

The job description is written from the perspective of the role itself. It answers: what does this job do?

What a Job Specification Contains

A job specification defines the person for the role — the qualifications, skills, and characteristics a candidate must or should have. It covers:

• Education requirements — minimum degree, field of study, or equivalent
• Experience requirements — years of experience, type of experience, industry background
• Technical skills — specific tools, systems, languages, certifications
• Soft skills — communication, leadership, problem-solving, interpersonal abilities
• Physical requirements — if relevant (standing, lifting, travel frequency)
• Personal attributes — traits like adaptability, attention to detail, cultural fit requirements

The job specification is written from the perspective of the ideal candidate. It answers: who should do this job?

Sell Custom Apparel — We Handle Printing & Free Shipping

How They Blend Together in Real Job Postings

In formal HR management, job descriptions and job specifications are separate documents. In practice — particularly in the public job postings you apply to — they're almost always combined into a single posting.

The typical structure you see on LinkedIn or Indeed is:

• Job title (description)
• "About the company" or "About the role" section (description)
• "Responsibilities" section (description)
• "Requirements" or "Qualifications" section (specification)
• "Preferred qualifications" or "Nice to have" section (specification)
• Compensation and benefits (often missing, but description if included)

When job seekers talk about "reading the job description," they usually mean this full combined document. Both components matter for your application: responsibilities tell you what you'd actually do (and help you identify implied skills), and requirements tell you what you need to bring.

Which Part Matters Most for Your Application

For ATS optimization: the specification (requirements section) is what ATS systems primarily scan for keyword matches. Your resume's skills section and work history should reflect the terminology from the requirements.

For interview preparation: the description (responsibilities section) is what tells you what you'd actually be doing. Prepare specific examples from your history that demonstrate you've done analogous work.

For red flag detection: both sections matter, but the specification often contains the more actionable signals. Unrealistic requirements, degree inflation, and years-of-experience gaps appear in the specification. Culture warning phrases often appear in the description.

The Coyote Job Description Analyzer processes both sections and extracts signals from the full document — not just the requirements list.

For HR Professionals: Writing Better Combined Postings

If you're on the hiring side, keeping the description and specification components conceptually separate helps you write better postings:

Write the description first — Before listing requirements, be specific about what this person will actually do. Day 1-90 activities, recurring tasks, key deliverables. Specificity in the description attracts better-fit candidates and reduces mismatched applications.

Derive the specification from the description — What skills does someone actually need to do each responsibility? List those as required. What would make the job easier but isn't essential? List those as preferred. This prevents requirement inflation.

Review for hidden barriers — Once you have a draft specification, check each requirement: is it genuinely essential, or is it a proxy for something else? Degree requirements that are proxies for "professional communication skills" often screen out qualified candidates unnecessarily.

You can use the analyzer on your own job descriptions to see what signals you're sending to candidates — including any red flag language that might reduce application quality.

Frequently Asked Questions

Do all companies write formal job specifications?

Most larger companies have internal job specifications in their HR systems even if they don't publish them separately. What you see as a job seeker is usually the combined document. Smaller companies often write ad hoc postings without formal underlying documents.

Which part of the job posting should I focus on for my resume?

Both. The responsibilities section tells you what you'll be doing — your resume should show you've done comparable work. The requirements section tells you what skills to emphasize and what terminology to use. The requirements section is more directly relevant for ATS optimization.

Is a person specification different from a job specification?

In some HR frameworks, particularly in the UK, a "person specification" specifically describes the ideal candidate (skills, experience, attributes), while a "job description" describes the role and responsibilities. This is essentially the same distinction as job description vs. job specification in US terminology.