INCLUSION · Updated June 19, 2026
Inclusive JDs fill faster and attract more qualified candidates. Here's the language to avoid, the swaps that work, and the structural choices — accommodations, essential vs. preferred, posted pay — that genuinely widen your pipeline.
Inclusion isn't a layer you sprinkle on at the end — it's structural. These five choices, made before you write a single sentence, do most of the work.
PRINCIPLE 01
Years-of-experience proxies and required degrees disproportionately filter out women, career-changers, and underrepresented candidates who can do the work. Lead with the outcome and the demonstrated capability that proves it.
PRINCIPLE 02
Words like "rockstar," "ninja," "crush," "dominate," "aggressive," and "competitive" skew male applicant pools in published research (Gaucher, Friesen & Kay, 2011). Swap them for plain verbs that describe the actual work.
PRINCIPLE 03
Pay transparency narrows the gender pay gap and roughly doubles qualified applicant flow. Posting a good-faith range also signals you've thought about leveling rather than negotiating against the candidate.
PRINCIPLE 04
A one-line accommodations statement, plus a clear breakdown of essential vs. preferred requirements, tells disabled candidates whether the role is actually open to them — without making them ask.
PRINCIPLE 05
Candidates with caregiving responsibilities, disabilities, or hourly day jobs can't absorb open-ended interview loops. Publishing the steps, time commitment, and decision SLA up front evens the playing field.
The most-cited coded phrases in JDs, what to use instead, and the reason each one matters. Sourced from Gaucher et al. (2011) and Textio's published research on hiring language.
| AVOID | USE INSTEAD | WHY |
|---|---|---|
| Rockstar / Ninja / Guru | Senior / Lead / Expert | Hyperbolic titles correlate with male-skewed applicant pools. |
| Aggressive, dominant, competitive | Driven, decisive, ambitious | Masculine-coded; reduces female applications in controlled studies. |
| Strong, fearless, hard-charging | Effective, confident, focused | Same coding issue — describe the behavior, not the persona. |
| Manpower, manhours, chairman | Workforce, work hours, chair | Gendered defaults; modern alternatives are widely understood. |
| Native English speaker | Fluent written and spoken English | "Native" can violate national-origin discrimination rules in the US. |
| Young, energetic, digital native | Curious, fast-moving, comfortable with modern tools | Age-coded language can trigger ADEA risk. |
| Recent graduate, fresh out of school | Early-career, 0–2 years experience | Same age-coding issue; describe the level explicitly. |
| He/she will... | You will... / They will... | Second person is warmer and avoids the gendered binary. |
| Must be able to lift 50 lbs (unless essential) | Omit, or specify when physically required | Non-essential physical requirements screen out disabled candidates unnecessarily. |
| 5+ years experience required | Demonstrated experience [doing the specific work] | Years-of-experience proxies suppress applications from women and career-changers. |
| Cultural fit | Values alignment with [specific value] | "Fit" is a documented vector for affinity bias. |
| Family, tribe, brotherhood | Team, group, colleagues | Familial metaphors deter candidates with healthy work-life boundaries. |
Tap the desktop view for the "why" column, or run any draft through the inclusive-language pass below to flag these automatically.
The single highest-leverage structural change. Splitting requirements into "essential" and "preferred" tells candidates exactly which bars are real — and stops qualified people from filtering themselves out over nice-to-haves.
ESSENTIAL
Things the person genuinely cannot do the job without. Be ruthless — 4–6 max.
PREFERRED
Helpful but not gating. Candidates won't filter themselves out for missing these.
One paragraph at the bottom of every JD. It tells disabled candidates the role is genuinely open and removes the friction of having to ask.
EXAMPLE
RoleHive is committed to building an inclusive team. If you need any accommodations during the interview process — including extended time, alternative formats, or anything else that would help you do your best — email hello@rolehive.ai and we'll arrange it. We hire on what you can do, not how you got there.
Swap in your own email and tweak the voice — but keep the three signals: there's a real channel, accommodations are real, and you hire on capability.
AI INCLUSIVE-LANGUAGE PASS
Even careful writers miss things — "rockstar" sneaks back in, a degree requirement gets pasted from an old JD, the accommodations line goes missing. RoleHive's JD generator runs an inclusive-language pass on every draft, automatically.
RELATED
Pair this with the JD template, the five rules, and the pay transparency checklist for a complete pre-publish workflow.
A JD that doesn't unintentionally screen out qualified candidates based on gender, age, race, disability, or background. It uses plain language, names the work and the outcome, posts pay, and makes the interview loop accessible.
Yes. Textio's research across millions of postings shows that gender-neutral, jargon-free JDs fill roughly 14 days faster and attract a more balanced applicant pool. The marginal effort per posting is small once you have a template.
No — the opposite. Removing hype words like "rockstar" forces you to specify what the person will actually do, which raises the quality of the applicant pool because candidates self-select more accurately.
Use a shared template (see our JD template guide) and run every draft through an automated inclusive-language pass before publishing. RoleHive does this on every generated JD by default.
In the US, language like "young," "recent graduate," or "native English speaker" can support discrimination claims under the ADEA and Title VII even when no discrimination was intended. State-specific pay disclosure rules add another layer.