/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Tests show GPT-3.5 and GPT-4 systematically produce biases that disadvantage protected groups, based on their names, when screening and ranking job candidates

Recruiters are eager to use generative AI, but a Bloomberg experiment found bias against job candidates based on their names alone

Bloomberg

Context & Ripple Effects

This finding extends a longer record of automated employment tools creating unequal outcomes: earlier coverage found that algorithmic application screening could disproportionately exclude poorer applicants (algorithmic hiring screens that penalized poorer applicants).

It also puts a hiring-specific test alongside evidence that generative systems can amplify demographic stereotypes in job-related imagery (stereotypes in AI-generated job imagery), despite OpenAI having used external experts to probe GPT-4 for prejudice and other risks before release (pre-release bias testing for GPT-4).

First-order effects

  • Recruiters using GPT-3.5 or GPT-4 to screen or rank applicants face an immediate risk that name signals, rather than job-relevant qualifications, influence candidate treatment.
  • The results give employers a concrete reason to pause or constrain automated ranking workflows and test outputs before they shape hiring decisions.

Second-order effects

  • AI hiring-tool buyers are likely to demand auditable evaluations and human review controls from vendors, shifting deployment risk from a model demo to the employer's operating process.
  • Model providers and recruitment-software vendors face pressure to show whether mitigations hold in high-stakes workflows, not merely that a general-purpose model can generate useful text.

Third-order effects

  • If organizations continue adopting general-purpose models in employment decisions, hiring may become a leading test case for operational AI governance: documented evaluation, escalation paths, and accountability for outcomes.
  • The broader shift is from treating model bias as a pre-release safety issue to treating it as a deployment-control problem shared by model makers and the organizations that use them.

The trend: Generative AI is moving into consequential workplace decisions faster than governance practices can establish whether automated outputs are equitable and accountable.

Discussion

  • @leonyin Leon Yin on x
    New: Employers and HR vendors are using AI chatbots to interview and screen job applicants. We found that OpenAI's GPT discriminates against names based on race and gender when ranking resumes. W/ @daveyalba and @Leonardonclt gift link: https://www.bloomberg.com/... [video]
  • @daveyalba Davey Alba on x
    NEW with @LeonYin @Leonardonclt: Ever since the advent of ChatGPT in late 2022, there's been so much excitement for generative AI across industries. We wanted to ask—is there a risk of racial bias in generative AI being used for hiring and recruitment? https://www.bloomberg.com/.…
  • @cameronwilson @cameronwilson on x
    I'm sure everyone up in arms about Google Gemini's image generation will be equally incensed (or perhaps more because of the real world impact) that OpenAI's racial discrimination in suggesting hiring candidates, right?
  • @rachelmetz Rachel Metz on x
    Please read this extremely in-depth investigation about racial bias in GPT 3.5 and 4 from @LeonYin, @daveyalba, and @Leonardonclt!
  • @leonardonclt Leonardo on x
    🚨Read this before you use OpenAI for Hiring🚨 @LeonYin @daveyalba and I ran thousands of resume screening tests with GPT-3.5 and GPT-4 and found that the tech will racially discriminate applicants based only on their name. Serious implications. 🧵 1/10 https://www.bloomberg.com/...…
  • @f_j_j_ Francis Jervis on x
    I'm slightly surprised by these results, but still important to bear in mind this would be a prohibited use case for GPT-3.5 (or any OpenAI model, or for that matter any sensible co's, including open licenses).
  • @jon_ayre Jon Ayre on x
    No surprises here, either in the intrinsic biases in AI models or in the fact that recruiters are using it anyway. I wrote a post about both issues: https://jonayre.uk/...