HIRING · Updated June 19, 2026

How to write a job description candidates actually finish reading

Five rules, a reusable structure, and an AI-assisted shortcut — built from thousands of JDs shipped through RoleHive. Use it as a checklist before every requisition.

Already know what role you're hiring for? Jump straight to the pay transparency checklist to make sure the posting is compliant before it goes live.

The five rules

These are the patterns that consistently separate JDs that fill the role from JDs that sit open for 90 days. Apply them in order — each one compounds on the one before it.

RULE 01

Lead with the outcome, not the title

Candidates skim. The first 80 words decide whether they keep reading or close the tab.

Start with what the role will accomplish in the first 6–12 months — the problem it solves, the product surface it owns, the customer it serves. Save the company boilerplate for the bottom. A clear outcome statement filters in candidates who actually want the work and filters out everyone else, which is the whole point of the JD.

DON'T

We are looking for a passionate Senior Product Designer to join our growing team in a fast-paced environment.

DO

You'll own the onboarding experience for our 40,000 paid users — shipping a new flow within 90 days that takes activation from 38% to 55%.

RULE 02

Separate must-haves from nice-to-haves

Long requirement lists shrink the qualified applicant pool, especially among women and underrepresented candidates.

Pick 4–6 must-haves that genuinely predict success in the role and put everything else under nice-to-haves. Drop the years-of-experience proxy when a skill or portfolio demonstrates the same thing. Be specific: "shipped a B2B onboarding flow that moved activation" tells you more than "5+ years in SaaS."

DON'T

Requirements: 7+ years experience. Bachelor's degree required. Master's preferred. Expert in 12 tools.

DO

Must-haves: shipped a B2B SaaS onboarding flow end-to-end; comfortable working directly with engineers in Figma; data-literate (you can read funnel charts and form a hypothesis).

RULE 03

Show pay, level, and location up front

Compensation isn't a closing detail — it's the single biggest reason candidates apply or skip.

Put a good-faith pay range, the level (IC4, Senior, Staff), and the working location (remote, hybrid, on-site with city) high in the JD. In states like California, Colorado, New York, and Washington this isn't optional — see our pay transparency guide. Even where it isn't legally required, posting pay roughly doubles qualified applicant flow in most studies.

DON'T

Competitive salary. Location flexible.

DO

$165k–$190k base + 0.05–0.10% equity · Senior IC (L5) · Remote within US/Canada, with quarterly on-sites in NYC.

RULE 04

Write like a human, not a brochure

Corporate filler ("synergistic," "rockstar," "family," "wear many hats") is invisible to good candidates and a red flag to great ones.

Use the second person. Use short sentences. Cut adjectives you can't measure. Read the JD out loud — anywhere you'd be embarrassed to say it to a friend, rewrite it. The voice should match how your team actually talks in Slack, not how a 2014 careers page sounded.

DON'T

We are a passionate, fast-paced, mission-driven family of rockstars looking for a unicorn who can wear many hats.

DO

Our team is six engineers, two designers, and one PM. We ship weekly, do async standups, and meet in person once a quarter. You'll be the third designer.

RULE 05

Make the next step obvious and small

If the application takes 40 minutes, your best candidates — the ones with options — won't start it.

Tell candidates exactly what happens after they apply: who reviews it, how long it takes, what the interview loop looks like. Cut every field you don't truly need on the application itself. A 5-minute application with a clear loop converts 3–4× better than a long form behind a generic "Apply now."

DON'T

Submit your application and we will get back to you if there is a fit.

DO

Apply with a résumé or LinkedIn. We reply within 5 business days. Loop is: 30m with the hiring manager → 45m portfolio review → 60m system + collab session with two future teammates.

JD structure template

