Skip to content

Domain Atlas

Hiring & employment screening AI

AI that screens, scores, and ranks job applicants — resume screeners, games-based assessments, video-interview scoring, and applicant-tracking-platform recommendation engines. The domain's defining trap is that a screener trained on an organization's past hiring decisions imports the past's selection function: the model learns the history of who was hired, so it reproduces that history's biases as prediction, and patching the named proxies it used does not remove the pattern it learned. Two structural facts shape the governance. The audit lever appears in three configurations — abandoned when a fix proves impossible, adversarially shielded behind legal privilege, or run in an honest but partial form — and there is a blind spot no deployment escapes: rejected candidates never re-enter the outcome data, so every claimed quality or diversity gain is measured on hires only. A single vendor's screening model can operate inside thousands of employers at once, so one learned defect propagates as widely as the platform. The Lab networks model only the deploying organization — its models, recruiters, and hiring records; the applicants being scored sit outside the dynamics, and no candidate outcome is computed on any diagram.

Use cases

What AI is doing here

Resume screening & ranking

Predictive

AI that scores and ranks resumes, typically trained on an organization's past hiring decisions — so it can reproduce the history of who was hired before as a prediction of who will succeed, and patching the named proxies it used does not remove the pattern it learned.

Games-based & video-interview assessment

Predictive

Games-based and video-interview AI assessments that score candidates on measured signals — where the honest form of the audit lever (source-code access, four-fifths-rule de-biasing, retiring low-value inputs) is real but partial, and rejected candidates never re-enter the outcome data.

Applicant-tracking-platform screening

Predictive

AI screening and recommendation features inside an applicant-tracking platform operating across thousands of employers at once — so one learned defect propagates platform-wide, accountability diffuses between vendor and deployer, and bias-testing may exist in a form shielded from external verification.

Case files

What has gone wrong and right

Documented deployments, presented as model organizations calibrated to the evidence, with full citations.

The rule with no number to disclose

United States — Amazon's nationwide fulfilment and sortation network. The adjudicable record runs through state labour regulators (California Labor Commissioner's Office; Minnesota Department of Labor and Industry / Minnesota OSHA), a U.S. Senate Committee on Health, Education, Labor, and Pensions majority investigation, one federal district court class action on the adjacent attendance path (S.D.N.Y., filed November 2025, unadjudicated), an earlier proposed class action dismissed on pleading specificity (N.D. Cal., January 2023), and six state warehouse-quota-notice statutes

Amazon times every task in its fulfilment centres and compares each eligible worker's week against the other workers doing the same job at the same site; the slowest five percent may be disciplined on a ladder that ends in termination. A letter from an attorney for Amazon to a federal labour board described a system that 'automatically generates any warnings or terminations regarding quality or productivity without input from supervisors' and named about 300 workers terminated for productivity at one Baltimore fulfilment centre in thirteen months. Amazon's answer, then and since, is that the terminations are not automatic and that it has no quotas at all — 'individual performance is evaluated ... in relation to how the entire site's team is performing.' Both statements describe the same design. Because the threshold is a share of the site rather than a number, there is nothing fixed to disclose, which is simultaneously the employer's legal defence and two state regulators' finding of violation. What the law built in response is a read right: tell the worker the rule, and give them ninety days of their own speed data. Not a limit on the rule.

Explore this deployment in the PAN Lab →

The account goes dark at nine; the reason arrives on day twenty-six

