Job Specification
A document that details the qualifications, skills, experience, education, and personal attributes required for a person to perform a specific job successfully.
What Is a Job Specification?
Key Takeaways
- ✓A job specification (also called a person specification) details the qualifications, skills, experience, and attributes a person needs to perform a job successfully.
- ✓It differs from a job description: the description focuses on the role (tasks and duties), while the specification focuses on the person (required capabilities).
- ✓78% of employers report that well-defined job specifications improve hiring accuracy by giving interviewers clear evaluation criteria (SHRM, 2023).
- ✓Overly inflated specifications (15+ requirements) reduce female applicants by 50% compared to concise specs with 5 to 6 essentials (Hewlett Packard research).
- ✓42% of new hires fail within 18 months, primarily due to poor fit between the person and the role's actual requirements (Leadership IQ, 2023).
A job specification is the "person" side of a job's documentation. While a job description answers "What does this role involve?", a job specification answers "What kind of person can do this role well?" It lists the education, experience, technical skills, soft skills, certifications, physical requirements, and personal attributes needed for success. Specifications serve a critical purpose: they translate the job's demands into measurable candidate criteria. Without them, hiring becomes subjective. Interviewers evaluate candidates based on gut feel rather than defined competencies. That leads to inconsistent hiring decisions, bias, and the 42% failure rate that Leadership IQ documented in their study of 20,000 new hires. A good specification draws a clear line between essential requirements (must-haves without which the person can't do the job) and desirable attributes (nice-to-haves that would make them more effective). This distinction matters legally, ethically, and practically.
Job specification vs job description
A job description lists what the job involves: tasks, responsibilities, reporting lines, working conditions, and expected outcomes. A job specification lists what the person needs: qualifications, skills, experience, and traits. The description is about the work. The specification is about the worker. In practice, many organizations combine them into a single document. That's fine, as long as both elements are present. The risk of combining them is blurring the line between job requirements and person requirements. A task like "manages a $2M annual budget" (description) requires a skill like "financial planning and budget management experience" (specification). Both need to be stated explicitly.
Legal implications of job specifications
Job specifications have direct legal significance. Every requirement listed must be defensible as genuinely necessary for the role. If a specification requires a bachelor's degree but the job can be performed effectively without one, that requirement could be challenged as discriminatory under disparate impact doctrine (Griggs v. Duke Power Co., 1971). The Americans with Disabilities Act requires that specifications distinguish between essential and marginal functions. Physical requirements must reflect actual job demands, not assumptions. Listing "must be able to lift 50 lbs" for a desk-based role is a compliance risk. Every specification should be reviewed against the job analysis data and validated by HR and legal.
Components of a Job Specification
A complete job specification addresses these categories. Not every role will use every category, but each should be considered.
| Component | What It Covers | Example |
|---|---|---|
| Education | Minimum and preferred educational qualifications | Bachelor's in Computer Science or equivalent practical experience |
| Experience | Years and type of relevant work experience | 3+ years of B2B SaaS product management experience |
| Technical skills | Specific tools, technologies, methodologies, or domain expertise | Proficiency in SQL, Tableau, and statistical analysis (regression, A/B testing) |
| Soft skills/Competencies | Behavioral and interpersonal capabilities | Strong cross-functional communication, conflict resolution, stakeholder management |
| Certifications/Licenses | Required professional certifications or legal licenses | PMP certification required, AWS Solutions Architect preferred |
| Physical requirements | Physical demands of the role (if applicable) | Ability to stand for 8-hour shifts, lift up to 30 lbs |
| Personal attributes | Traits and work style characteristics that predict success | High comfort with ambiguity, self-directed, detail-oriented under deadline pressure |
How to Write an Effective Job Specification
Writing job specifications is a balance between being specific enough to guide hiring decisions and being flexible enough to attract a diverse candidate pool.
Start with job analysis data
Don't write specifications from memory or assumptions. Base every requirement on documented job analysis: observation of current job holders, interviews with managers, review of performance data for successful employees in the role. Ask: "What skills and attributes distinguish high performers from average ones in this role?" Those differentiators become your essential requirements. Everything else is nice-to-have.
Separate essential from desirable requirements
Essential (must-have): Requirements without which the candidate genuinely cannot perform the core functions. These are non-negotiable. Desirable (nice-to-have): Additional qualifications that would make the candidate more effective but aren't required from day one. They can be learned on the job. Be honest about which category each requirement belongs to. If you label 15 things as "essential," you've either inflated the requirements or the job is so complex that you need to split it into two roles.
Use measurable, observable criteria
Vague specifications like "good communication skills" are almost useless for evaluation. What kind of communication? Written? Verbal? Presenting to C-suite? Translating technical concepts for non-technical stakeholders? Instead of "good communication skills," write: "Ability to present project status and recommendations to VP-level stakeholders in weekly reviews." Measurable criteria reduce interviewer subjectivity and make evaluations consistent across candidates.
Question every educational requirement
Does the role genuinely require a bachelor's degree, or does it require the skills typically gained during a degree? Many companies are removing degree requirements: Google, Apple, IBM, and Accenture no longer require degrees for most roles. If the specification lists a degree, add "or equivalent practical experience" to keep the door open for self-taught professionals, bootcamp graduates, and career changers. This single change can increase your candidate pool by 30 to 50% for many roles.
Validate against current top performers
Compare your draft specification against the profiles of people who are currently excelling in the role. If your best performer doesn't meet one of the "essential" requirements you listed, it probably shouldn't be essential. This reality check prevents specifications from becoming aspirational wish lists that no real human would meet.
How Job Specifications Impact the Hiring Process
The specification directly shapes every downstream hiring activity.
Sourcing and screening
Recruiters use the specification to write Boolean searches, set ATS screening filters, and evaluate resumes. A clear specification means recruiters spend time on qualified candidates instead of guessing. A vague specification means every resume looks like a potential fit (or none of them do), and the recruiter can't make confident decisions about who to advance.
Interview design
Each essential requirement in the specification should map to at least one interview question or assessment. If "SQL proficiency" is essential, there should be a technical question or test that evaluates SQL skills. If "stakeholder management" is essential, there should be a behavioral interview question like: "Tell me about a time you managed conflicting priorities from two senior stakeholders." Specifications that aren't tested during interviews are just words on paper.
Offer decisions and compensation
When multiple candidates are finalists, the specification provides the evaluation framework for choosing between them. Who meets more of the essential requirements? Who brings stronger desirable qualifications? This structured comparison reduces the influence of personal preferences and hiring biases. The specification also informs compensation: candidates who exceed the specification's requirements may command higher salary within the range.
Common Job Specification Mistakes
These errors reduce hiring effectiveness and can create legal exposure.
Inflated requirements
Requiring 10 years of experience for a mid-level role, demanding a master's degree for work that doesn't need one, or listing 20 technical skills when the job uses 5. Every inflated requirement narrows your candidate pool, disproportionately discourages underrepresented applicants, and extends time-to-fill. The Hewlett Packard research is clear: women apply only when they meet 100% of requirements, while men apply at 60%. Fewer, more accurate requirements increase both quality and diversity of applicants.
Copying old specifications without reviewing
Roles evolve. A specification written 5 years ago for a "Social Media Manager" probably includes skills that are now irrelevant (like Vine expertise) and misses skills that are now essential (like short-form video production for TikTok and Reels). Always review and update specifications before each hiring cycle. Compare the old spec against current job analysis data and the profiles of current top performers.
Using personality traits as requirements
"Must be an extrovert" or "outgoing personality required" are problematic for several reasons. They're not measurable, they introduce bias against introverted candidates who may excel in the role, and they can't be objectively assessed in an interview. Replace personality traits with observable behaviors: instead of "extroverted," specify "comfortable presenting to groups of 50+ people and facilitating workshops."
No distinction between essential and desirable
When everything is labeled as "required," nothing is. Candidates can't tell what actually matters. Recruiters can't prioritize. And the hiring team debates whether a candidate who meets 12 of 15 requirements is "good enough." Draw a clear line. If someone can't do the job without it, it's essential. If they can learn it in the first 90 days, it's desirable.
Job Specification Template and Example
Here's a practical template structure that works for most roles.
Template structure
Start with the job title and department. Follow with the role summary (2 to 3 sentences describing the role's purpose and impact). Then list Essential Requirements: education or equivalent experience, years and type of experience, specific technical skills, critical competencies. Then Desirable Requirements: additional certifications, industry-specific knowledge, bonus technical skills, language abilities. Finally, include Working Conditions if relevant: physical demands, travel requirements, shift patterns. Keep the total document to one page.
Example: Senior Product Manager specification
Essential: 5+ years of product management experience in B2B SaaS. Demonstrated ability to define product strategy and roadmap based on customer research and business metrics. Experience with agile development methodologies (Scrum or Kanban). Strong written communication (PRDs, strategy documents, customer-facing content). Track record of shipping products from concept to launch with measurable business outcomes. Desirable: Experience in HR tech or recruiting technology. Familiarity with SQL for ad hoc data analysis. Prior experience managing products with 10K+ active users. Product management certification (AIPMM or equivalent). Working Conditions: Hybrid role (3 days in office). Occasional travel (10 to 15%) for customer interviews and conferences.
Frequently Asked Questions
What's the difference between a job specification and a competency framework?
How many requirements should a job specification include?
Should job specifications include salary information?
Can job specifications be discriminatory?
How often should job specifications be updated?
Who is responsible for writing job specifications?
Written by Adithyan RK