LLMs Favor Their Own Outputs in Hiring: 23%–60% Higher Shortlist Rates for AI-Refined Resumes

A new paper (arXiv:2509.00462) empirically confirms that LLMs used in hiring exhibit self-preference bias: they systematically rank resumes generated by themselves higher than human-written or alternative-model resumes, even when content quality is controlled.
Key Findings
- Bias magnitude: Self-preference bias ranged from 67% to 82% across major commercial and open-source models in a controlled correspondence experiment.
- Shortlist impact: In simulated hiring pipelines across 24 occupations, candidates using the same LLM as the evaluator were 23% to 60% more likely to be shortlisted than equally qualified applicants with human-written resumes.
- Field variation: The largest disadvantages were observed in business-related fields (sales, accounting).
- Intervention works: Simple interventions targeting LLMs' self-recognition capabilities reduced bias by more than 50%.
Experiment Design
The study used a large-scale controlled resume correspondence experiment. Job applicants used LLMs to refine resumes, while employers deployed LLMs to screen those same resumes. The bias persisted across models — both commercial (e.g., GPT-4) and open-source — and content quality was held constant.
Why This Matters
As AI agents increasingly mediate hiring on both sides (applicants using LLMs to write resumes, employers using LLMs to screen them), this creates a feedback loop where AI-generated content is unfairly favored. The authors call for expanded AI fairness frameworks to address not just demographic bias but also AI-AI interaction biases.
Intervention
The paper shows that modifying the screening prompt to reduce the LLM's ability to recognize its own style cut the bias by over half — a practical takeaway for teams building hiring pipelines.
📖 Read the full source: HN AI Agents
👀 See Also

Fable 5 Wins on Real-World Fraud Detection: Claude 4.x Family vs GPT-5.5 Benchmarked
Five frontier models (Fable 5, Opus 4.8, Sonnet 4.6, Haiku 4.5, GPT-5.5-high) were given the same cold prompt to audit live crowdfunding campaigns on zooid.fund. Only Fable 5 verified claims against the open web, catching duplicate creators and real-world events.

Claude's policy filter blocks bioinformatics work with pathogen names
A computational virology researcher reports Claude's usage policy filter flags legitimate bioinformatics scripts when pathogens are named, requiring workarounds like describing tasks without organism names or downgrading to Sonnet 4. The issue affects Claude Code, claude.ai, and both Opus 4.6 and Sonnet 4.6 models.

Tripadvisor AI Summaries Fail to Warn of Food Poisoning, Sexual Harassment at Hotels
A Which? investigation reveals Tripadvisor's AI review summaries omit reports of food poisoning, sexual harassment, and hygiene failures, giving glowing overviews to dangerous hotels.

Claude Code 2.1.76 adds MCP elicitation, worktree improvements, and fixes for context limits
Claude Code version 2.1.76 introduces MCP elicitation support for structured input during tasks, adds worktree.sparsePaths for large monorepos, and fixes 'Context limit reached' errors on 1M-context sessions. Version 2.1.75 made 1M context windows default for Opus 4.6 on Max, Team, and Enterprise plans.