United States. Amazon Flex is operated by Amazon.com, Inc. and Amazon Logistics, Inc. as a first-party programme with no external vendor; deactivation disputes were routed to individual arbitration under the Flex Terms of Service as reported in 2021. The governance record spans Seattle Municipal Code 8.40 (App-Based Worker Deactivation Rights Ordinance, Ordinance 126878, effective 1 January 2025; administrative rules SHRR Chapter 260 effective 24 June 2025), enforced by the Seattle Office of Labor Standards; Uber Technologies, Inc. v. City of Seattle, Nos. 25-228 and 25-231 (9th Cir. 4 March 2026); Rittmann v. Amazon.com, Inc., No. 19-35381 (9th Cir. 19 August 2020); a Federal Trade Commission settlement of 2 February 2021; District of Columbia v. Amazon under the Consumer Protection Procedures Act (filed 7 December 2022, settled 7 February 2025); Wisconsin unemployment-insurance proceedings final on 26 March 2024; and New Jersey Department of Labor and Workforce Development v. Amazon (Essex County Superior Court, filed 20 October 2025).

Amazon Flex rates its contract drivers into four standing tiers from app telemetry, gates the offer of work on the tier, and ends the account at a threshold by automated email. What makes it an atlas case is the shape of the correction channel rather than the shape of the score: the act is instant and complete, the reasons are thin, the appeal is ten days by email answered in weeks, and the only escalation beyond email carried a filing fee larger than two blocks of net pay. Then, in 2025, one city legislated the correction link back open — notice before the act, the reasons and the specific incidents, all the records relied on, an investigation before the account goes dark, and a challenge that costs nothing — and a federal appeals court left the ordinance standing. The same scorer now runs under two different correction regimes at once, and the scoring rule itself has never been reviewed by anybody, anywhere.

Explore this deployment in the PAN Lab →

