Job Description vs Job Specification: What is the Difference?
A job description outlines what the role involves — duties, responsibilities, reporting structure, and working conditions. A job specification defines who fits the role — the skills, qualifications, experience, and personal attributes a candidate needs. Confusing the two leads to hiring documents that either lack focus or miss critical context. Understanding the distinction helps you write better postings and evaluate candidates more effectively.
All resources Job Description vs Job Specification
What a job description covers
The job description is the external-facing document that tells candidates what the role is and what they will do. It includes the job title, location, a summary of the position, a list of core responsibilities, reporting relationships, working conditions, and compensation. The job description is typically shared with candidates on job boards, your career page, and during the recruitment process. It answers the candidate question: What will I be doing if I take this role?
What a job specification covers
The job specification is the internal document that defines the ideal candidate profile. It lists the minimum qualifications, required skills, educational background, certifications, years of experience, and personal attributes needed to succeed. The job specification is used by hiring managers and recruiters during screening and interview evaluation. It answers the hiring team question: What kind of person do we need for this role?
- Minimum educational qualifications (degree, certifications)
- Required technical skills and competencies
- Minimum years of relevant experience
- Soft skills and personal attributes
- Industry-specific knowledge or training
How the two documents work together
The job description is derived from the job specification. You start by defining who you need (specification), then translate that into what the role involves (description). For example, if the specification requires “5+ years of Python experience,” the description might list “Design and maintain backend services in Python and PostgreSQL” as a core responsibility. The specification is the blueprint; the description is the advertisement. Both should be aligned — if the description promises work the specification does not prepare someone for, or the specification demands skills the description never mentions, there is a mismatch.
Common mistakes when conflating the two
Employers frequently merge these documents, which creates problems on both sides. Listing qualifications in the responsibilities section confuses candidates. Including duties in the screening criteria makes interviews unfocused. Treating preferences as requirements shrinks the talent pool unnecessarily. Keep the documents separate in your process even if you only publish the job description externally.
- Mixing qualifications into the responsibilities section
- Listing every possible skill as a requirement in the description
- Using the description as the sole screening tool
- Forgetting to update the specification as the role evolves
- Ignoring the specification during interview evaluation
When you need both documents
For any role with more than one candidate applying, both documents add value. The job specification ensures the hiring team agrees on what “qualified” means before reviewing applications. The job description ensures candidates understand the role before applying. For very small teams or solo hiring, a combined document can work, but maintaining the distinction in your thinking — what the role does versus who can do it — will always improve your hiring outcomes.
Related resources
Related job descriptions
Frequently asked questions
Can I combine the job description and job specification into one document?
For external postings, you typically only share the job description. The job specification is an internal tool used by the hiring team during screening and interviews. Combining them for external use can overwhelm candidates with too much information and make the posting harder to read.
Which document should I write first?
Start with the job specification. Define who you need — qualifications, skills, experience — then translate that into a job description that describes the role and responsibilities. The specification is the blueprint; the description is the advertisement.
How often should I update the job specification?
Review it whenever the role changes, when market conditions shift, or when you realize your requirements are too narrow or too broad. If you are not getting qualified applicants, the specification may need adjustment. If you are getting unqualified applicants, it may need tightening.
Use InstantJD to create your job description
Generate a scored, editable, hiring-ready job description in minutes — free for verified employers.