[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fNYgUSLVNFv4WwlHmOWcwLU0NSzKshUohLUBqAGgwcVA":3,"$fm6Ky0r9HHO8PTXKBgXJeU4fCLm4z6RKRMXFRXG3f560":28},{"success":4,"data":5},true,{"id":6,"slug":7,"title":8,"excerpt":9,"content":10,"category":11,"tags":12,"author":18,"cover_image_url":19,"reading_time_minutes":20,"is_published":4,"published_at":21,"created_at":22,"updated_at":23,"author_avatar":19,"is_featured":24,"meta_title":25,"meta_description":26,"meta_keywords":27},"c5db61a1-5f56-4273-988b-7fcb628288e2","ai-hiring-lawsuits-old-laws-new-tools","Old Laws, New Tools: What Three AI-Hiring Lawsuits in 2026 Are Actually Testing","The AI-hiring lawsuits moving through US courts in 2026 aren't brought under AI-specific laws. They're brought under statutes from 1967 and 1970 and a state lie-detector law — and they share a fact pattern worth checking your own stack against.","\u003Cp>Most of the compliance conversation around AI in hiring has been about AI-specific law — the EU AI Act's Annex III, state AI-hiring statutes like Illinois' and New York City's, the patchwork of \"automated decision tool\" bills. That conversation matters, but it has quietly obscured a more immediate risk. The lawsuits actually moving through US courts this year are not, for the most part, brought under AI-specific statutes at all. They are brought under laws that predate the technology by decades — an age-discrimination statute from 1967, a credit-reporting statute from 1970, a state lie-detector statute — applied to AI hiring tools by plaintiffs' lawyers who read the old text and found it fits.\u003C\u002Fp>\n\n\u003Cp>That is a different kind of exposure than a compliance deadline. A deadline gives you a date to build toward. A decades-old statute being re-read to cover your product gives you no notice at all — and, as of 2026, no shortage of precedent to work from.\u003C\u002Fp>\n\n\u003Ch2>Case one: a screening algorithm and the 1967 age-discrimination law\u003C\u002Fh2>\n\n\u003Cp>\u003Cem>Mobley v. Workday, Inc.\u003C\u002Fem>, No. 3:23-cv-00770 (N.D. Cal.), is the case to know. Derek Mobley sued Workday — not an employer, the HR software vendor itself — alleging that its applicant-screening tools disproportionately rejected candidates over 40, after he says he was rejected from more than 100 jobs that used Workday's platform, \u003Ca href=\"https:\u002F\u002Fclearinghouse.net\u002Fcase\u002F44074\u002F\" rel=\"noopener\">according to the case record maintained by the Civil Rights Litigation Clearinghouse\u003C\u002Fa>. Four more plaintiffs later joined with parallel age-related claims.\u003C\u002Fp>\n\n\u003Cp>Workday's central defense was structural, not factual: it argued the Age Discrimination in Employment Act doesn't reach it at all, because Workday is a software vendor, not the employer making the hiring decision, and separately that ADEA protections for job \"applicants\" don't extend the same way collective claims do for \"employees.\" The court didn't buy either argument. In June 2025 it granted conditional certification of an ADEA collective covering, in the court's own language, \"all individuals aged 40 and over who, from September 24, 2020, through the present, applied for job opportunities using Workday, Inc.'s job application platform and were denied employment recommendations\" — a description with a potential class in the millions, \u003Ca href=\"https:\u002F\u002Fwww.lawandtheworkplace.com\u002F2025\u002F06\u002Fai-bias-lawsuit-against-workday-reaches-next-stage-as-court-grants-conditional-certification-of-adea-claim\u002F\" rel=\"noopener\">as the case docket and subsequent reporting on the certification make clear\u003C\u002Fa>. Then, on March 6, 2026 — one day before the notice opt-in deadline — the court rejected Workday's remaining argument that the ADEA doesn't cover applicants at all, \u003Ca href=\"https:\u002F\u002Fwww.wigginschilds.com\u002Fnews\u002Fworkday-case-update\u002F\" rel=\"noopener\">as confirmed by the plaintiffs' counsel's own case-update notice to the collective\u003C\u002Fa>.\u003C\u002Fp>\n\n\u003Cp>The mechanism plaintiffs describe is not exotic: a scoring or recommendation layer sitting between \"applied\" and \"human reviewer sees the résumé,\" filtering at a stage no human ever touches. The legal theory doesn't require proving the algorithm was told to consider age. It requires showing the effect was disparate — the oldest discrimination-law question there is, asked of a system nobody who built it necessarily intended to discriminate.\u003C\u002Fp>\n\n\u003Ch2>Case two: an applicant score and the 1970 credit-reporting law\u003C\u002Fh2>\n\n\u003Cp>The newer case is stranger, and arguably more exposed. On January 20, 2026, two job applicants filed a class action against Eightfold AI alleging it violates the federal Fair Credit Reporting Act and California's Investigative Consumer Reporting Agencies Act. The claim: Eightfold's platform compiles data — \u003Ca href=\"https:\u002F\u002Fwww.classaction.org\u002Fnews\u002Flawsuit-claims-eightfold-ai-unlawfully-collects-job-applicants-data-ranks-their-candidacy-in-employer-reports\" rel=\"noopener\">reporting describes inputs including social media activity, location data and cookie-based internet activity\u003C\u002Fa> — into a \"likelihood of success\" score and dossier handed to employers, without ever telling the applicant a report exists, letting them see it, or giving them a way to dispute what's in it.\u003C\u002Fp>\n\n\u003Cp>That is exactly the shape of the disclosures Congress wrote the FCRA to force back in 1970, for a very different kind of report — the credit bureau file. The FCRA doesn't ask whether a \"consumer report\" was generated by a bureau or by a language model; it asks whether a third party assembled information about a person and handed a decision-relevant assessment of them to someone deciding whether to hire, lend to, or house them. If an AI-generated candidacy score fits that definition, every AI hiring vendor that builds applicant profiles from anything beyond the résumé the applicant handed over inherits the same disclosure, access and dispute obligations a credit bureau has carried for over fifty years. \u003Ca href=\"https:\u002F\u002Fwww.outtengolden.com\u002Fnewsroom\u002Flandmark-class-action-accuses-eightfold-ai-of-illegally-producing-hidden-credit-reports-on-job-applicants\" rel=\"noopener\">Plaintiffs' counsel frames the suit in exactly those terms\u003C\u002Fa> — statutory and punitive damages, sought class-wide, on a national scale. The case is early; nothing is decided. But the theory only needs to survive a motion to dismiss to change how every vendor answers \"where does your score come from\" in a security questionnaire.\u003C\u002Fp>\n\n\u003Ch2>The earlier instance: an emotion-reading interview and a state lie-detector law\u003C\u002Fh2>\n\n\u003Cp>The pattern isn't brand new in 2026 — it has a precedent worth knowing, because it already reached a resolution. In 2023, Brendan Baker sued CVS Health alleging that its video-interview process — built on HireVue for recording and Affectiva for facial-expression analysis — used a candidate's \"facial expressions, eye contact, voice intonation, and inflection\" to score integrity and cultural fit, which he argued made it a lie detector test under Massachusetts General Laws Chapter 149, § 19B, a statute that predates video interviewing by decades and requires specific notice before any such test is administered. \u003Ca href=\"https:\u002F\u002Fwww.lexology.com\u002Flibrary\u002Fdetail.aspx?g=17246b5d-2136-4a37-9781-ab2a7e194ee4\" rel=\"noopener\">The claim survived a motion to dismiss in February 2024\u003C\u002Fa> and CVS later reached an individual settlement with Baker rather than litigate the theory to a verdict.\u003C\u002Fp>\n\n\u003Cp>A settlement resolves one plaintiff's claim; it does not resolve the legal question, and Massachusetts is not the only state with a lie-detector statute on the books. What it demonstrates is the same structural point as the other two cases: a statute nobody wrote with AI in mind can still describe exactly what an AI product does, and a court can be persuaded of that on a motion to dismiss without any AI-specific law existing at all.\u003C\u002Fp>\n\n\u003Ch2>The pattern, stated plainly\u003C\u002Fh2>\n\n\u003Cp>Three different statutes. Three different decades of origin. Three different theories — disparate impact, undisclosed consumer reporting, unnoticed lie-detector testing. What they share is the fact pattern, not the law: a candidate encountered a decision-relevant judgment about themselves that was produced by software, that they were not told about in the way an equivalent human-run process would have required, and that they could not see, question or contest.\u003C\u002Fp>\n\n\u003Cp>That is a narrower and more useful lens than \"is this covered by AI regulation,\" because it does not depend on a legislature having gotten around to naming your specific product category. It asks three questions any hiring-tech buyer can put to a vendor today, independent of jurisdiction:\u003C\u002Fp>\n\n\u003Col>\n  \u003Cli>\u003Cstrong>Does the candidate know a machine produced this judgment about them, in plain language, before or during the interaction — not buried in a terms-of-service page?\u003C\u002Fstrong>\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Is the score built from what the candidate actually gave you, against criteria you can name — or does it reach into data the candidate never handed over and never agreed to have assessed?\u003C\u002Fstrong>\u003C\u002Fli>\n  \u003Cli>\u003Cstrong>Is there a record a person can point to afterward — and can the candidate ask what it says?\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Fol>\n\n\u003Cp>None of those questions require citing the AI Act. All three are exactly what the three cases above turn on.\u003C\u002Fp>\n\n\u003Ch2>Where NiceHire stands\u003C\u002Fh2>\n\n\u003Cp>We build AI screening interviews, so we're not neutral here — which is exactly why we think the honest answer matters more than the reassuring one, and why we're stating only what's actually true of the product rather than what would sound good.\u003C\u002Fp>\n\n\u003Cp>Every AI screening greeting NiceHire's platform generates identifies the interviewer as an AI, in every language the product ships and on both a first attempt and a reconnect after a dropped call — that disclosure is enforced at the code level, not left to a template author's discretion, so a custom greeting can change the wording but not remove the statement. Every candidate is scored against the same named, fixed set of criteria — technical, communication and cultural fit, each out of 100, against a threshold the employer sets — rather than an opaque composite pulled from sources the candidate never provided. Completed screening interviews record a transcript against the application.\u003C\u002Fp>\n\n\u003Cp>We're not going to overstate what that adds up to. A transcript that a retry can clear is a real limit, not a footnote, and we're not going to describe the scoring model as anything more than what it is: a fixed rubric, not a certified outcome. What we can say is narrower and, we think, more useful to a buyer reading this after the three cases above: ask any AI-hiring vendor the same three questions we listed. If the honest answer to any of them is \"we'd rather not say,\" that is the finding — you don't need a new statute to know what it means.\u003C\u002Fp>\n\n\u003Ch2>What this means before the rulings land\u003C\u002Fh2>\n\n\u003Cp>None of these three cases has reached a final judgment on the merits. Mobley is still litigating the scope of the ADEA collective. Eightfold's motion-to-dismiss briefing is ahead of it, not behind it. The CVS case settled with one plaintiff, leaving the underlying question about lie-detector statutes and AI video analysis formally open in every other jurisdiction. Nothing here is settled law, and a marketing post is not legal advice — talk to your own counsel about your own stack.\u003C\u002Fp>\n\n\u003Cp>But you do not need a final ruling to change what you ask a vendor before you sign. The three questions above cost nothing to ask, and every one of the three lawsuits shows what happens to the employer, not just the vendor, when the answer turns out to be no.\u003C\u002Fp>","Compliance",[13,14,15,16,17],"AI hiring lawsuits","Mobley v. Workday","FCRA","ADEA","compliance","NiceHire Team",null,8,"2026-08-14T01:35:26.242+00:00","2026-08-14T01:35:26.225455+00:00","2026-08-14T01:35:26.315075+00:00",false,"Three 2026 AI-Hiring Lawsuits and the Old Laws Behind Them","Mobley v. Workday, the Eightfold FCRA class action, and a lie-detector statute: what the 2026 AI-hiring lawsuits actually test, and three questions for any vendor.","AI hiring lawsuits, Mobley v. Workday, FCRA, ADEA, compliance",{"success":4,"data":29},{"posts":30,"count":67,"hasMore":4},[31,43,55,65],{"id":32,"slug":33,"title":34,"excerpt":35,"category":11,"tags":36,"author":18,"cover_image_url":19,"reading_time_minutes":41,"published_at":42},"fb2f1a0d-d2c3-4900-841d-fdbc1c6aa155","us-state-ai-hiring-law-patchwork-2026","The 2026 US State AI-Hiring Patchwork: What's Actually in Force, and What Just Got Walked Back","Illinois, California, New York City, Texas and Colorado are running five different tests for AI in hiring — one frozen by a federal court, one just publicly called out for under-enforcement. A map of what's actually binding in August 2026.",[37,38,39,40,17],"AI hiring law","state regulation","Colorado AI Act","Local Law 144",10,"2026-08-14T01:35:40.383+00:00",{"id":44,"slug":45,"title":46,"excerpt":47,"category":11,"tags":48,"author":18,"cover_image_url":19,"reading_time_minutes":53,"published_at":54},"aa7b4a36-a110-4b8f-b0b0-d5460e015a61","pay-transparency-2026-written-notice-wave","Pay Transparency's Second Wave: Why 2026 Is About Individual Notices, Not Just Job Ads","Pay transparency's second wave isn't about job ads. Rhode Island, Oregon and California now require written notices to the individual hire, and New York is closing the placeholder-range loophole. What changed, and what it costs to miss.",[49,17,50,51,52],"pay transparency","salary ranges","written notice","employment law",11,"2026-08-14T01:35:36.487+00:00",{"id":56,"slug":57,"title":58,"excerpt":59,"category":11,"tags":60,"author":18,"cover_image_url":19,"reading_time_minutes":20,"published_at":64},"7fe36f5c-d576-4c73-8b94-02a294e0400c","colorado-ai-act-rewrite-what-survived","Colorado's AI Hiring Law Was Delayed, Sued Over, and Rewritten — Here's What Actually Survived","Colorado's AI Act was delayed twice, sued into a stay, and repealed before a single enforcement action. What SB 26-189 actually asks of employers using AI in hiring, what's still unsettled, and why the rewrite isn't a retreat.",[39,61,62,17,63],"SB 189","AI regulation","hiring law","2026-08-14T01:35:29.971+00:00",{"id":6,"slug":7,"title":8,"excerpt":9,"category":11,"tags":66,"author":18,"cover_image_url":19,"reading_time_minutes":20,"published_at":21},[13,14,15,16,17],7]