Job description example: build the role before you write the ad

A complete employer example

Job title: Customer Support Team Lead
Reports to: Head of Customer Operations
Location and schedule: [approved arrangement]
Employment status: [approved classification]

Role purpose: Keep the support queue predictable and help agents resolve recurring customer problems consistently.

Outcomes:

• Maintain clear daily queue ownership and escalation coverage.
• Coach agents using reviewed conversations and documented standards.
• Identify recurring product or process failures and route them to the correct owner.
• Keep support procedures current when the product changes.

Essential functions:

• Assign and rebalance queue work.
• Handle defined escalations.
• Review service-quality samples and deliver feedback.
• Coordinate with product, sales, and billing owners.
• Maintain accurate team records and procedures.

Required qualifications: [only skills, experience, education, licenses, or availability needed for the work].
Preferred qualifications: [use sparingly].
Working conditions: [screen time, phone work, shifts, travel, physical or environmental conditions, where job-related].

Why essential functions need evidence

EEOC guidance says essential functions are the basic duties an employee must perform, with or without reasonable accommodation. Relevant evidence includes why the position exists, available staff, expertise, actual employee experience, time spent, and consequences if a duty is not performed [EEOC, 2026].

A written description prepared before advertising or interviewing can be considered evidence of essential functions, but the label is not conclusive. Do not mark every task "essential" to avoid doing the analysis.

Job description versus job posting

The internal description can include decision rights, handoffs, controls, and operational detail. The public posting should explain the work, requirements, pay or benefits information required by law, location, schedule, application process, and why a qualified candidate might choose the role.

Do not bury schedule, travel, physical conditions, or weekend work after a long culture paragraph. Candidate surprises become early turnover and manager rework.

Qualification audit

For each requirement, ask what task fails without it and whether experience, training, or another credential could show the same capability. Separate mandatory licenses from preferences. Remove years-of-experience inflation copied from the prior employee.

Read the description for coded or exclusionary language, unexplained physical demands, and requirements unrelated to actual work. An accommodation statement is not a substitute for accurate essential functions.

Manager calibration before posting

Ask the manager to allocate a normal week across outcomes, name the hardest decision, list the three most common handoffs, and describe what good performance looks like at 30, 90, and 180 days. Compare that answer with the written duties.

Then ask a current role-holder or adjacent colleague what is missing. Differences often reveal hidden administrative work, unofficial on-call duties, or a title that does not match the job.

Frequently asked questions

How long should a job description be? Long enough to define the work and boundaries. The candidate posting can be shorter than the internal operating document.

Should every duty be essential? No. Distinguish fundamental duties from marginal, shared, or occasional tasks.

Can we reuse a competitor's description? Use occupational references for research, but write from your real workflow, tools, schedule, and decision rights.

When should it be updated? Review it when the role, manager, location, technology, or required qualification changes and before the next hiring cycle.