HR AI Skill

Job Description Generator

Write, optimize, and publish job descriptions. Use when creating new JDs from approved requisitions, rewriting existing descriptions for clarity or inclusivity, localizing for specific regions, generating platform-specific variants (LinkedIn, Indeed, Glassd...

Job Description Generator

Create compelling, compliant, and conversion-optimized job descriptions that attract the right candidates.

Workflow

  1. Load the approved requisition data (title, team, level, location, comp range, must-haves).
  2. Enrich with context: pull 2–3 similar past roles from the org to understand scope, review successful hire profiles for pattern matching, check team page for culture signals.
  3. Draft using the structure below — lead with impact, not duties.
  4. Run the inclusivity audit (see checklist).
  5. If multi-region: localize comp ranges, benefits mentions, legal disclosures, and work-authorization language per jurisdiction.
  6. Generate platform-specific variants with character limits and formatting rules.
  7. Produce JSON-LD structured data for SEO.
  8. Route to hiring manager for final review before publish.

JD Structure Template

[Job Title] — [Team] — [Location / Remote Policy]

## About [Company]
One sentence on mission. One sentence on culture differentiator.
No boilerplate — make it specific.

## Why This Role Exists
Two paragraphs. First: the business problem this role solves.
Second: the impact a great person would have in 12 months.
Connect the role to company goals, not just team needs.

## What You'll Do
5–7 bullets. Action-oriented, specific outcomes.
Format: "You will [verb] [specific thing] to drive [measurable outcome]."
Avoid generic bullets like "work collaboratively with cross-functional teams."

## What We Need
### Required (4–6 items)
- Specific skills, tools, years of experience
- Lead with the non-negotiables
- Label degree requirements as "or equivalent experience"

### Preferred (3–5 items)
- Nice-to-haves that differentiate great candidates
- Label as "Bonus if you have..." or "Nice to have"

## What We Offer
- Compensation range: [$X–$Y] [currency] [frequency]
- Equity: [if applicable, range or "competitive"]
- Benefits: health, dental, vision, 401(k) match, PTO policy
- Learning & development: [stipend, conference budget, internal mobility]
- Work setup: [remote stipend, equipment, flexible hours]

## Our Process
Brief timeline: Application → Phone Screen → Technical/Case → Team Interview → Offer
Typical timeline: 3–4 weeks from application to offer

## How to Apply
One clear CTA. Link or email.
Optional: "No agencies, please" if applicable.

## EEO Statement
[Company] is an equal opportunity employer. We celebrate diversity
and are committed to creating an inclusive environment for all employees.
[Add state-specific disclosures if required: CA, NY, CO, WA, MA, IL]

Title Optimization Rules

Inclusivity Audit Checklist

Before publishing, verify every item:

Platform Variant Rules

| Platform | Max Chars | Formatting | Tips | |----------|-----------|------------|------| | LinkedIn | 20,000 | Rich text, bullets | Use hashtags in first comment | | Indeed | 15,000 | Plain text blocks | Keyword-stuff naturally for search rank | | Glassdoor | 10,000 | HTML-ish | Emphasize culture, salary transparency, reviews | | Wellfound | 5,000 | Markdown | Mission-first tone, equity details | | GitHub Jobs | 3,000 | Markdown | Stack-specific, link to repos | | Company Careers | Unlimited | Full HTML | Most detailed version, embed videos |

JSON-LD Structured Data

Generate JobPosting schema for the careers page:

{
  "@context": "https://schema.org/",
  "@type": "JobPosting",
  "title": "Senior Software Engineer",
  "description": "Full JD text here...",
  "employmentType": "FULL_TIME",
  "hiringOrganization": {
    "@type": "Organization",
    "name": "Company Name",
    "sameAs": "https://company.com"
  },
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "San Francisco",
      "addressRegion": "CA",
      "addressCountry": "US"
    }
  },
  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": {
      "@type": "QuantitativeValue",
      "minValue": 140000,
      "maxValue": 180000,
      "unitText": "YEAR"
    }
  },
  "datePosted": "2025-01-15",
  "validThrough": "2025-04-15"
}

Localization Rules

When localizing for a new region:

  1. Compensation: Convert to local currency, adjust for cost-of-living index (use Payscale/O*NET data)
  2. Benefits: Replace US-specific benefits (401k) with local equivalents (pension, superannuation, etc.)
  3. Legal disclosures: Add region-specific equal opportunity language, data privacy notices (GDPR in EU)
  4. Work authorization: Adjust visa sponsorship language per local immigration law
  5. Date/time formats: Localize (DD/MM vs MM/DD), timezone mentions

Edge Cases