Job Description Prompts: 20 AI Templates That Attract Top Talent

Write a complete job description for:

ROLE: [JOB TITLE]
LEVEL: [Entry / Mid / Senior / Lead / Director]
DEPARTMENT: [TEAM NAME]
LOCATION: [Remote / Hybrid / Onsite — City, State]
SALARY RANGE: [RANGE or "Competitive"]

COMPANY:
- Name: [COMPANY NAME]
- Industry: [INDUSTRY]
- Size: [EMPLOYEE COUNT]
- Mission: [ONE SENTENCE]

KEY RESPONSIBILITIES (3-5):
1. [RESPONSIBILITY]
2. [RESPONSIBILITY]
3. [RESPONSIBILITY]

MUST-HAVE SKILLS (3-5):
1. [SKILL]
2. [SKILL]
3. [SKILL]

Structure the JD with:
1. Hook — One sentence that makes this role exciting
2. About the Role — What they'll own, who they'll work with
3. What You'll Do — Bullet responsibilities (action verbs, outcomes-focused)
4. What You Bring — Requirements as skills, not years
5. Nice to Have — 2-3 bonus qualifications
6. What We Offer — Benefits, culture, growth
7. How to Apply — Clear next step

Rules:
- Under 600 words
- No gendered language
- No "rockstar/ninja/guru"
- Focus on impact, not credentials
- Include salary range

Write a job description for an executive role:

ROLE: [VP/SVP/C-Level TITLE]
REPORTS TO: [CEO / Board / etc.]
DIRECT REPORTS: [NUMBER AND TYPES]
COMPANY STAGE: [Startup / Growth / Enterprise]
COMPANY SIZE: [$REVENUE or EMPLOYEE COUNT]

STRATEGIC MANDATE:
- Primary objective: [WHAT THIS ROLE MUST ACHIEVE IN 12-18 MONTHS]
- Secondary goals: [2-3 ADDITIONAL PRIORITIES]

BOARD/INVESTOR CONTEXT (if applicable):
[ANY RELEVANT CONTEXT]

Generate:
1. Executive summary (strategic framing, not a job listing)
2. The opportunity — why this role matters now
3. Key responsibilities — strategic, not tactical
4. Ideal candidate profile — experiences and leadership qualities
5. Compensation philosophy (equity, performance incentives)
6. Confidential application process

Tone: Authoritative, strategic, compelling
Length: 400-500 words
Audience: Passive candidates and executive recruiters

Write a technical job description for:

ROLE: [SOFTWARE ENGINEER / DATA SCIENTIST / DevOps / etc.]
LEVEL: [Junior / Mid / Senior / Staff / Principal]
TEAM: [TEAM NAME AND WHAT THEY BUILD]
TECH STACK: [LIST PRIMARY TECHNOLOGIES]

WHAT THE TEAM SHIPS:
[DESCRIBE THE PRODUCT/SYSTEM IN 1-2 SENTENCES]

ENGINEERING CULTURE:
- Deploy frequency: [Daily / Weekly / Biweekly]
- Code review: [PROCESS]
- Testing: [APPROACH]
- On-call: [YES/NO — ROTATION DETAILS]

Generate:
1. The hook — what makes this team's work interesting
2. What you'll build — specific projects and systems
3. Tech stack details — what they'll use daily
4. Requirements — skills and experience (not years)
5. Bonus points — nice-to-haves
6. Engineering perks — learning budget, conferences, open source time
7. Interview process — what to expect (transparency builds trust)

Rules:
- Be specific about the stack (not "modern technologies")
- Describe the problems, not just the tools
- Include team size and collaboration style
- Avoid listing every technology ever invented

Write a job description for a remote/hybrid role:

ROLE: [JOB TITLE]
WORK MODEL: [Fully Remote / Hybrid — X days in office]
TIME ZONE REQUIREMENTS: [SPECIFIC ZONES OR "Flexible"]
ELIGIBLE LOCATIONS: [COUNTRIES/STATES]
OFFICE LOCATION (if hybrid): [CITY]

COLLABORATION MODEL:
- Sync hours: [CORE HOURS, IF ANY]
- Meeting cadence: [DAILY STANDUP, WEEKLY 1:1s, etc.]
- Communication tools: [SLACK, ZOOM, etc.]
- In-person gatherings: [FREQUENCY — quarterly offsites, etc.]

Generate:
1. Opening that highlights remote/hybrid benefits
2. How the team works — async vs sync expectations
3. Responsibilities with remote context
4. Requirements including remote-specific skills
5. What we provide — home office stipend, coworking budget, etc.
6. Time zone and availability expectations (be explicit)
7. How to apply