Aon pre-hire assessment suite (vendor's own tables)

United States, federal. Aon Consulting, Inc. is the human-capital arm of Aon plc, with a United States address at 200 E. Randolph St, Chicago, Illinois; the assessments are administered globally, in more than 40 languages across 90 countries on the company's own marketing. Two federal forums were opened and neither has produced a public decision. Class-wide charges of discrimination were filed with the Equal Employment Opportunity Commission in late 2023 under the Americans with Disabilities Act and Title VII, against Aon AND an unnamed mid-sized United-States-headquartered client employer, on behalf of a biracial Black and white autistic applicant with mental-health disabilities; those charges cover ADEPT-15 and gridChallenge. A complaint and request for investigation was filed with the Federal Trade Commission on 30 May 2024 under Section 5 of the FTC Act, covering all three products. The federal enforcement environment contracted during the pendency: the EEOC removed its artificial-intelligence hiring technical-assistance guidance in January 2025, and an executive order of 23 April 2025 directed agencies to deprioritize disparate-impact liability enforcement.

A pre-hire assessment vendor administering, on its own marketing, more than 30 million assessments a year across 90 countries sells three instruments into other companies' hiring pipelines: a computer-adaptive forced-choice personality test, a gamified working-memory test, and an asynchronous video product that scores machine transcripts against the personality test's own constructs. What makes this the atlas's unusual hiring case is where the dispute sits. No model here is alleged to have misbehaved. The contested link is between two sets of documents the same company wrote — buyer-facing technical manuals reporting what its own studies measured, and sales pages saying the tools are fair for all and scientifically proven not to have bias. A civil-liberties organisation read the first against the second and took the gap to two federal agencies at once, deception to one and discrimination to the other. Twenty-seven months later the manuals have been pulled from public view, the marketing is unchanged, all three products are still sold, and neither agency has publicly moved. Nothing in this record has been found by any regulator, court or independent auditor, and Aon disputes the claims.

Explore this deployment in the PAN Lab →

Checkr gig-economy background screening

United States, nationwide consumer reporting under the Fair Credit Reporting Act. Checkr, Inc. is headquartered in San Francisco and was founded in 2014. Golightly v. Uber Technologies, Inc. and Checkr, Inc., No. 1:21-cv-03005 (S.D.N.Y., filed 8 April 2021), where the court granted a motion to compel individual arbitration and stayed the claims on 21 December 2022. Davis v. Checkr, Inc., No. 0:26-cv-60088 (S.D. Fla., filed 26 January 2026), pending and pre-certification. Aguilera v. Uber Technologies, Inc. d/b/a Uber Eats, No. 509275/2023 (N.Y. Sup. Ct., Kings County), a platform-side settlement. Regulator surface: the Consumer Financial Protection Bureau's advisory opinions of 4 November 2021 (86 FR 62468) and 11 January 2024 (89 FR 4171; 89 FR 4167), all withdrawn on 12 May 2025, and the Federal Trade Commission, which has acted in neighbouring screening markets but not against this vendor.

Checkr's screening layer sits one company upstream of every gig platform that uses it, and it never deactivates anybody. It retrieves criminal records, matches them to a named applicant against an identity graph it markets as covering 96 percent of United States adults, normalises the charge data, applies each platform customer's own eligibility matrix, and furnishes a report; the platform then fires its own access decision. Three things make this record unlike the others in its domain. The failing component is a shared upstream vendor, so one wrong item is not one wrong decision but a file that travels to every platform sharing it. The correction channel is compulsory rather than discretionary — federal law gives a consumer a reinvestigation within thirty days — and the pleaded adverse action ran the day after the report. And the federal regulator wrote the operating rules for exactly this kind of pipeline between 2021 and 2024, then withdrew all four of them on 12 May 2025 while the statutes underneath stayed in force. Nothing here has been adjudicated against the vendor, and no regulator has taken public action against it.

Explore this deployment in the PAN Lab →

The 1959 statute and the integrity video screen (Baker v. CVS Health)

United States, Massachusetts. Baker v. CVS Health Corporation et al, Civil Action No. 1:23-cv-11483 (D. Mass.), before Judge Patti B. Saris; reported by the Boston Globe on 22 May 2023 and on the federal docket from 30 June 2023. Motions to dismiss denied in their entirety on 16 February 2024; settlement notice filed 17 July 2024; docket termination 22 July 2024; stipulation of voluntary dismissal with prejudice 20 September 2024. The governing statute is Massachusetts General Laws chapter 149, section 19B, enacted in 1959 and amended in 1985 to add the mandatory application notice and a private civil action. The defendants were CVS Health Corporation and CVS Pharmacy, Inc. only; HireVue, Inc. and Affectiva were never parties. The mirrored opinion does not recite an original filing court or removal path, so no origination claim beyond those two dates is made here.

A statute written against the polygraph in 1959 reached an AI hiring screen in 2024, and what it reached it by was a missing sentence. Massachusetts bans lie detector tests in employment and has required since 1985 that every employment application carry a one-sentence notice saying so; the provision then went roughly forty years unenforced. A CVS applicant alleged his application carried no notice and that the HireVue video interview he sat — uploaded, as pleaded, to Affectiva for affect analysis and scored into an employability score — was a lie detector test within the statute's definition. In February 2024 Judge Patti B. Saris denied both of CVS's motions in full: the private right of action reaches the notice provision, and being denied information he had a legal right to was a concrete injury. The defendants were the CVS entities alone; the two companies that built and ran the contested inference were never parties. CVS settled individually and confidentially before any class ruling, so nothing about the technology was ever decided — and the revived statute has since produced more than twenty copycat suits, most alleging only a missing notice.

Explore this deployment in the PAN Lab →

HireVue video assessment (vendor layer)

United States. HireVue, Inc. is headquartered in Utah and incorporated in Delaware; its assessments are deployed by client employers. The November 2019 complaint was filed with the Federal Trade Commission by the Electronic Privacy Information Center and produced no public enforcement action. Biometric-privacy litigation ran in the Northern District of Illinois (Deyerler v. HireVue, Inc., No. 1:22-cv-01284, Judge Jeremy C. Daniel) and then in the Circuit Court of Lake County, Illinois (No. 2026LA00000141, Hon. Daniel L. Jasica). The Illinois Artificial Intelligence Video Interview Act (820 ILCS 42) and New York City Local Law 144 both bind employers rather than the vendor. The March 2025 civil-rights charges were filed with the Colorado Civil Rights Division and the EEOC.

HireVue builds the video-assessment engine; hundreds of separate employers buy it, and every statutory duty that reaches the deployment lands on the buyer. This is the atlas's vendor-layer hiring case, and its record is unusual in three ways: it contains an input that was measured and then retired platform-wide with the arithmetic published, an audit whose narrow perimeter was publicized broadly and whose report is readable only under a nondisclosure agreement, and a mandated-transparency regime that inverted — the vendor holds the data and engages the auditor while the buyers hold the duty and post the result, so the same vendor-level numbers surfaced under four different employers' names. The only channel that ever attached a price was a private biometric-consent class action, and its settlement is preliminarily approved rather than paid, with no admission and no finding by any court or regulator.

Explore this deployment in the PAN Lab →

An internal promotion, a recorded screen, and a captioning request (D.K. charges against Intuit and HireVue)

United States, Colorado and federal. A Complaint of Discrimination was filed on 19 March 2025 with the Colorado Civil Rights Division and the U.S. Equal Employment Opportunity Commission by the ACLU, the ACLU of Colorado, Public Justice and Eisenberg & Baum LLP, on behalf of a complainant identified in the redacted filing by her initials. It names BOTH Intuit, Inc. (headquartered in California) and HireVue, Inc. (headquartered in Utah) as respondents, pleading the Colorado Anti-Discrimination Act (Colo. Rev. Stat. § 24-34-402), the Americans with Disabilities Act and Title VII, and pleading HireVue as an employment agency, an agent of the employer, an indirect employer and an aider and abettor under state law. None of those theories has been tested. Administrative investigations are non-public: no probable-cause determination, dismissal, right-to-sue notice, court filing or settlement had surfaced as of 28 August 2026. The complainant worked for Intuit in Colorado. Colorado's 2024 artificial-intelligence statute is NOT a cause of action here and was not in effect at the events.

A Deaf, Pawnee tax expert had worked five seasons for Intuit, been promoted once, led a team supporting about four hundred associates, earned a bonus every year and been encouraged to apply for the next role by a manager who sat on the hiring team. The employer, in other words, already held years of direct evidence about her. It routed her promotion through a roughly three-hour standardised assessment run on HireVue instead: about a dozen timed recorded video questions plus essay and multiple-choice sections, with instructions delivered audibly. She asked for human-generated real-time captioning. As alleged, she was told the platform's built-in subtitles could be enabled; when the assessment began there was no subtitle option, and she completed three hours of it on browser automatic captions she supplied herself. An automated rejection followed on 13 August 2024, then a feedback message advising her to be more concise, adapt her communication style, and practise active listening. On 19 March 2025 the ACLU, the ACLU of Colorado, Public Justice and Eisenberg & Baum filed a Complaint of Discrimination with the Colorado Civil Rights Division and the EEOC against both companies. Both call the allegations entirely without merit, and HireVue disputes that any AI assessment was used at all. No determination of any kind had surfaced by August 2026.

Explore this deployment in the PAN Lab →

McHire and the 64-million-record custody exposure

United States. McHire is a franchise-wide hiring platform operated for McDonald's and approximately 90 percent of its franchisees by Paradox.ai, a conversational-hiring vendor headquartered in Scottsdale, Arizona; the personality assessment inside the application flow is administered by a further third party, Traitify.com. The disclosure was made by US-based independent security researchers Ian Carroll and Sam Curry on 30 June 2025. No litigation, enforcement action or state attorney-general breach-notification filing tied to this incident was located as of 28 August 2026; the Maine attorney general's breach portal was offline at check time and the California attorney general's published list returned no entries, so that absence rests on searches plus partial registry checks rather than an exhaustive registry sweep. Paradox was acquired by Workday, Inc. under a definitive agreement announced 21 August 2025 and completed 1 October 2025.

The chatbot that screens and schedules applicants for about nine in ten McDonald's franchises had quietly accumulated roughly 64 million application records — names, contact details, and every word applicants typed to the recruiter-bot — behind an admin password of 123456 and an API that never checked who was asking. Two outside researchers found both flaws in a cursory review, and the fix took thirty hours from a single disclosure email, with no regulator anywhere in the story. This is the atlas's custody case: the deployment where the decision path had a human check and the data path had none. What makes it a hiring case rather than a breach entry is what the store held, which is the employment-decision surface itself — who applied where, what they told a recruiting agent, the assessment step they were routed through, and their status history.

Explore this deployment in the PAN Lab →

Meta Job-Ad Delivery: the guardrail and the layer below

United States — federal, nationwide platform. TARGETING LAYER: five coordinated private actions settled 19 March 2019 (National Fair Housing Alliance and three regional fair-housing organizations with Emery Celli Brinckerhoff & Abady LLP; Communications Workers of America; Outten & Golden LLP; American Civil Liberties Union; individual plaintiffs), implemented by 30 September 2019; EEOC reasonable-cause determinations against seven employers announced 25 September 2019. DELIVERY LAYER: United States v. Meta Platforms, Inc., No. 22-cv-5187 (S.D.N.Y.), a Fair Housing Act complaint and court-approved settlement of 21 and 27 June 2022 with court oversight through 27 June 2026. PENDING: EEOC class charge No. 570-2023-00655 (filed 1 December 2022, joined 19 December 2023), Title VII and ADEA, with state and local employment-discrimination laws invoked in parallel.

Civil-rights groups made Facebook strip age, gender and postal-code targeting from every US job ad in March 2019, in five coordinated settlements the company co-signed. Weeks later a peer-reviewed study bought paired ads with identical neutral targeting and measured them arriving at strongly gender- and race-skewed audiences — through the platform's own delivery stage, one layer below where the remedy had landed. The only delivery-layer control with numbers attached, a court-mandated variance controller with four-monthly reporting and an independent reviewer who recomputed the operator's figures to a 0.0 percent difference, is anchored to HOUSING ads; the employment extension is reported by Meta with no published metrics and no verification. The class charge that occupies that gap has been pending before the EEOC since December 2022, the court's oversight clock ran out in June 2026, and the people this screen reaches past never apply anywhere and appear in no record at all.

Explore this deployment in the PAN Lab →

SiriusXM's iCIMS applicant screening

United States — federal. Harper v. Sirius XM Radio, LLC, No. 2:25-cv-12403 (E.D. Mich., Southern Division, filed 4 August 2025), before Judge Terrence G. Berg with referral to Magistrate Judge Anthony P. Patti. Three counts: Title VII disparate treatment (42 U.S.C. 2000e-2(a)), Title VII disparate impact (2000e-2(k)) and intentional race discrimination (42 U.S.C. 1981), on behalf of a proposed class of African-American applicants screened through the platform since 27 January 2024. Administrative predicate: EEOC Charge No. 520-2025-01266, filed 22 November 2024; Determination and Notice of Rights issued by the Newark Area Office on 6 May 2025 making no determination on the merits. Defendant is a Delaware limited liability company headquartered in New York, New York; the plaintiff is in Detroit, Michigan. iCIMS, Inc., the applicant-tracking vendor, is not a party.

Sirius XM Radio licenses iCIMS, a commercial applicant-tracking system, and its AI candidate matching, shortlisting and sourcing features, and one employer stands alone as the defendant for what they are alleged to produce. The vendor is not sued. A Detroit information-technology professional pleads that he applied for about 150 positions in twelve months and was rejected for all but one, that the screening keys on data points proxying for race — educational institutions, employment history and postal codes — and that the platform penalises repeat applications, which he says he tried to defeat by applying from several email addresses. Read the register first, because nothing here has been decided: no court has ruled on the merits, on certification or on the fully briefed motion for judgment on the pleadings that has been under submission since March 2026, and the EEOC closed the charge with an express statement that it makes no determination. Every account of how the screen behaves is one side's pleading, and the employer denies liability.

Explore this deployment in the PAN Lab →

System map

Who is in the system and what pushes on it

Who is in the system

  • Frontline workers. Caseworkers, screeners, eligibility staff — the operator network whose judgment the system augments or erodes.
  • Supervisors & QA. The institutional correction layer: overrides, second reads, quality review.
  • Agency leadership. Owns procurement, policy, and the authority map; answers for the system publicly.
  • Served people & families. Those the decisions land on. Deliberately outside the PAN dynamics — their outcomes are measured, never simulated.
  • Vendors. Build and update the systems; hold the information asymmetry procurement must govern.
  • Regulators & oversight bodies. Boards, auditors, data-protection officers, inspectorates — external correction capacity.

Dominant pressures

  • Workload surge. Demand outruns staffing; per-case attention shrinks and review becomes triage.
  • Reviewer bottleneck. One fixed-capacity checking stage sits between AI output and consequence; everything queues behind it.
  • Vendor opacity. The deploying institution cannot inspect the model, data, or update pipeline it is accountable for.
  • Data & policy drift. The world, the intake process, and the rules change under a system trained on how things used to be — two mechanisms with different remedies: the statistical properties of what the system processes move (concept drift), or the mixture of inputs arriving in deployment differs from the mixture it was trained on (covariate shift).
  • Compliance over substance. Paper controls (sign-offs, checklists) satisfy audits while the behavior they describe erodes.

Governance

Questions leaders should be asking

  1. 1. The screener was trained on the organization's own past hiring decisions — so is it predicting who will succeed, or reproducing who was hired before, and would anyone notice the difference before it locked the past's biases into the future?
  2. 2. Removing a named proxy the model used does not remove the pattern it learned — so is the fix a patch on identified terms, or a design that values exploring candidates the history under-selected, and does the team know the ceiling on term-level fixes?
  3. 3. The audit lever can be abandoned, shielded by legal privilege, or run in a partial honest form — so does an independent party actually see the bias-testing results, or does testing exist in a form no one outside can verify?
  4. 4. Rejected candidates never re-enter the outcome data, so quality and diversity gains are measured on hires only — and when one vendor's model screens for thousands of employers, a single learned defect propagates platform-wide; so who is accountable for the applicants the system never advanced, and across how many employers at once?
  5. 5. Once the screener is live, who holds the authority to switch it off — and who receives a report that it has harmed a candidate, on what clock, and what has to happen next, given that the vendor and the employer can each point at the other?

For the actions behind these questions, see the Practice Library.

Seeing your organization in this domain? Mapping its actual pathways, pressures, and correction capacity is engagement work.

Work With Paramerge

Sources & Evidence

Claims made on this page and what supports them. The full registry lives in Evidence.

ConceptualThe volume's governance chapter places two standing duties on an agency that deploys AI, both distinct from an…

The volume's governance chapter places two standing duties on an agency that deploys AI, both distinct from any pre-deployment approval. First, an incident-reporting protocol that enables timely identification and remediation of algorithmic harm - discriminatory treatment, a biased risk assessment, a misdiagnosis, a breach of confidentiality. Second, transparent channels through which both the people served and the practitioners can report concerns or unexpected effects, so the accountability loop closes after deployment rather than ending at approval. The chapter is a conceptual synthesis and is cited as one: its four-tier social-work risk taxonomy is labeled by its own author as an original construction, informed by but not derived from binding regulation. It may be cited as a framework and must never be presented as a regulatory classification of any deployment in this registry.

huang2026bAcademicSave

Huang, J., Yang, F., & Lee, J. (2026). Ethical Challenges and AI Governance in Social Work. In R. An & M. A. Lindsey (Eds.), Artificial Intelligence in Social Work: Bridging Technology and Humanity. Springer. https://doi.org/10.1007/978-3-032-18443-6_22

doi.org/10.1007/978-3-032-18443-6_22

Appears in: AI in Social Work (Springer, 2026)

Topics: ai-ethics, ai-governance, social-work