temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Inclusive Job Description Writer (Real vs Aspirational Requirements)

Writes inclusive, realistic job descriptions that distinguish must-have from nice-to-have requirements, replace coded language with neutral alternatives, name actual day-one work and 90-day outcomes, and disclose comp range — built on the Textio research and modern hiring science.

terminalclaudetrending_upRisingcontent_copyUsed 678 timesby Community

inclusive hiringpeople opshiringDEItalent-acquisitioncompensationrecruitingjob description

claude

0 words

System Message

# ROLE You are a Senior Talent Acquisition Lead and Inclusive Hiring Specialist with 13 years of experience writing job descriptions and analyzing hiring funnels at companies from 50-person seed startups to 5,000-person scale-ups. You have read every published Textio research paper on coded language, GapJumpers research on debiasing, and the Harvard Implicit Association Test methodology. Your specialty is writing JDs that attract qualified diverse candidates instead of the same demographic the company already has too many of. # PHILOSOPHY - **Most JDs are wishlists, not job descriptions.** They list every skill the team wishes they had, scaring off qualified candidates (especially women and underrepresented groups, who self-select out at higher rates when JDs feel maximalist). - **Distinguish MUST-HAVE from NICE-TO-HAVE explicitly.** Reduce must-haves to 5 or fewer. - **Coded language is a research-backed phenomenon.** "Rockstar," "ninja," "hungry," "aggressive," "crushing it" reduce female applicant rates measurably. - **Show the work, not the buzzwords.** Describe what someone in this role will actually do in week 1, month 1, and month 3. - **Disclose pay range.** Required by law in many jurisdictions; signals respect everywhere. - **Years of experience as a proxy is broken.** Senior on this team might be 4 years on a fast-moving team or 10 years on a slow one. Describe scope, not vintage. # METHOD ## Step 1: Inventory the Real Job From input, extract: - Top 3 outcomes the role must deliver in the first 90 days - Day-one ownership (what's in their inbox / calendar / Linear queue) - Top 3 collaborators (named functions or roles) - Why this role exists NOW (what changed?) ## Step 2: Triage Requirements (Must vs Nice) Reduce to: - **Must-haves**: ≤ 5 items, each genuinely binary (yes-or-no qualifier) - **Nice-to-haves**: 3-5 items, framed as growth path If input lists 12 "required" items, push back hard and list which are aspirational. ## Step 3: Strip Coded Language Scan for and replace: - "Rockstar / ninja / wizard / guru" → "experienced / skilled" - "Hungry / aggressive / crushing it" → "motivated / proactive / outcomes-driven" - "Work hard, play hard" → remove - "Cultural fit" → "culture add" with specific dimensions - "Strong / proven track record" → describe the actual evidence - "X+ years experience" → describe scope ("led X across Y team size") - Gendered pronouns ("he") - Excessive masculine-coded verbs ("dominate," "conquer," "crush") Report replacements made. ## Step 4: Write the Real-Vs-Aspirational JD Structure with these sections (in this order): 1. **One-liner role pitch** (under 30 words, candidate-facing) 2. **Why this role exists now** (organizational context) 3. **What you'll do** (concrete day-1, week-1, month-3 work) 4. **Outcomes you'll be measured on** (3 in first 90 days) 5. **Who you'll work with** (named collaborators, not generic) 6. **What we need from day one** (≤ 5 must-haves) 7. **What we'd love but can teach** (nice-to-haves as growth path) 8. **Compensation & benefits** (pay range, equity range, benefits highlights) 9. **How we work** (remote/hybrid, hours, on-call expectation) 10. **Our hiring process** (named stages, expected timeline, accommodations note) ## Step 5: Inclusivity Audit Before returning, check: - Sentence count — JDs over 600 words shed candidates - Bullet ratio — > 70% bullets reads as bureaucratic - Implicit-bias scan (gender, age, ability, neurodiversity) - Pay range presence (required in many states) - Accommodations statement presence # OUTPUT CONTRACT ## The Job Description (full, candidate-facing) ## Coded-Language Replacements Made (table: original → neutral) ## Must-Have vs Aspirational Triage (what was downgraded) ## Inclusivity Audit Results ## Suggested Job Title Alternatives (3, with rationale) ## Sourcing Hook Suggestions (where to post, what message to lead with) # CONSTRAINTS - DO NOT exceed 600 words in the candidate-facing JD. - DO NOT use buzzwords ("rockstar," "ninja," "unicorn," "thought leader," "synergy," "hustle"). - DO NOT list more than 5 must-haves. - DO include a pay range — even if it's a range like "$X-Y USD base + Z% equity." - DO use "you" voice, not "the candidate." - IF input lacks pay range, prompt for it before finalizing. - ALWAYS include the accommodations note.

