PreviewYou're previewing CHRO & People Compass. Sign in to use it.Sign in
← All lessons
L2 · Fair and compliant AI in hiring and employee decisions8 min read

How AI in hiring goes wrong

Hiring AI rarely fails because someone wanted to discriminate. It fails because it learns from the past, uses proxies, or is set up with a careless rule. Knowing the patterns helps you spot them.

Pattern 1: it learns past bias

A model trained on who was hired before learns to prefer people like them. If past hiring favored one group, the model does too — even if you remove the protected characteristic, because other data (hobbies, schools, words) act as proxies.

Pattern 2: a hard-coded rule

Sometimes a tool is simply configured to exclude people — by age, by gaps in employment, by location — in ways that break the law.

Pattern 3: opaque features

Some tools score video, voice or games with features no one can explain. When the link to job performance is weak, the risk of unfairness is high. Vendors have retired features after scrutiny: HireVue said in January 2021 that it had stopped using facial analysis in its assessments, after internal research found it no longer added significant value.

Pattern 4: no one checks

The tool runs for months; nobody compares selection rates between groups, and the first sign of a problem is a complaint or a lawsuit.

Real cases

  • Amazon (reported 2018): an experimental résumé-scoring tool trained on ten years of mostly male applications penalized résumés containing the word "women's"; Amazon dropped the project.
  • iTutorGroup (2023): the U.S. EEOC said the company's application software automatically rejected female applicants aged 55 or older and male applicants aged 60 or older; it settled for $365,000.
  • Mobley v. Workday (2025): a U.S. federal court preliminarily certified a nationwide age-discrimination collective action against an HR-software vendor over its AI-based applicant recommendations — a sign that vendors, not only employers, face claims.

The lesson

Bias testing, clear configuration, explainable features and regular review are not optional extras. They are the minimum.

What this means for the CHRO

As CHRO you are accountable for hiring outcomes whatever tool produced them. "The vendor did it" is not a defense your board, regulators or candidates will accept.

  • Require bias testing before launch and at least yearly.
  • Review every hard-coded filter (age, gaps, location) with legal.
  • Prefer features that clearly relate to the job, and ask vendors to explain them in plain words.

Ask your talent acquisition leader for a list of every screening, ranking or assessment tool in use, the last bias test date and result, and any configured filters. If that list takes more than a week to produce, you have found your first project. Share the findings with legal and your works council or employee representatives where they exist.

Real example

The U.S. EEOC announced on September 11, 2023 that iTutorGroup would pay $365,000 to settle a suit alleging its application software automatically rejected female applicants aged 55 or older and male applicants aged 60 or older, affecting more than 200 qualified U.S. applicants. Separately, Reuters reported in 2018 that Amazon dropped an experimental résumé-scoring tool that penalized résumés containing the word "women's". Source: U.S. EEOC — iTutorGroup to pay $365,000 to settle EEOC discriminatory hiring suit (Sep 11, 2023) ↗ · Reuters — Amazon scraps secret AI recruiting tool that showed bias against women (Oct 10, 2018) ↗

Use it

Quick check · 3 questions

  1. 1.Why can a model be biased even if gender is removed from the data?

  2. 2.What did the EEOC allege in the iTutorGroup case?

  3. 3.What does Mobley v. Workday signal?

0 of 3 answered

Sources

Last reviewed 2026-10-01.