Most job postings read like they were assembled by committee, because they were. Legal added compliance language. Marketing added company mission. HR added the required qualifications list. The hiring manager added their wish list. The result is usually 2,000 words of bloat that discourages the candidates the company actually wants to attract. Writing a good job posting in 2026 is partly a writing problem, partly a compliance problem, and partly an organizational-discipline problem. The best postings are shorter than most, more specific than most, and run through a review process that balances all four stakeholder perspectives.
What a Modern Job Posting Should Include Core sections: a clear role title (no internal jargon), a two to three sentence summary of what the role does and why it exists, the three to five most important responsibilities, required qualifications (genuinely required, not wish-list), preferred qualifications, pay range (required in an increasing number of states), benefits summary, location and work arrangement (remote, hybrid, on-site), and an EEO statement.
Skip the 14-bullet responsibilities lists, the "company culture" paragraphs that could apply to any company, and the passive-voice compliance language that obscures rather than clarifies. The best postings read like a hiring manager wrote them, not a template.
State Pay Transparency Laws Apply to Most Postings in 2026 A dozen states plus DC now require pay ranges in job postings, and the list has been growing annually. California, Colorado, Connecticut, Hawaii, Illinois, Maryland, Minnesota, Nevada, New York, Rhode Island, Washington, and DC all have some version of pay transparency law as of 2026. Each has specific requirements, but most share the same core: employers must disclose the hourly or salary range the employer in good faith expects to pay for the position.
The laws apply to postings visible to candidates in those states, which for remote roles means most postings. Enforcement has been active, with multi-state employers facing fines and class-action lawsuits over missing or sham pay ranges.
What About Job Postings That Just Say "Competitive Salary"? In states with pay transparency laws, that language is non-compliant and has been penalized. In states without pay transparency requirements, it's technically legal but undermines trust and depresses application quality. Candidates are far more likely to apply to postings with specific ranges.
Language That Inadvertently Signals Bias Research on job posting language has found consistent patterns. Terms like "rockstar," "ninja," and "aggressive" skew male applicants. "Young," "energetic," "digital native" skew younger applicants. "Must be physically able to" without specific essential function reasoning can invite ADA claims. Required qualifications that aren't actually required ("10+ years experience" for a mid-level role) filter out qualified candidates and can produce disparate impact.
Scrub postings for coded language that signals demographic preferences. Focus qualifications on actual job requirements, not accumulated assumptions. Use tools that flag gendered or ageist language if your volume warrants them.
Running a Job Posting Program That Attracts the Right Candidates Start with the internal job description and distill rather than expand. A strong posting is typically 300 to 500 words, not 1,500. Include the pay range, the EEO statement, and the necessary compliance language, but don't let those elements dominate.
Distribute beyond your ATS and career site. Pair with job bank listings, applicant tracking system integrations, and relevant industry boards. Tie the posting workflow to recruitment and talent acquisition processes so every posting uses the current approved template. Reference EEOC guidance on non-discriminatory language at eeoc.gov/employers and DOL pay transparency resources at dol.gov. The postings that consistently produce the best hires are the ones written specifically for the audience, not the ones edited into committee-safe blandness.
.svg)
.svg)
