Job Description Template for Evidence-Ready Hiring

A job description template should do more than help a hiring manager fill a blank page. It should create one role record that a recruiter can carry into sourcing, resume review, interviews, and the final human decision without translating the role from scratch at every stage.

The U.S. Office of Personnel Management describes job analysis as the foundation for assessment and selection decisions. Its guidance connects the tasks performed in a job and the competencies required to perform them. That connection is the core of this template: every qualification should point back to work the person will actually own.

Use the copyable structure below as the approved role record, then adapt the candidate-facing language for the opening. The template is deliberately compact. If a field does not improve role clarity or a later review, it does not belong here.

Copyable job description template

1. Role identity

• Role title: [Use the title candidates and the hiring team will recognize.]
• Team: [Name the function and immediate team.]
• Reports to: [Name the manager role, not a person.]
• Role level: [State the approved level and the scope that distinguishes it.]
• Work arrangement: [Describe where and how the work is expected to happen.]
• Role owner: [Name the hiring manager role responsible for keeping this record current.]

2. Role purpose

Why this role exists: [In two or three sentences, name the problem the role owns, the people or systems it serves, and the change successful work should create.]

Avoid an opening built from adjectives. “Strategic, collaborative leader” does not tell a recruiter what evidence to seek. A useful purpose statement names decisions, deliverables, and impact: “This role turns customer and operating evidence into a prioritized product plan and owns the cross-functional handoff from decision to delivery.”

3. Outcomes

• Outcome 1: [What should be observably different after the person has learned the role?]
• Outcome 2: [What recurring result will this role own?]
• Outcome 3: [Which important handoff, decision, or service should become more reliable?]

Outcomes give the hiring team a reason for each requirement. They are not promises about what one person will achieve on a fixed timeline. Write them as role expectations the team can explain and revisit.

4. Responsibilities

• [Action verb] [the work or decision owned] [for whom or at what scope].
• [Action verb] [the recurring deliverable] [with the important collaborators named].
• [Action verb] [the problem to diagnose or improve] [using the relevant evidence].
• [Action verb] [the handoff or communication responsibility] [and what a complete handoff contains].
• [Action verb] [the review or operating responsibility] [and who depends on it].

Describe ownership, not every activity someone might perform. If two bullets express the same responsibility with different verbs, combine them. If a responsibility does not connect to a role outcome, decide whether it is background context or whether the outcome list is incomplete.

5. Required qualifications

For every required item, complete all four fields:

• Qualification: [Name the capability in observable terms.]
• Supports: [Link it to a responsibility or outcome above.]
• Evidence indicator: [Describe what a resume, work sample, or structured conversation could establish.]
• Needed when: [State whether it must be present at entry or can be developed in the role.]

Repeat that structure only for qualifications whose absence would materially change the initial review. “Strong communication” is too vague to screen consistently. “Has explained a high-impact technical trade-off to a nontechnical decision group” names work and gives the reviewer something concrete to verify.

6. Preferred qualifications

List capabilities that would help but should not act as an undeclared gate. Use the same qualification, responsibility, and evidence fields as the required section. That forces the hiring team to explain why an item matters and prevents a familiar tool, title, or industry label from quietly becoming more important than the work itself.

UC Davis Human Resources recommends separating critical requirements from desirable ones and notes that screening should use the criteria stated in the position description. That is a practical reason to preserve the distinction in the source document rather than deciding it candidate by candidate.

7. Working context

• Key collaborators: [Roles or teams this person works with regularly.]
• Decision scope: [Decisions owned, decisions recommended, and decisions approved elsewhere.]
• Operating rhythm: [Important recurring reviews, cycles, or handoffs.]
• Tools or systems: [Include only those necessary to understand the work; separate trainable tools from entry requirements.]

This section gives a candidate and reviewer the context needed to interpret experience. It should not become a hidden list of personality preferences. Keep the language attached to observable interactions and decisions.

8. Hiring process

• Initial review: [Criteria examined and accountable reviewer.]
• Screening conversation: [Evidence gaps or role context to clarify.]
• Structured interviews: [Priority areas and interviewer ownership.]
• Additional assessment, if used: [Capability examined and review method.]
• Decision: [Person accountable for the final selection and evidence packet required.]

A maintained template can connect the document to the process. GitLab’s current job description library template includes an overview, role, level, responsibilities, requirements, performance indicators, career ladder, and hiring process. Your exact sections may differ, but naming the downstream process keeps the description from ending at publication.

9. Version record

• Version date: [YYYY-MM-DD]
• Approved by: [Hiring manager and recruiter roles.]
• Role expert consulted: [Current role holder, former role holder, or subject-matter reviewer.]
• Reason for revision: [New role, changed scope, unclear screening results, or another specific trigger.]

Keep prior versions when a live search spans a meaningful change. The team should be able to tell which criteria shaped each review and whether earlier candidates need another look under the revised standard.

How to complete the template with the hiring manager

Begin with the work, not the previous description. Ask the hiring manager for three recurring decisions, three important deliverables, and the consequences of weak execution. Then ask a current role holder or another qualified role expert to challenge the draft. The job analysis guide for recruiters provides the deeper workflow for connecting tasks, competencies, and screening criteria.

Next, read every required qualification beside the responsibility it supports. Remove any item that lacks a clear connection. Move trainable capabilities to preferred or working context. For each remaining requirement, write one evidence indicator and one likely follow-up question. This turns the description into a usable input for candidate review without pretending that a resume answers everything.

Finally, ask the recruiter to read the document as an outsider. Unfamiliar internal language, duplicated requirements, and ambiguous level signals are easier to find before the opening is published. Use the job description checklist for that final review, and run the text through the Job Description Health Checker to surface clarity gaps and requirements bloat.

Turn the approved description into an evidence-backed screen

Create one screening line for each required and preferred qualification. Preserve the link to the responsibility, the accepted evidence indicator, and the source excerpt for each candidate. Use a shared status vocabulary for established evidence, partial evidence, absent evidence, and unresolved information. The status organizes review; it does not decide who advances.

Resume Autopsy can compare a candidate batch with the supplied job description and organize supporting resume evidence under a qualification checklist. A recruiter must verify the extracted criteria, inspect the evidence, account for context the resume cannot establish, and make every advancement decision. If the output exposes a vague or overloaded requirement, correct the role record first and apply the revised version consistently.

Use AI as a drafting assistant, not a role owner

AI can propose headings, turn a vague responsibility into alternatives, identify repeated requirements, or suggest links between qualifications and outcomes. Treat those suggestions as provisional. The model does not know why the role exists, which trade-offs the team accepts, or whether a familiar phrase reflects the actual work.

The hiring manager owns the role, the recruiter owns the quality of the hiring handoff, and qualified human reviewers own candidate decisions. Keep those responsibilities visible in the version record and process section.

A template is useful when it survives the handoff

The test of a job description is not whether it sounds polished. It is whether a recruiter, interviewer, and hiring manager can use the same role definition without inventing new criteria along the way. A compact template that connects outcomes, responsibilities, qualifications, evidence, and decision ownership gives the team that common starting point.

When the role definition is ready, see Resume Autopsy for a human-reviewed candidate comparison built around the job description and supporting resume evidence.