mythsthe wider recordMobley v. Workday2025

everyone assumed:

a hiring algorithm is a neutral filter, not a legal liability

what was actually true:

A screening tool does not absorb the legal responsibility for who it screens out.

how it happened

  1. whoAI screeningat very large scale
  2. the gapaggregate patterninvisible to one applicant
  3. the resultcollective actionage discrimination claim certified
the gap that let it happen the result

what everyone assumed

Buying a screening tool is supposed to remove judgment, and removing judgment is supposed to remove bias. A machine does not have a gut feeling about your age. It is a reasonable belief, and it is exactly how these tools are sold and how the procurement decision reads on paper: hand the first cut to software and you have made hiring more consistent, not less lawful.

what happened

The screening ran the way screening runs, quietly, at scale, one application at a time. Workday represented that roughly 1.1 billion applications were rejected through its tools during the relevant period. No single rejection looked like a legal event. The shape only existed in the aggregate, across applicants nobody was comparing to each other, and the aggregate is the one view a single rejected candidate never gets to see.

step by step

  1. AI screening runs at scaleAbout 1.1 billion applications rejected through the tools, Workday said.
  2. the pattern only shows in aggregateNo single rejection looks like a legal event.the assumption breaks here
  3. 16 May 2025collective certification under the ADEAThe court finds a plausible common policy.
  4. July to December 2025HiredScore included, notice plan approvedAllegations only; the case is ongoing.

how it surfaced

Derek Mobley, who alleged he was rejected from a large number of roles, brought a claim that Workday’s AI screening discriminated against applicants over forty under the Age Discrimination in Employment Act. On May 16, 2025, Judge Rita Lin of the U.S. District Court for the Northern District of California granted preliminary collective certification under the ADEA, finding the plaintiff had plausibly shown a common policy with an alleged disparate impact. On July 7, 2025, the court held the collective reached applicants screened by Workday’s HiredScore features, rejecting the argument that HiredScore was a separate, later-acquired product. The court approved a plan to notify prospective collective members on December 2, 2025. These are allegations and procedural rulings, not findings of liability; the case is ongoing and Workday disputes the claims.

A screening tool does not absorb the legal responsibility for who it screens out.

The employer, and potentially the vendor, still own the pattern the tool produces, whether or not anyone is looking at it in aggregate.

picture it at a company like yours

The company here is made up. The other two paths are not: they happened, and each links to the story.

your company
a normal dayYou use software that screens job applicants before a person sees them.
the gap nobody seesNobody looks at who gets screened out in total, only at individual hires.an automated decision nobody reviews
  1. in this story
    the day it mattersA rejected applicant brings a case that the screening is biased.
    what it costs youYou are part of a lawsuit about decisions your team never saw.
  2. or it goes like this
    howA screening rule quietly rejects applicants by age.
    what leavesa discrimination settlementwho ends up with ita regulator acting for the applicants
    it happenediTutorGroup, 2023
  3. or it goes like this
    howA model learns past hiring patterns as signs of quality.
    what leavesa year of skewed decisionswho ends up with itcandidates who never knew why
    it happenedAmazon, 2018

sources

  1. Mobley v. Workday, Inc., Civil Rights Litigation Clearinghouse
  2. Federal Court Allows Collective Action Lawsuit Over Alleged AI Hiring Bias, Holland & Knight
  3. AI Bias Lawsuit Against Workday Reaches Next Stage, Proskauer, Law and the Workplace

← all myths

your turn

what you can do about it

  1. this week

    Ask your team one question about whatever tool screens your applicants: has anyone tested its outcomes across age, and can we see that result.

    Somewhere in your hiring, software is making a first cut, and the people it rejects are receiving a clean, ordinary rejection that reveals nothing about the rule that produced it. The question the quiet months ask is whether anyone on your side has looked at the shape of those rejections, not the individual calls.

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.