What is A Job Specification?
A job specification describes the qualifications, skills, knowledge, experience, and other job-related requirements a person needs to perform a role. It gives recruiters and assessors a basis for deciding what evidence to seek. A job description concentrates on the work and responsibilities; a job specification concentrates on the requirements for performing that work.
Organizations use these labels differently. Some combine the specification and description in one document. In executive search, a position specification can include the company, mandate, responsibilities, and candidate profile. Agree on the document’s purpose before assuming its title establishes a fixed format.
Every requirement should have a reason tied to the work and a practical way to assess it.
What should a job specification include?
Begin with the capabilities required to deliver the role’s outcomes. These can include technical knowledge, relevant experience, professional credentials, communication requirements, and specific working conditions. State the required proficiency or scope where a broad skill label would be ambiguous.
Separate requirements needed at entry from preferences and capabilities that can be developed. A client may prefer experience with its exact software, but accept someone who can demonstrate comparable work with a related system. Keeping that distinction visible prevents unnecessary exclusion.
Describe the evidence expected. “Leadership” could mean allocating daily work, coaching supervisors, leading a business transformation, or influencing peers without formal authority. Each requires different questions. A requirement that no assessor can explain or evaluate needs revision.
Record practical constraints accurately, including location, travel, shift patterns, and any genuinely required credential. Avoid adding personal characteristics or proxies that have no defensible relationship to the role. Requirements with legal implications need appropriate local review.
How to write the specification
Use the job description and stakeholder discussions to identify the work. Ask capable incumbents and managers which tasks distinguish acceptable performance and what someone must know before starting.
Convert those tasks into requirements. For each item, ask why it is needed, how it will be assessed, and whether an alternative background could provide the same capability. Document who has approved the requirement.
Review the complete profile against the available market. An agency can test whether the combination of requirements, compensation, and location is realistic. Market difficulty does not automatically justify lowering standards; it can reveal the need to change the role, pay, support, or search scope.
Version the specification before research begins. When the client changes a requirement, update the shared brief and identify which earlier candidates need another look. An unrecorded change creates inconsistent screening and misleading reports about candidate quality.
Job specification versus position specification
A job specification can serve as the requirements component of a broader position specification. The latter may describe the organization, role context, reporting line, mandate, and candidate expectations together.
The distinction is useful for an agency intake. A polished search document may still contain vague requirements. Extract the criteria into a working assessment record so researchers and interviewers know what to verify.
A job advertisement serves a different purpose: communicating the opportunity to prospective applicants. It should accurately represent the role, but it does not need to reproduce every internal assessment instruction.
Example: defining a warehouse operations manager
A staffing client asks for five years of warehouse management experience and a degree. The recruiter asks which outcomes matter: safe shift delivery, inventory accuracy, supervisor coaching, and managing a seasonal peak.
The client confirms that the degree is a preference rather than a requirement for the work. The specification focuses on demonstrated responsibility for comparable operations, required safety knowledge, team leadership, and relevant scheduling experience. It names the evidence needed for each.
A candidate from a smaller site has managed a more complex shift pattern than someone from a larger facility. The recruiter investigates that evidence rather than using employer size as a shortcut. The updated specification gives the client a clearer basis for comparison.
Using the specification in assessment
Connect each requirement to a stage. A screening conversation may establish availability and clarify relevant scope. A technical interview can explore domain knowledge. A work sample can examine a task. An interview scorecard can keep evidence and ratings consistent.
Avoid asking every interviewer to assess every item. Assign ownership so important criteria receive enough attention without repeating the whole process. Leave room for follow-up where evidence is uncertain.
For executive roles, test scope and context rather than relying on titles. A chief financial officer in one organization may hold a very different remit from a person with the same title elsewhere. Ask about scale, decisions, stakeholders, and outcomes.
Quality checks and common mistakes
Check whether every requirement is clear, job-related, assessable, and classified correctly. Review how often interviewers disagree about the same wording and whether late brief changes are driving rejection.
Common problems include copying a predecessor’s background, making every preference mandatory, specifying arbitrary years of experience, and adding requirements after meeting an attractive candidate. Correct the brief openly rather than applying an invisible standard to later applicants.
Software can help organize criteria and search terms. It cannot establish that a requirement is appropriate simply by generating it. Recruiters and hiring stakeholders must review suggested requirements and verify that they relate to the actual work.
Practical checklist
- Identify the work and required outcomes.
- Separate entry requirements, preferences, and development needs.
- Define evidence and assessment ownership.
- Check the profile against compensation and market availability.
- Approve and version the brief.
- Reassess affected candidates after material changes.
Questions recruiters ask
Is a job specification the same as a job description?
They overlap, but a useful distinction is requirements versus responsibilities. Employers may combine both in the same document.
Must every requirement be mandatory?
No. Distinguish requirements needed to perform the role from preferences. State acceptable alternative evidence where appropriate.
Can the specification change during a search?
Yes. Record the change, obtain the relevant approval, brief assessors, and review earlier decisions affected by the revised criteria.
Recruitment