Job descriptions are marketing. They’re how you attract candidates and set expectations. A generic, boring description gets generic, disengaged applicants. A compelling, clear description attracts people who want to work with you.
What a Job Description Must Do
Not everyone—the right people.
The right candidates should think:
•
“This is exactly what I’m looking for”
•
“This company sounds interesting”
Wrong candidates should think:
•
“I don’t have this experience”
•
“This culture isn’t my style”
Clarity about what the job actually is.
•
What they’ll do day-to-day
•
What the environment is like
Structure of a Great Job Description
First paragraph matters most.
•
What the company does (briefly)
Example:
“We’re building [product] to solve [problem] for [who]. We’re looking for [role] to [impact]. This is a chance to [exciting opportunity].”
What they’ll actually do.
•
Key responsibilities (5-8 bullets)
•
Vague language (“drive results”)
•
Endless lists of everything
•
Must-have skills and experience
•
Keep it focused (5-7 items)
•
Things that would help but aren’t required
Be honest: If something is truly required, say so. If it’s flexible, say that.
•
What you’re building and why
Be real: Generic statements don’t differentiate.
5. Compensation and Benefits
•
Salary range (required in many places, good practice everywhere)
•
What to expect in the process
Vague:
“Own the product strategy.”
Specific:
“Define the product roadmap for our mobile app. Run discovery with customers. Prioritize features based on user research and business impact.”
Specificity helps candidates self-select.
Passive:
“Responsibilities include management of engineering team.”
Active:
“Lead a team of 5 engineers building our core platform.”
Active voice is clearer and more engaging.
Why does this role matter?
Before:
“Build features for our product.”
After:
“Build features that help [customers] achieve [outcome]. Your work will directly impact [metric].”
Be Honest About Challenges
Transparency builds trust.
“We’re early stage. Things change fast. You’ll be building process from scratch. If you want established structure, this might not be for you.”
Right candidates will appreciate honesty.
Everyone is “fast-paced” and “mission-driven” and wants “rock stars.”
•
What’s actually different about you?
•
What’s the real culture like?
•
What specifically makes this interesting?
Generic language attracts generic candidates.
Must-Have vs. Nice-to-Have
Be honest about what’s required:
If you’d hire someone without skill X, it’s not required.
Overly strict requirements:
•
“5+ years experience required” (when 3 would be fine)
•
“Must have [specific technology]” (when they could learn)
•
Long lists of requirements
Result: Qualified candidates self-select out.
The Problem with Laundry Lists
•
Intimidate qualified candidates
•
Especially affect underrepresented groups
•
Often not actually required
Research shows: Men apply when meeting 60% of requirements. Women apply when meeting 100%.
Required (3-5 items):
Things you truly need.
Nice to have (2-3 items):
Things that would help.
State explicitly:
“We’d love to hear from you even if you don’t meet every requirement.”
Multi-page job descriptions.
Fix: Keep it to 1-2 pages max. Focus on what matters.
Could be any company, any role.
Fix: Include specific details about your company and this specific role.
Is this entry-level or senior? Unclear.
Fix: Be explicit about level and expectations.
Makes candidates guess if it’s worth applying.
Fix: Include range. It saves everyone time.
All Requirements, No Selling
Fix: Sell the opportunity, not just the requirements.
“Synergize stakeholder alignment to drive ROI.”
Fix: Write like a human. Clear, simple language.
Language signals who’s welcome.
Gendered language: “He will lead…” excludes half of candidates.
Aggressive language: “Crush it,” “killer instinct” signals culture some won’t want.
•
Use “you” instead of gendered pronouns
•
Avoid unnecessarily aggressive language
•
Focus on what the role involves, not personality stereotypes
•
State commitment to diversity if genuine
•
Textio and similar platforms
•
Have diverse reviewers read it
[Role] at [Company]
[1-2 sentence hook: What is this role and why is it exciting?]
About Us
[2-3 sentences: What you do, who you serve, what stage you're at]
About the Role
You'll [own/lead/build] [specific area]. This is a chance to [impact].
Day-to-day, you'll:
• [Responsibility 1]
• [Responsibility 2]
• [Responsibility 3]
• [Responsibility 4]
• [Responsibility 5]
What We're Looking For
Required:
• [Must-have 1]
• [Must-have 2]
• [Must-have 3]
Nice to have:
• [Bonus 1]
• [Bonus 2]
[Note about not needing to meet every requirement]
What We Offer
• [Salary range]
• [Equity]
• [Key benefits]
• [Location/remote]
How to Apply
[Clear instructions]
•
Job descriptions are marketing—they attract and filter candidates
•
Hook them in the opening paragraph; don’t bury the good stuff
•
Be specific about what they’ll actually do, not vague platitudes
•
Keep requirements focused: 3-5 must-haves, 2-3 nice-to-haves
•
Long requirement lists scare off qualified candidates, especially underrepresented groups
•
Include salary range—it saves everyone time
•
Sell the opportunity, not just list demands
•
Skip corporate speak and clichés; write like a human
•
Be honest about challenges—transparency attracts the right people
•
Check for inclusive language; words signal who’s welcome