Address:
- How onboarding works remotely
- Career growth for remote employees
- Team connection and culture building

Convert these experience-based requirements into skills-based requirements:

CURRENT REQUIREMENTS:
[PASTE EXISTING REQUIREMENTS — e.g., "10+ years in marketing"]

ROLE CONTEXT:
- What the person will actually DO day-to-day: [DESCRIBE]
- Key outcomes they need to deliver: [LIST 3-5]
- Team they'll work with: [DESCRIBE]

For each requirement, generate:
1. The skill/ability it actually represents
2. How to phrase it without years
3. Observable evidence a candidate could demonstrate
4. Portfolio/work sample that would prove this ability

Example transformation:
BEFORE: "8+ years of product management experience"
AFTER: "You've shipped multiple products from concept to launch, managed cross-functional teams, and can show measurable impact on user metrics."

Apply this pattern to all requirements.
Flag any requirements that seem unnecessary or exclusionary.

Help me sort these qualifications into tiers:

ROLE: [JOB TITLE]
ALL QUALIFICATIONS FROM OUR WISHLIST:
[PASTE EVERYTHING THE HIRING TEAM WANTS]

Sort into:

TIER 1 — MUST HAVE (can't do the job without these):
- Only include what's truly required from day one
- Maximum 4-5 items

TIER 2 — STRONG PREFERENCE (significant advantage):
- Skills that accelerate ramp-up
- Maximum 3-4 items

TIER 3 — NICE TO HAVE (bonus, not expected):
- Things we can teach or that add extra value
- Maximum 2-3 items

REMOVE — DON'T LIST:
- Qualifications that are unrealistic combinations
- Requirements that screen out diverse candidates
- Skills everyone at this level has (don't waste space)

For each tier, explain WHY it belongs there.
Flag if Tier 1 has too many items (studies show >5 deters applicants).

Audit this job description for inclusive language:

[PASTE FULL JOB DESCRIPTION]

Check for:

1. GENDERED LANGUAGE
   - Words that skew masculine (aggressive, dominant, rockstar)
   - Words that skew feminine (nurturing, supportive)
   - Suggest neutral alternatives

2. AGE BIAS
   - "Digital native" → suggest alternative
   - "Young, energetic team" → suggest alternative
   - Unnecessary degree requirements that exclude experience

3. ABILITY BIAS
   - Physical requirements not essential to the role
   - "Must be able to..." — is it actually required?

4. CULTURAL BIAS
   - "Culture fit" → suggest "culture add"
   - Assumptions about work style or availability
   - Idioms or references that don't translate globally

5. SOCIOECONOMIC BIAS
   - Unpaid internship requirements
   - Prestigious school preferences
   - Unnecessary credential requirements

Provide:
- A marked-up version with all issues highlighted
- A clean, revised version with all changes applied
- A summary of changes with reasoning

Write an equal opportunity and inclusion statement for:

COMPANY: [NAME]
INDUSTRY: [INDUSTRY]
SPECIFIC COMMITMENTS (if any): [e.g., veteran hiring, disability inclusion, etc.]

Generate 3 versions:

VERSION A — STANDARD (legally sound, professional)
- Covers all protected classes
- Meets EEOC requirements
- Clean and direct

VERSION B — AUTHENTIC (shows real commitment)
- References specific programs or initiatives
- Mentions employee resource groups if applicable
- Feels genuine, not boilerplate

VERSION C — BRIEF (for space-constrained listings)
- 2-3 sentences maximum
- Hits the key points
- Links to full policy page

For each version:
- Ensure legal compliance
- Avoid performative language
- Be specific where possible
- Include reasonable accommodation language

Optimize this job title for job board performance:

CURRENT TITLE: [YOUR INTERNAL JOB TITLE]
ROLE LEVEL: [ENTRY / MID / SENIOR / LEAD]
INDUSTRY: [INDUSTRY]
TARGET PLATFORMS: [LinkedIn, Indeed, Glassdoor, etc.]

Generate:
1. 5 alternative titles ranked by search volume
2. For each title:
   - Why candidates search for this
   - Monthly search estimate (relative: high/medium/low)
   - Competition level
   - Click-through appeal

RULES:
- Keep titles under 60 characters
- Include level indicator (Senior, Lead, etc.)
- Avoid internal jargon candidates won't search for
- Don't keyword-stuff

BAD: "Marketing Ninja Level III — Growth Division"
GOOD: "Senior Growth Marketing Manager"

Also flag if the title:
- Doesn't match market expectations for the role
- Could confuse candidates about the actual work
- Differs significantly from competitor listings

Reformat this job description for multiple platforms:

[PASTE FULL JOB DESCRIPTION]

TARGET PLATFORMS:
1. LinkedIn
2. Indeed
3. Company careers page
4. [OTHER PLATFORM]

For each platform, generate:
1. Optimized title (platform-specific best practices)
2. Formatted description (respecting character limits and formatting)
3. Key fields to fill in (location type, experience level, etc.)
4. Tags/skills to select

PLATFORM RULES:
- LinkedIn: 2,000 char limit for mobile display, use bullet points
- Indeed: Structured data fields matter, include salary
- Careers page: Full version with employer brand content

Also generate:
- 3 social media posts to promote the listing (LinkedIn, X, company Slack)
- A referral email template for internal sharing

Create A/B test variants for this job description:

[PASTE JOB DESCRIPTION]

CURRENT PERFORMANCE (if known):
- Views: [NUMBER]
- Applications: [NUMBER]
- Qualified applications: [NUMBER]

Generate 2 test variants that change ONE element each:

VARIANT A — DIFFERENT HOOK
- Rewrite the opening paragraph with a different angle
- Test: impact-focused vs team-focused vs growth-focused
- Keep everything else identical

VARIANT B — DIFFERENT REQUIREMENTS FORMAT
- Same requirements, different presentation
- Test: bullet list vs narrative vs "you might be a fit if..."
- Keep everything else identical

For each variant:
- Hypothesis: why this might improve applications
- What to measure: views, applies, qualified rate
- Minimum sample size: how many views before deciding
- Expected lift: realistic improvement range

Also suggest:
- 3 additional elements worth testing in future rounds
- Which metrics matter most for this role type

Audit this job description across every dimension:

[PASTE FULL JOB DESCRIPTION]

CONTEXT:
- How long has this role been posted? [DURATION]
- Applications received: [NUMBER, if known]
- Quality of applications: [HIGH/MEDIUM/LOW]

Score each area (1-10) and provide specific fixes:

1. CLARITY (is the role well-defined?)
   - Can a candidate picture their first week?
   - Are responsibilities specific or vague?

2. APPEAL (does it excite the right candidates?)
   - Is the hook compelling?
   - Does it sell the opportunity, not just list demands?

3. INCLUSIVITY (does it welcome diverse candidates?)
   - Gendered language check
   - Unnecessary credential requirements
   - Accessibility

4. ACCURACY (does it match the real role?)
   - Overpromising or underselling?
   - Requirements that the team would actually waive?

5. COMPETITIVENESS (how does it compare to market?)
   - Salary transparency
   - Benefits mentioned
   - Growth opportunities

6. SEARCHABILITY (will candidates find it?)
   - Title optimization
   - Keywords present
   - Structure for job board parsing

Deliver:
- Scorecard with all ratings
- Top 3 changes that would have the biggest impact
- Fully rewritten version incorporating all improvements

Compare my job description against competitor postings:

MY JOB DESCRIPTION:
[PASTE YOUR JD]

COMPETITOR ROLE URLS OR DESCRIPTIONS:
1. [PASTE OR DESCRIBE COMPETITOR JD 1]
2. [PASTE OR DESCRIBE COMPETITOR JD 2]
3. [PASTE OR DESCRIBE COMPETITOR JD 3]

Analyze across:
1. Title and positioning — who sounds more appealing?
2. Compensation transparency — who shares more?
3. Requirements bar — who is more/less demanding?
4. Benefits and perks — what are they offering that we aren't?
5. Culture messaging — who tells a better story?
6. Application process — who makes it easier?

Deliver:
- Side-by-side comparison table
- Our strengths vs. competitors
- Gaps we should close
- Specific copy suggestions to differentiate
- An "ideal JD" combining the best of all versions

Convert this internal job specification into a candidate-facing job description:

INTERNAL SPEC:
[PASTE INTERNAL DOCUMENT — may include org charts, salary bands, internal codes, etc.]

RULES:
1. Remove all internal jargon and codes
2. Translate "corporate speak" into human language
3. Keep the essence but change the audience
4. Add selling points the spec doesn't mention

INTERNAL → EXTERNAL TRANSLATIONS:
- "Manages cross-functional stakeholders" → what this actually means day-to-day
- "Drives P&L ownership" → the impact they'll have
- "Band 7, Grade 3" → remove, replace with title clarity
- "Matrix reporting" → describe the actual team structure

Generate:
1. The candidate-facing JD (ready to post)
2. A list of everything removed and why
3. A list of everything added and why
4. Suggested interview talking points for things that were too internal to publish