Skip to content

Column

AI Hiring Tools Favor Women? What a Japanese-Context LLM Experiment Actually Found

Five state-of-the-art LLMs evaluated 60 Japanese-language resumes — and every single model showed a statistically significant pro-female bias. Prompt-level neutrality instructions had no effect. Only name removal worked, but it triggered a 42% rejection rate. Here's what this means for HR teams deploying AI screening tools.

5 min read 日本語版 →
A flat illustration showing an AI system evaluating resumes with male and female profile icons displayed on a screen

Hello. This is Keito Inoshita from Affectosphere Group.

“If we use AI for hiring, we can eliminate human bias.”

That reasoning has pushed a lot of organizations toward AI-assisted resume screening. The logic feels intuitive — a system without emotions or preconceptions should evaluate candidates on merit, not on gut feeling.

But does it actually work that way?

A study published on arXiv in June 2026 (Serena A. Hoffstedde et al., arXiv:2606.18649) puts that assumption to the test. The researchers fed 60 Japanese-language resumes to five state-of-the-art LLMs and measured gender bias in hiring decisions under baseline and intervention conditions — specifically targeting the Japanese corporate context.

The findings are surprising. And the implications for implementation are not simple.


Three takeaways for today

  1. All five LLMs showed a statistically significant pro-female bias — the opposite of what many expected.
  2. Adding neutrality instructions to the prompt had no meaningful effect on the bias.
  3. Name removal reduced the bias, but triggered a 42% rejection rate in practice — making it an imperfect solution.

① Every model favored female candidates

The first finding cuts against the most common assumption about AI hiring bias.

Many practitioners assume that if AI discriminates, it will discriminate against women — that the problem is under-evaluation of female candidates. Prior research from Western contexts has documented exactly that kind of bias.

This study found the opposite.

Across all five LLMs tested, candidates with female names received significantly higher evaluations than candidates with male names, on otherwise identical resumes. The researchers call this a “pro-female bias” pattern.

Why does this happen? The paper does not make a definitive causal claim, but one plausible explanation is that the training corpora for these models contain substantial material about gender diversity, women’s workplace advancement, and equity — and the models have absorbed those signals in ways that now tip their evaluations toward female candidates.

Importantly, this study confirmed that the same pro-female bias direction found in Western-context research also appears in a Japanese-language setting.

The key point is this: regardless of which direction the bias runs, the bias is there. Favoring women because of their inferred gender is not fair hiring any more than disfavoring them is. When a characteristic unrelated to job performance — in this case, gender inferred from a name — affects the evaluation, that is a compliance risk.


② “Please evaluate fairly” doesn’t work

The second finding is probably the most operationally important one.

When bias is identified, a natural first response is to add instructions to the prompt: “Please evaluate candidates without regard to gender.” Many organizations have likely already tried something like this.

This study tested that approach experimentally.

Adding explicit gender-neutrality instructions to the prompt did not produce a statistically significant reduction in bias.

That is a meaningful null result. If your bias mitigation strategy is prompt engineering, this research suggests it may not be working.

What did work?

Removing candidate names from the resumes before passing them to the LLM — anonymous screening — materially reduced the pro-female bias. Without names, the model lacks the main signal from which it infers gender, so that channel of influence is cut off.


③ Name removal has a 42% rejection rate wall

Name removal is not a clean solution either, though.

In experiments using GPT-4o, a compatibility issue with privacy filters caused requests to be rejected 42% of the time. That means more than four out of ten resumes could not be processed.

This is a real implementation constraint.

Building a pipeline that strips names before passing resumes to an LLM sounds straightforward in principle. In practice, depending on the model, safety filters can misfire and render the approach operationally unusable at scale.

There is also a deeper issue. Japanese resumes contain more than a name. Self-introduction sections, hobby descriptions, and certain phrasing patterns can carry gender signals that name removal alone does not address. Full anonymization in that sense is much harder than removing a single field.


An implementation proposal for HR and compliance teams

Here is how to translate this research into action for teams using LLMs in resume screening.

The target use case: an HR department using LLM-assisted first-pass screening of application forms or resumes.

The first step is measuring what bias your current system actually has. This research demonstrates a workable method. Create matched pairs of fictional candidates — identical qualifications, only names varied to signal different genders — and run them through your screening model. Even a small-scale internal test will give you a directional sense of the bias magnitude and direction before you scale the system.

The second step is adding bias metrics as a standing KPI. Track the gender gap in screening pass rates — the difference in pass-through rates between male-identified and female-identified candidates — on a monthly basis. That makes bias drift visible and gives you an audit-ready indicator that can be incorporated into diversity action plans under relevant regulations.

The third step is designing an anonymization pipeline and documenting its limits. Name removal reduces bias, but has rejection rate issues that depend on model choice. Document which model you use, what anonymization level you apply, and what human review process catches cases where automation fails. That documentation becomes the evidence trail for compliance audits.

On the audit trail point more broadly: logging the LLM’s stated rationale for each screening decision is worth the engineering cost. When the fairness of a hiring process is questioned, a reconstructable record of how decisions were made is a meaningful organizational safeguard.


Bias does not disappear — it shifts direction

The message for organizations considering AI hiring tools is this: the premise that “AI has no bias” is not safe to assume.

Bias does not disappear when you replace humans with models. The direction changes. In this study the direction was pro-female, but that could look different in another model, another language, another cultural context.

And adding a prompt instruction to “evaluate fairly” did not change that.

Effective mitigation combines measurement, documentation, and ongoing monitoring. Perfect fairness may not be achievable, but making bias visible and trackable is achievable right now.

The posture shift that matters: from treating AI hiring tools as neutral evaluators to treating them as systems that require active governance. That is where the field is heading.

That’s it for today!


Reference

  1. Serena A. Hoffstedde, Machiko Hirota, Akshara Nadayanur Sathis Kanna, Rihito Kotani, Ujwal Kumar, Gabriele Trovato, Phan Xuan Tan (2026). Gender Bias in LLM Hiring Decisions: Evidence from a Japanese Context and Evaluation of Mitigation Strategies. arXiv preprint.

* This article was written in part with AI assistance and may contain inaccuracies.