Job Description Best Practices

Structure

[Hook: Why this role matters]

## What You'll Do
- [Action verb] [specific responsibility] [impact/outcome]
- ...

## What You Bring
- [Skill/qualification] — [context for why it matters]
- ...

## Nice to Have
- [Bonus qualification]
- ...

## Why Join
[Authentic pitch for the opportunity]

Opening Hook

Good:

We're building the infrastructure that powers modern logistics. As our Staff Engineer, you'll architect the systems that help thousands of drivers deliver millions of packages—and you'll do it with a team that ships fast without cutting corners.

Bad:

We are looking for a highly motivated self-starter to join our growing team.

The hook should answer: Why does this role exist? What's exciting about it?

Responsibilities

Use Action Verbs

✅ "Design and implement API infrastructure serving 10M+ requests/day"
❌ "Responsible for API infrastructure"

Be Specific About Scope

✅ "Own end-to-end development of our mobile checkout experience, from PRD through production"
❌ "Work on mobile features"

Show Impact

✅ "Partner with Sales to build demo environments that close enterprise deals"
❌ "Build demo environments"

Requirements

Minimum List Only

The more requirements, the fewer applicants—especially from underrepresented groups. Research shows women apply when they meet 100% of qualifications; men at 60%.

Focus on Skills, Not Proxies

✅ "Experience building production ML systems"
❌ "5+ years of ML experience" or "PhD required"

Question Every Requirement

• Do you actually filter on this?
• Has someone without this succeeded in the role?
• Is this a proxy for something else you actually need?

The "10 Years Experience" Problem

10 years ≠ competence. What you actually need is often:

• Depth in specific technologies
• Experience at a certain scale
• Demonstrated judgment

Nice to Have

Everything beyond minimum requirements goes here. Make it clear these are bonuses:

• "Bonus if you have experience with Kubernetes, but we'll teach you"
• "Familiarity with our stack (Go, PostgreSQL, React) is helpful but not required"

Inclusive Language

Avoid

• Gendered terms: "guys," "manpower," "chairman"
• Aggressive language: "ninja," "rockstar," "crush it"
• Unnecessary requirements: "native English speaker," "young and dynamic"
• Loaded terms: "culture fit" (use "values alignment")

Use

• "You" over "the candidate"
• Clear, simple language
• Specific skills over personality traits

Degree Requirements

Most roles don't actually require degrees. Consider:

• "Bachelor's degree or equivalent experience"
• Or remove entirely and focus on skills

Common Mistakes

Mistake	Fix
"Must have 8+ years experience"	What skills do 8 years represent?
"Fast-paced environment"	Everyone says this. What's actually fast?
"Wear many hats"	Which hats specifically?
"Competitive salary"	State the range
"Work hard, play hard"	Describes nothing useful
Requirements list > 10 items	Cut to essentials

Tone by Role Level

Level	Tone	Focus
Entry	Welcoming, growth-focused	Learning, mentorship
Mid	Balanced, impact-focused	Ownership, growth path
Senior	Direct, impact-focused	Scope, autonomy, strategy
Leadership	Strategic, mission-focused	Vision, team-building

Remote/Hybrid Clarity

Be explicit:

• Remote: "Fully remote, [timezone expectations if any]"
• Hybrid: "Hybrid: 2-3 days/week in [location]"
• On-site: "Based in [location]"

Don't make candidates guess or wait until the offer to find out.