← Back to Issue

Hiring's Algorithmic Blackball

From MyClaw Newsletter · subscribed via aiste.ulozaite@gmail.com · original ↗ · unsubscribe

Stanford-led researchers found AI hiring vendors can turn one bad assessment into repeated rejection, as stored scores follow applicants across employers using the same platform for up to 330 days. Their Pymetrics audit found lost job advances and racial disparities, warning that opaque hiring systems can quietly blackball candidates before any human review, even across unrelated roles.


[

user avatar

](/heynavtoor)

Nav Toor

@heynavtoor

Stanford researchers proved you are not being rejected by 10 companies. You are being rejected by one algorithm 10 times. Your score is stored for 330 days. Every company that uses the same vendor sees the same number. They call it the algorithmic blackball. Researchers at Stanford HAI, Chapman University, and Northeastern University published the largest audit of AI hiring algorithms ever conducted. The paper is called “Algorithmic Monocultures in Hiring.” Published at FAccT 2026, May 26. The data came from Pymetrics, the AI hiring platform used by major Fortune 100 companies. Here is what they found. When you apply for a job at a company that uses Pymetrics, you play a series of assessment games. Your scores are stored. For up to 330 days. If another company also uses Pymetrics, your application is evaluated using the same stored scores. You are not getting two separate evaluations. You are getting the same score twice. If the algorithm rejects you once, it rejects you everywhere. The researchers call this the “algorithmic blackball.” One bad score locks you out of every company that shares the same vendor. You never find out why. You never get a second chance. You just stop hearing back. They ran a large-scale simulation using real applicant data. The result: over 40,000 job advances were lost because applicants who would have succeeded at one company were screened out by an algorithm calibrated for a different one. Then they measured who gets hit hardest. 25.87% of Black applicants were routed into algorithmically discriminatory hiring processes. 14.74% of Asian applicants. These are not hypothetical projections. These are rates measured in deployed, real-world hiring systems used by some of the largest employers on earth. The same algorithm. Applied across companies. Producing the same racial disparities at every one of them. This is already in the courts. Mobley v. Workday is a federal class-action lawsuit alleging that AI hiring tools systematically discriminate against older, Black, and disabled applicants. The case is ongoing. In Europe, the EU AI Act classifies hiring algorithms as high-risk AI systems by default. Compliance requirements take effect August 2, 2026. Weeks away. In the United States, there is no equivalent federal law. The researchers make four recommendations. Measure adverse impact at the position level. Strengthen cross-employer surveillance. Monitor risks from algorithmic concentration. Create legal pathways for independent researchers to access hiring data. The last one carries an implicit warning. This study was only possible because Pymetrics voluntarily shared its data. Most vendors would prefer their algorithms remain opaque. The next time you apply for a job and never hear back, the rejection may not have come from a human. It may have come from a score you received 330 days ago, at a company you have already forgotten, for a role that had nothing to do with the one you just applied to.

7:59 PM · Jun 25, 2026!function(options){var element=document.getElementById(options.targetId);if(!element)return;var cached=document.querySelector(‘[data-timezone]’);var timeZone=cached&&cached.dataset.timezone   Intl.DateTimeFormat().resolvedOptions().timeZone;element.dataset.timezone=timeZone;element.textContent=(function formatFullTimestamp({ timestamp, lang = “en”, timeZone }) { const date = new Date(timestamp); let zone = timeZone; if (zone) try { new Intl.DateTimeFormat(“en”, { timeZone: zone }).format(); } catch { zone = “UTC”; } return `${new Intl.DateTimeFormat(lang, { hour: “numeric”, minute: “2-digit”, timeZone: zone }).format(date)} · ${new Intl.DateTimeFormat(lang, { month: “short”, day: “numeric”, year: “numeric”, timeZone: zone }).format(date)}`; })({timestamp:options.timestamp,lang:options.lang,timeZone:timeZone})}({“lang”:”en”,”targetId”:”_R_dotilid4j6_”,”timestamp”:1782417596000});31.1KViews

23

220

485

299