A reusable skeleton you can drop any role into. Keep the order — candidates expect the most important information (outcome, comp, location) before they decide to keep reading.

  1. 01

    Headline + outcome

    Role title, 1–2 sentences on the outcome you're hiring for, the most exciting context.

  2. 02

    Pay, level, location

    Range, level, working pattern, time zone overlap. Above the fold.

  3. 03

    What you'll do

    4–6 concrete responsibilities, written as verbs the person will actually do this quarter.

  4. 04

    Must-haves

    4–6 capabilities tied to outcomes. Use skills and demonstrated work, not years.

  5. 05

    Nice-to-haves

    Optional. Helps candidates self-assess without filtering themselves out.

  6. 06

    How we work

    Team size, meeting cadence, async vs sync, in-office expectations.

  7. 07

    Hiring process

    Steps, who's involved, total time commitment, decision SLA.

  8. 08

    Company + benefits

    Short. Link to a careers page for the long version.

Need a head start? Browse the template library — every template uses this structure with role-specific defaults filled in.

AI-ASSISTED JD WRITING

Use AI to draft, not to publish

A generic prompt to ChatGPT produces a generic JD — heavy on adjectives, light on specifics, often missing pay and process. The fix isn't avoiding AI; it's feeding it the right inputs and reviewing the output against the rules above.

What to feed the model

  • The outcome you're hiring for in one sentence ("ship a new onboarding flow that takes activation from 38% to 55%").
  • Team shape (size, function mix, who the role reports to).
  • The 4–6 must-haves — written as capabilities, not years.
  • Pay range, level, and location (or remote eligibility).
  • The interview loop and decision SLA.

What to check before publishing

Compliance (state-by-state pay disclosure), inclusive language, voice consistency, and whether the must-haves actually predict success. This is the layer RoleHive's JD generator runs automatically — it produces the draft, flags missing fields, applies the active state's pay-disclosure rule, and lets the hiring manager edit in plain language without breaking the structure.

SHORTCUT

Have RoleHive draft the JD from a one-sentence brief, then edit. Most teams ship a ready-to-post JD in under 10 minutes — and every draft already passes the checklist below.

Pre-publish checklist

Run this before any role goes live. RoleHive applies the same checks automatically when generating or refining a job description.

  • Title is the role candidates would search for, not your internal job code.
  • Outcome appears in the first 80 words.
  • Pay range, level, and location are above the responsibilities list.
  • Must-haves list is 4–6 items, each tied to a real outcome.
  • No years-of-experience proxy where a skill describes it better.
  • Voice matches how the team actually talks (read it out loud).
  • Interview loop and SLA are documented in the JD.
  • Required application fields trimmed to the bare minimum.
  • Inclusive-language pass complete (no "rockstar," "ninja," "young," "native English").
  • Compliance pass complete for every state the role could be filled from.

FAQ

How long should a job description be?

Aim for 350–600 words in the body. Short enough that candidates read it on a phone in under three minutes, long enough to communicate the outcome, must-haves, comp, and process. Anything past 600 words is usually company boilerplate that belongs on a separate careers page.

Should I include salary in the job description?

Yes — almost always. Several US states (CA, CO, NY, WA, IL, MD, NJ, MA, MN, VT, and DC, with more added each year) require a good-faith pay range on the posting. Even where it isn't required, posting pay typically doubles qualified applicant flow and cuts down on misaligned conversations.

What's the difference between a job description and a job posting?

A job description is the internal-facing document that defines responsibilities, level, and comp band. A job posting is the candidate-facing version published on your careers page or LinkedIn. The posting should be a tighter, second-person rewrite of the JD — same facts, friendlier voice.

Can I use AI to write a job description?

Yes, and it's the fastest way to get a strong first draft. The trick is to feed the AI specific inputs (the team, the outcome, the must-haves, the comp band) rather than asking for a generic JD. Tools like RoleHive's JD generator structure the prompt for you and run compliance and inclusive-language checks before you publish.

How often should I update job descriptions?

Re-review every time you reopen the requisition, and at minimum every 12 months. Responsibilities drift, comp bands move, and the laws governing what must appear on a posting change every quarter.

— From brief to published JD —

Draft your next JD in minutes, not hours.

RoleHive turns a one-sentence brief into a structured, compliant, on-voice job description — ready to publish or hand off to your ATS.