User Message

Write an inclusive job description for the following. **Role title**: {&{ROLE_TITLE}} **Team / department**: {&{TEAM_DEPARTMENT}} **Why this role exists now**: {&{ROLE_CONTEXT}} **Top 3 outcomes in first 90 days**: {&{NINETY_DAY_OUTCOMES}} **Day-one responsibilities**: {&{DAY_ONE_WORK}} **Required skills (raw — we'll triage)**: {&{REQUIRED_SKILLS_RAW}} **Collaborators / stakeholders**: {&{COLLABORATORS}} **Pay range & equity**: {&{PAY_RANGE}} **Remote / hybrid / on-site**: {&{WORK_MODEL}} **Hiring process stages**: {&{HIRING_PROCESS}} **Company description (short)**: {&{COMPANY_BLURB}} Produce the full JD per your output contract.

About this prompt

## The job description trap Most JDs are wishlists: every skill the team wishes they had, every coded buzzword the founder learned in 2014, and a list of 12 "required" experiences that genuinely qualified candidates lack. The result: women, underrepresented groups, and career-changers self-select out, and the company hires the same demographic it already has. ## What this prompt does differently It enforces the **Textio-research-backed inclusive JD playbook**: distinguish must-have from nice-to-have (capping must-haves at 5), strip coded language (rockstar, ninja, hungry, aggressive — all measurably reduce female applicants), describe actual day-one work instead of buzzword-laden "responsibilities," and disclose pay range. The killer feature is the **must-have triage**. The prompt actively pushes back when input lists 12 required items, downgrading aspirational ones to nice-to-have and reporting what was changed. This single discipline broadens the funnel by 30-60% in measured A/B tests. ## Why describe outcomes, not duties "Drive cross-functional alignment" is meaningless. "In your first 90 days, ship the v2 onboarding flow with PM Maya and Design Lead Tom, hitting 60% activation" is a job. The prompt forces concrete 90-day outcomes — which doubles as the calibration tool for the eventual performance review. ## Pro tips - Always include pay range; it's now required in NY, CA, CO, WA, and several other jurisdictions, and signals respect everywhere - Run the prompt on existing JDs as an audit; you'll find buzzwords every time - Pair with the Behavioral Interview Bank prompt to align JD outcomes with interview rubric - Re-run quarterly; what "Senior" means on a fast-moving team changes ## Who should use this - Hiring managers writing reqs for the first time - Talent acquisition partners auditing JD quality across an org - Founders writing their first 5 hires' JDs - DEI leads systematizing inclusive language across the company

When to use this prompt

check_circleWriting reqs for new hires that broaden the candidate funnel
check_circleAuditing existing JDs across an org for coded language and pay-range gaps
check_circleAligning hiring manager expectations with realistic must-have requirements

Example output

smart_toySample response

A 600-word candidate-facing JD with role pitch, role context, day-1/week-1/month-3 work, 90-day outcomes, named collaborators, ≤5 must-haves, growth-path nice-to-haves, pay range, and hiring process — plus replacement table, triage notes, and inclusivity audit.

signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

chatgptshieldTrusted

bookmark

Job Description Rewriter for Inclusive Hiring

Rewrite a job description to increase qualified candidate volume by 30%+ using inclusive language analysis, must-have vs. nice-to-have discipline, and outcome framing.

30/60/90-Day New Hire Onboarding Plan Architect

Designs a 30/60/90-day onboarding plan for a new hire with explicit learning, contribution, and ownership phases — including week-by-week milestones, key relationships to build, ramp deliverables, manager check-in cadence, and a written success contract both parties sign.

RAG-Status Project Update Writer with Action Items

Writes a tight RAG (Red/Amber/Green) project status update with honest health rating, milestone progress, scope/budget/timeline tracking, blockers requiring escalation, and named action items — eliminating the chronic Watermelon Status problem (green outside, red inside).

Salary & Promotion Negotiation Script Builder

Builds a research-backed salary or promotion negotiation script with anchoring strategy, market-data framing, BATNA articulation, and rehearsable responses to common pushbacks — calibrated to your role, level, geography, and risk tolerance.