Job Description Templates That Attract Good Hires (Not Spam Applicants)
Write job descriptions that filter for fit: role outcomes, must-haves vs nice-to-haves, red flags to avoid, and copy-paste templates for remote and hybrid roles.
A vague job description attracts everyone — and the wrong everyone. Good JDs sell the mission and filter for skills at the same time.
Outcome-first JD structure
- Role headline — title + level + location/remote
- Mission — one paragraph on why this role exists
- Outcomes (90 days) — 3–5 measurable results
- Responsibilities — 6–8 bullets max
- Must-haves — non-negotiables only
- Nice-to-haves — clearly labeled
- How we work — hours, tools, culture signals
- Process — next steps + timeline
Templates you can adapt
Growth marketer
Mission: Own experiments that grow qualified signups without burning paid budget.
90-day outcomes: Launch 8 tests, document winners, improve activation by X%.
Must-haves: Experiment design, analytics literacy, clear writing.
Customer support lead
Mission: Turn support into a trust channel.
90-day outcomes: Cut first-response time, publish FAQ updates from ticket themes.
Must-haves: Empathy under pressure, writing clarity, ownership.
Junior content writer
Mission: Ship useful posts that map to products.
90-day outcomes: 8 published drafts through editorial QA.
Must-haves: Portfolio samples, willingness to revise, basic SEO awareness.
Language that quietly repels great people
- “Rockstar / ninja / hustle culture”
- Unlimited unpaid overtime vibes
- 12 years experience for “junior” roles
- Fake “family” without boundaries
Inclusive clarity checklist
- Separate must vs nice
- Avoid gendered coded words when possible
- State salary range if you can — it filters faster
- Say who not to apply (politely) when relevant
Related guides
Frequently asked questions
How long should a job description be?
400–700 words is enough. Longer only for regulated or highly senior roles.
Should AI write the whole JD?
Use AI for a first draft, then replace fluff with real outcomes, tools, and process specifics only your team knows.
A job description is both a recruiting filter and an operating document. Strong candidates need enough detail to judge the work, authority, environment, and trade-offs—not a list of inflated traits copied from another company.
Define the role before writing
-
List the outcomes expected in the first 30, 90, and 180 days. Separate what the person owns from what the team owns.
-
Name the manager, close collaborators, decision authority, and whether the role creates a new function or replaces an existing position.
-
Split requirements into essential at entry and learnable after hiring. Remove credentials that are proxies rather than genuine job needs.
-
Confirm compensation range, location, schedule, travel, equipment, and employment status with HR or legal requirements for each hiring region.
Use a candidate-readable structure
Open with why the role exists, then describe outcomes and a realistic week. Follow with essential skills, useful extras, team context, compensation, benefits, process, and accessibility information. Keep company history brief unless it changes the work.
Audit language and scope
Replace “rockstar,” “digital native,” and personality-coded demands with observable work. Watch for a role that combines several full-time specialties or asks junior compensation for senior accountability. Invite candidates who meet most essential requirements without implying standards are optional.
Align the interview
Every interview stage should assess something named in the description. Publish the number and type of stages, avoid unpaid production work, and use the same scorecard across candidates. If the hiring team changes the role during interviews, revise the public description.
A practical review checklist
- Outcomes are clearer than task volume.
- Essential and learnable skills are separated.
- Compensation and location terms are explicit.
- Language describes observable work.
- Interview stages map to stated requirements.
Frequently asked questions
How many requirements should I list?
List the smallest set needed for safe and effective entry. Long wish lists discourage qualified applicants and obscure the capabilities that actually matter.
Should salary always be included?
Transparency improves self-selection and is legally required in some locations. Use a genuine range and explain variables rather than publishing an unusably broad band.
Can I reuse an old description?
Use it as a prompt for stakeholder review, not a source of truth. Team structure, tools, outcomes, and market expectations may have changed.
The related job-description tool can provide structure; the hiring manager must supply real outcomes, constraints, and compensation.
Share this article