The Equal Employment Opportunity Commission (EEOC) enforces federal employment anti-discrimination laws that affect every job advertisement published in the United States. While much attention in 2024–2026 has focused on state pay transparency laws, EEOC compliance requirements are equally significant — and the EEOC has been notably more active in scrutinising job posting language since issuing updated guidance in 2024 and 2025.
The required EEO statement
Every job posting should include an Equal Employment Opportunity statement. For non-federal contractors, the standard language covers all protected classes under Title VII, the ADEA, the ADA, and GINA: "We are an equal opportunity employer and do not discriminate based on race, color, religion, sex (including pregnancy, sexual orientation, and gender identity), national origin, age (40 or older), disability, or genetic information."
Federal contractors and subcontractors have additional requirements from the OFCCP, including language covering protected veterans and individuals with disabilities. See our OFCCP checklist for the complete contractor-specific language requirements.
Age discrimination: ADEA traps in job language
The Age Discrimination in Employment Act (ADEA) prohibits discrimination against workers 40 and older. Job posting language that functions as an age proxy creates ADEA exposure even when age is never explicitly mentioned. The EEOC's 2025 enforcement guidance specifically called out several common patterns:
"Recent graduate" or "new graduate preferred." This directly targets workers under a certain age and excludes protected ADEA class members. Replace with "entry-level" or describe the actual experience level sought: "0–2 years of experience in [field]."
"Digital native" or "tech-savvy". While the intent is usually to describe comfort with technology, "digital native" implies a generational identity and can function as an age proxy. Replace with specific technology skills: "Proficient in [specific tools/platforms]."
Maximum experience caps. "1–3 years of experience required" is more legally fraught than "1–3 years preferred." Experience caps can screen out ADEA-protected workers who have more experience than the cap. If experience above a threshold genuinely creates performance concerns (overqualification for growth roles, for example), document the business justification carefully.
Energy and agility language. "High-energy," "fast-paced environment," "agile and adaptable" can function as proxies for younger workers. Replace with behavioural descriptions: "Manages multiple competing priorities effectively" or "Thrives in environments with frequent change and ambiguity."
Degree requirements and disparate impact
The EEOC's 2022 guidance on educational requirements clarified that blanket degree requirements — "bachelor's degree required" for roles where the degree isn't genuinely necessary — can constitute disparate impact discrimination under Title VII if they disproportionately screen out protected racial or ethnic groups and are not proven to be job-related and consistent with business necessity.
The White House's Skills-First initiative and multiple large employer commitments since 2020 have accelerated the move away from blanket degree requirements. From a compliance standpoint, the shift is equally motivated: requiring a degree for a role where equivalent experience is demonstrably sufficient creates Title VII exposure that's increasingly difficult to defend.
Best practice: replace degree requirements with specific skills, knowledge, or experience requirements. Instead of "Bachelor's degree required," write "5 years of demonstrated experience in [specific area] or equivalent combination of education and experience." This is both more inclusive and more accurate about what the role actually requires.
Gender and sex discrimination: language patterns to avoid
Title VII prohibits discrimination based on sex, including pregnancy, sexual orientation, and gender identity following the Supreme Court's Bostock decision. Several language patterns create Title VII exposure:
Gendered role titles. "Salesman," "waitress," "stewardess" — use neutral alternatives. "Sales representative," "server," "flight attendant."
Personality descriptors with gendered associations. "Assertive," "aggressive" (associated with male-coded expectations), "nurturing," "collaborative" (associated with female-coded expectations) can signal preference for candidates of a particular gender. Describe outcomes and behaviours rather than personality traits.
Parental leave and family-status language. Phrases that imply family status preferences ("ideal for someone without family obligations," "requires full availability including evenings and weekends without exception") can create sex discrimination exposure, particularly pregnancy discrimination risk.
National origin and language requirements
English-language requirements are lawful if they are genuinely necessary for the performance of the job — not as a proxy for national origin discrimination. "Bilingual Spanish/English required" is lawful for roles where Spanish communication is a genuine job requirement. "Native English speaker preferred" is not lawful — it discriminates based on national origin without a legitimate job-related justification. The compliant framing is to describe the actual communication requirement: "Must communicate clearly in both written and spoken English with clients and team members."
How EEOC requirements interact with pay transparency laws
A fully compliant job posting in 2026 requires compliance with both pay transparency law requirements (salary range, benefits, bonus in Colorado and Washington; salary range elsewhere) and EEOC requirements (EEO statement, careful language review). These aren't competing frameworks — they're complementary elements of a complete posting. See our pay transparency overview for how to build a posting that satisfies both.
