Job Description Writer

Create inclusive, compelling job descriptions that attract top talent.

When to Use

• Writing a new job description
• Updating an existing role posting
• Making JDs more inclusive
• Optimizing for applicant conversion
• Ensuring compliance with hiring laws

Job Description Structure

Essential Sections

# [Role Title]

## About the Role
[2-3 sentences on impact and team context]

## What You'll Do
- [Responsibility 1 - action verb + outcome]
- [Responsibility 2]
- [Responsibility 3]
- [4-6 total responsibilities]

## What You'll Bring
**Required:**
- [Must-have skill/experience 1]
- [Must-have skill/experience 2]
- [Keep to 4-5 truly required items]

**Nice to Have:**
- [Preferred but not required 1]
- [Preferred but not required 2]

## What We Offer
- [Compensation range]
- [Key benefits]
- [Growth opportunities]

## About Us
[Brief company description + culture]

Inclusive Language Guidelines

Avoid Gendered Language

| Avoid | Use Instead | |-------|-------------| | "He will manage..." | "You will manage..." | | "Manpower" | "Workforce" or "Team" | | "Chairman" | "Chair" or "Chairperson" | | "Rockstar/Ninja/Guru" | "Expert" or "Specialist" |

Avoid Exclusionary Terms

| Avoid | Why | Use Instead | |-------|-----|-------------| | "Young and energetic" | Age discrimination | "Motivated" | | "Digital native" | Age bias | "Proficient with technology" | | "Culture fit" | Can mask bias | "Values alignment" | | "Must have 10+ years" | Often unnecessary | "Significant experience in..." |

Reduce Unnecessary Requirements

Before (exclusionary):

Requirements:
- Bachelor's degree required
- 5+ years experience required
- Must be willing to work 60+ hours

After (inclusive):

Requirements:
- Bachelor's degree or equivalent experience
- Demonstrated expertise in [skill]
- Ability to meet project deadlines with occasional extended hours

Role-Specific Templates

Engineering Role

## What You'll Do
- Design and implement [specific systems/features]
- Collaborate with [teams] to deliver [outcomes]
- Mentor junior engineers and contribute to technical decisions
- Participate in code reviews and improve engineering practices

## What You'll Bring
**Required:**
- Strong programming skills in [languages]
- Experience building [type of systems]
- Ability to break down complex problems
- Clear communication skills

**Nice to Have:**
- Experience with [specific technology]
- Contributions to open source
- Background in [related domain]

Non-Technical Role

## What You'll Do
- Lead [function] initiatives that support [business goal]
- Partner with [stakeholders] to [achieve outcome]
- Develop and maintain [processes/relationships]
- Track and report on [metrics]

## What You'll Bring
**Required:**
- Experience in [function/industry]
- Strong analytical and communication skills
- Ability to manage multiple priorities
- Collaborative approach to problem-solving

Compensation Transparency

Best Practices

## Compensation
- Base salary: $X - $Y (based on experience and location)
- Equity: [X shares / $Y value]
- Bonus: Up to X% of base salary
- Benefits: Health, dental, vision, 401k matching

Location: [Remote / Hybrid / On-site in City]

Legal Requirements by Location

| Location | Requirement | |----------|-------------| | California | Must include salary range | | Colorado | Must include salary range | | New York City | Must include salary range | | Washington | Must include salary range | | Connecticut | Must provide on request |

Quality Checklist

• [ ] Role title is clear and searchable
• [ ] Responsibilities focus on outcomes, not tasks
• [ ] Requirements distinguish must-have vs nice-to-have
• [ ] Language is gender-neutral
• [ ] No unnecessary degree requirements
• [ ] Years of experience are reasonable
• [ ] Salary range is included (where required)
• [ ] Company culture is authentically represented
• [ ] Application process is clear

SEO Optimization

Title Best Practices

• Use standard job titles (searchable)
• Include level (Senior, Lead, Principal)
• Avoid internal jargon

Good: "Senior Software Engineer - Backend" Bad: "Code Wizard Level III"

Keywords to Include

• Role-specific skills
• Industry terms
• Tools and technologies
• Team/department name

Best Practices

1. Lead with impact - What will this person accomplish?
2. Be specific - Vague JDs attract vague candidates
3. Keep it scannable - Bullets, not paragraphs
4. Show growth - Where can this role lead?
5. Be honest - Overselling leads to turnover
6. Update regularly - Stale JDs attract wrong candidates