Job Description Template for Hiring Teams and HR

A job description template helps hiring teams define what a role does, what success looks like, who approves it, and how candidates should be evaluated. It is more than a job ad. A good job description becomes the source of truth for recruiting, compensation, interviews, onboarding, performance expectations, and future role changes.

This resource is written for business teams that need a practical template they can copy, customize, and operationalize. It is not legal, HR, compensation, or employment advice. Review final job descriptions with qualified HR, legal, compensation, and compliance support, especially for regulated roles, multi-state hiring, union roles, exempt/nonexempt classification, accommodations, or safety-sensitive work.

What is included

• A copy-ready job description template for business and HR teams.
• A checklist for turning a hiring request into a role definition.
• A responsibility table that connects the job description to interviews, onboarding, and performance review.
• Common mistakes that make job descriptions hard to use after the role is posted.

How to use this job description template

Start with the operating need, not the title. Ask which work is not getting done, which team owns it today, what outcomes the new hire must improve, and which approvals are required before the role is opened. Then use the template to document the role in a format that HR, finance, the hiring manager, interviewers, and the future employee can all use.

For official job analysis language and occupational examples, teams can reference resources such as the O*NET occupational database. For U.S. compliance-sensitive role language, the EEOC guidance on employer ADA responsibilities is useful when thinking about essential functions and reasonable accommodation. SHRM also maintains practical guidance on developing job descriptions for HR teams.

Job description template

Copy the structure below into your HR system, approval workflow, job posting process, or internal role library. Replace bracketed text with your company details.

1. Role overview

Job title: [Role title]

Department: [Department or function]

Reports to: [Manager or role]

Location: [Office, remote, hybrid, region, or field territory]

Employment type: [Full-time, part-time, temporary, contract, internship, seasonal]

FLSA or local classification: [Exempt, nonexempt, contractor, or local equivalent, if applicable]

Compensation range: [Salary, hourly range, commission, bonus, or other structure where disclosed]

2. Role purpose

[Company Name] is hiring a [Role Title] to [primary business outcome]. This role is responsible for [main responsibility area] and works closely with [teams, customers, vendors, partners, or stakeholders]. Success in this role means [measurable outcome, service level, business result, or operational improvement].

3. Key responsibilities

• [Responsibility 1 tied to a business outcome]
• [Responsibility 2 tied to a recurring workflow or deliverable]
• [Responsibility 3 tied to collaboration, customers, vendors, or internal partners]
• [Responsibility 4 tied to documentation, reporting, compliance, quality, or approvals]
• [Responsibility 5 tied to improvement, escalation, or problem solving]

4. Required qualifications

• [Required experience, certification, license, education, or practical skill]
• [Required tool, system, industry, or workflow experience]
• [Required communication, judgment, physical, travel, scheduling, or availability requirement]

5. Preferred qualifications

• [Nice-to-have experience that improves performance but is not required]
• [Industry familiarity, additional tool knowledge, or advanced capability]

6. Success measures

• [Metric or outcome the role should improve]
• [Quality, speed, compliance, service, revenue, cost, or customer measure]
• [30, 60, or 90-day milestone for onboarding]

7. Working conditions and expectations

This role may require [schedule, travel, location, physical requirements, equipment use, customer interaction, confidentiality, system access, or safety requirements]. Include only requirements that are accurate, job-related, and reviewed by the appropriate owner.

Job description approval checklist

1. Confirm the business need and budget owner.
2. Define the role outcomes before listing tasks.
3. Separate required qualifications from preferred qualifications.
4. Review compensation range, classification, location rules, and approval status.
5. Confirm essential functions, working conditions, accessibility, and accommodation language with HR or legal where needed.
6. Map responsibilities to interview questions and scorecards.
7. Map success measures to the first 30, 60, and 90 days of onboarding.
8. Store the final description where HR, finance, the manager, interviewers, and onboarding owners can find it.

How the template connects to hiring operations

Example job description summary

A customer operations coordinator might be described this way: The role supports daily customer requests, routes issues to the right internal owner, monitors response timelines, updates records, and escalates blocked work. Success means customer requests are acknowledged quickly, assigned accurately, documented clearly, and resolved within the team service standard.

That summary is stronger than a generic list of tasks because it connects the work to outcomes. It also gives interviewers, managers, and onboarding owners a clearer way to evaluate whether the role is working.

Common mistakes

• Writing the job description like a job ad only. A job ad attracts candidates, but the job description should also support approvals, interviews, onboarding, and performance.
• Listing every possible task. Long task lists hide the core purpose of the role. Focus on recurring responsibilities and business outcomes.
• Mixing required and preferred qualifications. This can narrow the candidate pool unnecessarily and make screening inconsistent.
• Forgetting approval owners. Compensation, classification, location, budget, and reporting line should be approved before posting.
• Not updating the description after hiring. If the role changes during hiring or onboarding, update the source document so expectations stay accurate.

Where Workhint fits

Workhint helps organizations turn a static job description template into a live hiring and onboarding workflow. A team can use Workhint to define role intake, approvals, job description ownership, interview scorecards, document reviews, onboarding tasks, permissions, manager check-ins, and status reporting around the role.

This matters when role creation touches several teams. HR may own the template, finance may approve budget, managers may define outcomes, interviewers may evaluate candidates, IT may prepare access, and operations may track onboarding. Workhint helps connect those steps in an employee onboarding workflow so the job description does not sit disconnected from the work that follows.

FAQ

What should a job description template include?

A job description template should include role title, department, reporting line, location, employment type, classification, compensation range where applicable, role purpose, responsibilities, required qualifications, preferred qualifications, success measures, working conditions, and approval owners.

Is a job description the same as a job posting?

No. A job description defines the role internally. A job posting markets the role externally. They should be aligned, but the internal job description usually includes more detail about approvals, reporting lines, expectations, and operating context.

Who should approve a job description?

The hiring manager should approve role responsibilities and outcomes. HR should review structure, employment language, and consistency. Finance or leadership should approve budget and compensation. Legal or compliance may need to review regulated, safety-sensitive, or multi-jurisdiction roles.

How often should job descriptions be updated?

Review job descriptions when a role is opened, when responsibilities change, during compensation review, before performance review cycles, after team restructures, and when legal or operational requirements change.

Conclusion

A useful job description template gives the business more than a cleaner job post. It creates a shared operating record for why the role exists, what the person will own, how success will be measured, who approved the role, and how the hire should be onboarded. When the template is connected to approvals, interviews, onboarding, and performance, it becomes a practical management tool instead of a document that gets forgotten after recruiting starts.