· 6 min read
How to check a job posting for bias: a step-by-step method
A repeatable way to check a job posting for bias before you publish — what to read for, the five categories that matter, the words that quietly narrow your applicant pool, and how to automate the pass.
Biased wording in a job posting rarely looks like bias. It looks like a normal sentence written by a busy person reusing last year's description. But the words in a posting decide who pictures themselves in the role, and a handful of them can measurably narrow the applicant pool before a single person applies. Here is a repeatable method to check a job posting for bias before it goes live.
Read the posting cold, once, as a stranger
Before you analyze anything, read the whole posting once, straight through, as if you had never heard of the company. Note where you lose interest, where you feel unqualified, and where you would stop reading. That instinct is the signal the rest of the method makes specific. Do this before the checklist, not after — once you start hunting for categories, you cannot un-know them.
The five categories worth checking
Most bias in job postings clusters into five buckets. Check them in order; the earlier ones do the most damage.
Gender-coded language. Research on gendered wording finds that heavily masculine-coded postings draw fewer women applicants. The tell is usually adjectives, not pronouns: "aggressive," "dominant," "rockstar," "ninja," "competitive," "fearless." The fix is almost never to swap in feminine-coded words — it is to describe the actual work. "Aggressive self-starter" usually means "works without close supervision," which is both neutral and more informative.
Age-coded phrasing. "Digital native," "recent graduate," "high-energy," "young and dynamic," and "must be able to keep up with a fast-paced team" all signal an age preference, and several of them carry legal exposure in US hiring. Replace them with the underlying requirement — a specific tool, a specific pace, a specific level of autonomy.
Ableist language and unnecessary physical requirements. "Must be able to stand for eight hours" belongs in a posting only when standing is genuinely essential to the job. Copy-pasted physical requirements are one of the most common ways an otherwise inclusive posting screens people out. Ask of each one: is this the task, or is this how we happen to do the task?
Elitist or credential-inflated requirements. Degree requirements that the role does not need, "top-tier university," "Big Four experience," or a decade of experience for a mid-level job all shrink the pool along lines that correlate with background rather than ability. A useful test: would you reject your best current performer in this role if they applied under these requirements?
Culture language that codes for sameness. "Work hard, play hard," "like a family," and "must be a culture fit" tend to describe the people already there rather than the work to be done. "Culture add" phrasing, or simply describing how the team actually operates, does the same job without the filter.
Check the requirements list separately
Run one pass over the requirements list on its own, out of context. Split it into must-haves and nice-to-haves, and be honest about which is which. Evidence on application behavior consistently suggests that underrepresented candidates are likelier to self-select out when they do not meet every listed requirement — so a long, undifferentiated list of "requirements" functions as a filter even when you never intended it to. If a list has more than about eight hard requirements, it is usually a wish list wearing a requirements label.
Check what is missing, not just what is there
Bias also shows up as absence. A posting with no salary range asks candidates to negotiate from nothing, which reliably widens pay gaps for the people with least leverage. A posting with no mention of flexibility, leave, or accommodation leaves candidates who need those to guess. Omission is harder to spot than a bad adjective because there is nothing on the page to catch your eye — which is exactly why it belongs on the checklist rather than in your memory.
Automate the pass, then use your judgment
A manual read catches the obvious things and misses the repeat offenders, because familiar wording stops registering after the third posting of the day. That is the part worth automating.
Paste your job description into JobAuditor for a free instant audit, or use the job description bias checker if bias is all you want to look at. It scans the text against 60-plus research-backed terms across gender, age, race, disability, and national origin bias, flags a missing salary range, and suggests inclusive swaps — about 30 seconds, no signup.
Treat the output as a prompt for judgment, not a verdict. A flagged word in the right context is sometimes fine, and a clean scan does not make a posting inclusive on its own. The tool is there to make sure nothing obvious survives to publication; deciding what the role actually requires is still the job of the person writing it.
This article is general guidance on job posting practice, not legal advice. Anti-discrimination requirements vary by jurisdiction — confirm the rules that apply where you hire.