Skip to main content

Why this case matters

The Rejected Resumes: what really happens when hiring AI goes wrong

The company in this case is fictional. The failure mode is not. Resume-screening software has rejected real applicants for reasons ranging from learned bias to explicit rules, regulators on two continents have responded, and the courts are still deciding who pays when the machine is the one that said no.

The stakes

Why this case matters

Hiring decides who earns a living. When a scoring model filters resumes before a human ever reads them, it exercises power over people's livelihoods at a scale no single hiring manager ever could. One biased model deployed across thousands of employers can reject the same qualified applicant a hundred times before lunch.

Regulators noticed. The EU AI Act lists AI used to filter job applications and evaluate candidates as high-risk in Annex III, point 4(a). That classification brings conformity assessments, data governance duties, and human-oversight requirements. The Digital Omnibus (Regulation (EU) 2026/1744) moved those obligations to December 2, 2027, which gives deployers a runway, not a pass.

The measurement question is older than the AI Act. US regulators have long used the four-fifths rule: if a group's selection rate falls below 80 percent of the highest group's rate, that is evidence of adverse impact. The Disparity Lens in the game computes exactly this ratio, because it is the number investigators reach for first.

On the record

Verified real-world examples

Amazon's experimental recruiting tool (2014-2017)

Reuters reported in October 2018 that Amazon had built an experimental AI recruiting engine starting in 2014. It scored resumes from one to five stars, trained on patterns in resumes the company had received over the previous decade. Most of those resumes came from men.

By 2015 the team saw the problem: the system had taught itself that male candidates were preferable. It penalized resumes containing the word “women's,” as in “women's chess club captain,” and downgraded graduates of two all-women's colleges. Amazon edited the model to neutralize those specific terms, but engineers could not be sure the machine would not find new proxies. The project was scrapped.

Amazon's position, then and now: the tool was experimental and was never used by recruiters to evaluate candidates. No regulator found otherwise. The case still matters because it is the cleanest public demonstration of the core failure: a model trained on history will reproduce history, including the parts you would not defend.

EEOC v. iTutorGroup: programmed age cutoffs (settled 2023)

In September 2023 the US Equal Employment Opportunity Commission announced a $365,000 settlement with iTutorGroup. The EEOC's lawsuit alleged the company's tutor application software was programmed to automatically reject female applicants aged 55 or older and male applicants aged 60 or older. More than 200 qualified US-based applicants were allegedly rejected because of their age.

This one is different from Amazon's story. There was no learned proxy and no emergent bias. The discrimination was written into the software as an explicit rule. The settlement also brought non-monetary terms: anti-discrimination training, a new policy, injunctions against age and sex discrimination in hiring, and EEOC monitoring for at least five years.

The lesson for the game: not every biased outcome comes from a mysterious model. Sometimes the machine does exactly what it was told, and what it was told to do was, the EEOC alleged, an ADEA violation.

Mobley v. Workday: can the vendor be liable? (pending)

Derek Mobley applied to more than 100 jobs through employers using Workday's recruiting platform and says he was rejected every time, sometimes within minutes. He sued in 2023, alleging the screening tools discriminated based on race, age, and disability.

On June 22, 2026, a federal judge in California largely denied Workday's motion to dismiss, letting claims under California's Fair Employment and Housing Act and the federal Americans with Disabilities Act move forward. The court treated the vendor as a potential agent of the employers using its tools, which means “the vendor's algorithm did it” is not a defense that ends the case early.

Nothing has been proven. The case is in litigation and the discrimination is alleged, not adjudicated. But the procedural ruling already changed the conversation: vendors that build hiring tools may have to answer for them directly, and employers may not be able to outsource the liability along with the software.

From the game

Try the tool from the game

Demo of the Disparity Lens tool: moving the pass threshold changes group pass rates and the impact ratio
The Disparity Lens from Act 1. Move the threshold, drop the proxy feature, and watch the impact ratio move. Synthetic data, computed on your device.

In the classroom

For educators

Run the Disparity Lens before the debrief. Ask students to find a threshold where every group passes the four-fifths rule, then ask what the company gave up to get there. The tradeoff between selectivity and fairness is the whole lesson, and the tool makes it visible in seconds.

For the debrief, put the Amazon case next to the iTutorGroup case and ask which one is easier to prevent. Students usually pick the programmed cutoff. Then ask which one is easier to detect. The answers flip, and that flip is worth the session.

Fiction notice. The Rejected Resumes is a work of fiction: the company, the people, and the incident are invented for teaching. The real-world cases cited above are described as reported by their sources; allegations are allegations, and settlements are not findings of liability.

This game and article are an educational aid, not legal advice, compliance certification, or an audit. Nothing leaves your device: the game runs entirely in your browser.