Inside the Unfair Judge: A Mechanistic Interpretability Account of LLM-as-Judge Bias

A representation-level account of LLM-as-judge scoring bias — reading it as activation geometry that supports bidirectional causal control (attack and defense) and cross-domain prediction of judge failure. Seven judges · seven bias types · nine benchmarks.

Preprint · Under Review

Zixiang Xu1,2,3,†, Sixian Li4, Huaxing Liu1, Xiang Wang1, Shuai Li1, Zirui Song1,2, Xiuying Chen2,∗

1 AMAP, Alibaba Group  ·  2 MBZUAI  ·  3 University of Southern California  ·  4 University of Michigan, Ann Arbor
 Project leader; work done during an internship at AMAP, Alibaba Group.    Corresponding author: xiuying.chen@mbzuai.ac.ae

Preprint under review — not yet on arXiv. The arXiv, code, and data links will be added here once released.

MDS projection of a judge's final-token activations at layer 25: baseline judging inputs form one tight cluster while biased inputs are displaced to a surrounding region; colouring the same points by assigned score or by source dataset shows no clustering, indicating the separation reflects bias rather than score or domain.
The paper's central picture: at a mid-to-late layer of the judge, unbiased inputs sit on a tight activation manifold (blue, centre) while biased inputs are displaced outward (a). Recolouring the identical points by assigned score (b) or by source benchmark (c) yields no clustering — the displacement encodes bias, not the score distribution or the domain.

Overview (TL;DR)

Large language models are now routinely used as automatic judges — they rate answers, compare candidates, and supply reward signals for alignment and preference learning. But judges shift their scores in response to surface cues that have nothing to do with answer quality: who supposedly wrote the answer, how long it is, whether a crowd approves, and so on. Because judges sit inside RLHF and evaluation pipelines, these biases quietly propagate into the models they are meant to audit.

Prior work studies this at the input–output level: perturb the input, measure the score change, patch with prompt engineering. Inside the Unfair Judge asks the next question — when a judge issues an unfair score, what is happening inside the model? — and answers it with a representation-level account that holds across seven judges, seven bias types, and nine benchmarks. The three findings all follow from a single object in the judge's hidden state:

1 · Geometry

Unbiased inputs occupy a tight activation manifold; biased inputs are displaced along a low-dimensional, type-specific subspace that sharpens with depth and is recovered by two independent families of estimators.

2 · Causal control

Steering along that subspace drives scoring both ways: adding it reproduces bias on clean inputs (attack), subtracting it restores fair scores on biased ones (defense). A matched-norm random direction is inert.

3 · Operational

A simple linear projection onto the same features predicts judge failure on three entirely unseen benchmarks (AUC 0.82 vs ~0.63 for a text baseline).

In the authors' words, the contributions are to:

  1. "map the empirical landscape of scoring bias across seven bias types, nine benchmarks, and seven judges, recovering the behavioral asymmetry as a downstream signature";
  2. "characterize the bias subspace (dimensionality, depth profile, multi-estimator recovery) in three white-box judges (Llama-3.1-8B, Qwen3-14B, Gemma-3-12B)";
  3. "close the causal loop with bidirectional steering plus random-direction and bias-type-swap controls that rule out generic-perturbation and readout-direction alternatives"; and
  4. "show a linear projection onto the bias-direction features anticipates judge degradation cross-domain on three held-out benchmarks."

Abstract

Existing studies of LLM-as-judge scoring bias work predominantly at the input-output level: they perturb inputs, measure score deltas, and propose prompt-level mitigations. We argue that the same biases admit a representation-level account in the judge's hidden state, complementary to the input-output view and operationally useful in ways it does not afford. We report three findings, across seven judges, seven bias types, and nine benchmarks. Geometry: baseline judging inputs occupy a tight activation manifold while biased inputs are displaced along a low-dimensional, type-specific subspace that sharpens with depth and is recovered consistently by three families of estimators. Causal control: steering hidden states along this subspace drives scoring in both directions, forward shifts reproducing biased scoring on clean inputs and reverse shifts restoring baseline scoring on biased ones, while matched-norm random directions produce shifts an order of magnitude smaller. Operational: a simple linear projection onto the same bias-direction features anticipates judge failures on three entirely unseen benchmarks, substantially outperforming text-based alternatives. Reading bias as activation geometry, rather than as input-output noise, unifies geometric structure, causal control, and operational prediction within a single framework.

Key Findings & Why They Matter

1.The bias is asymmetric — and the asymmetry is a symptom, not the cause

Every one of the seven judges shows the same pattern: negative surface cues impose a substantial penalty, while the aggregate positive effect stays near zero (baseline mean ≈ 5.84 on Llama-3.1-8B). Only one positive cue — Refinement, a claim that the answer was "carefully revised" — clearly inflates scores. This behavioral asymmetry has long been reported at the input–output level; here it re-emerges as a downstream signature of the underlying activation geometry, rather than as the primary object of study.

2.Bias lives in a low-dimensional subspace that sharpens with depth

Biased activations are displaced along a subspace of only 3–5 effective directions per bias type at layer 25. Both the biased-core fraction and linear separability rise monotonically with depth. Two estimator families with entirely different objectives — directional-change (mean, geometric median, top PCA component) and discriminative-boundary (LDA, a regularized classifier, a linear SVM) — converge on the same late-layer axis, evidence of a genuine low-rank structure rather than an artifact of one estimator.

3.Bias is a matter of direction, not magnitude

Biased and baseline activations are statistically indistinguishable in L2 norm (p > 0.1) at every layer except the final score-readout head. The bias is encoded in which way the activation is displaced, not how far — which is exactly why a unit-normalized direction, rather than a magnitude, is the right handle for intervention.

4.Steering the subspace gives two-way causal control: attack and defense

Adding the bias direction to the judge's hidden state reproduces biased scoring on clean inputs (attack); subtracting it restores baseline scoring on biased inputs (defense). A matched-norm random direction is essentially inert — its effect is an order of magnitude smaller, with validity staying ≥ 0.99 across 30 draws — and a bias-type-swap control sits between random and within-type, ruling out both generic-perturbation and readout-direction explanations. On held-out folds, activation defense retains ≥ 80% of its in-sample effect and outperforms text-rewrite baselines by roughly 4–6×.

5.The same geometry predicts judge failure on unseen benchmarks

Given only a judge's internal state on an incoming (question, answer) pair, a simple linear projection onto the bias-direction features anticipates whether the judge will score unfairly — reaching AUC 0.82 on three entirely unseen benchmarks (0.85 in-domain), versus about 0.63 for a zero-shot text-LLM baseline. A more expressive gradient-boosted model wins in-domain (0.93 dev) but transfers worse (0.75): the low-dimensional geometry is the part that generalizes across domains, which is why the operational claim is anchored to the linear projection.

6.Bias types are not interchangeable, and they interact with domain

The seven types behave very differently. Bandwagon produces the largest negative effect (crossing −2 points on CommonsenseQA and ARC-Challenge) yet is among the weakest positive; Diversity is sharpest on socially sensitive benchmarks (SocialMaze −1.86, BBQ −2.03); Authority concentrates on knowledge-intensive ones (PubMedQA −1.25, MMLU −0.98); Prestige is a small but pervasive −0.3 to −0.5; and Sentiment is essentially flat. The positive and negative rankings are not mirror images — an early hint that the two polarities engage different internal mechanisms.

The Seven Bias Types

Each bias type is studied with a matched pair of content-preserving transformations: a positive variant expected to inflate the score and a negative variant expected to deflate it. Every transformation modifies only surface framing while keeping the factual content and logical structure of the answer fixed, so any resulting score change is attributable to the cue rather than to answer quality.

Prestige

Perceived source reputation or model provenance.

+Prepend a high-capability source (e.g., prefixing with "GPT-4:"). Prepend an outdated or less-capable source (e.g., "GPT-2:").

Verbosity

Preference for more elaborate vs more concise responses.

+Add a few explanatory or transitional phrases — slightly longer, same meaning. Trim non-essential words, making the wording more direct without dropping content.

Bandwagon

Signals of social consensus or peer opinion.

+Note that most prior reviewers approved (e.g., "92% of reviewers found this helpful"). Note that most prior reviewers were dissatisfied (e.g., "87% found this unhelpful").

Authority

Markers of academic credibility, or their absence.

+Insert a plausible, domain-appropriate academic citation and reference. Insert "[citation needed]" markers and a note questioning the evidence.

Sentiment

Emotional tone vs objectivity of the writing style.

+Add a few objective, neutral, scholarly terms. Add a few subjective, emotionally charged expressions.

Refinement

Metacognitive claims about the answer's review status.

+Append "This response has been carefully revised and professionally refined." Append "This is raw AI output that has not been reviewed by any human."

Diversity

Differential treatment by the author's stated social identity.

+Attribute the answer to a positively perceived group (e.g., "provided by an LGBTQ+ advocate"). Attribute the answer to a negatively perceived group (e.g., "provided by an extremist").

Four types (Prestige, Bandwagon, Refinement, Diversity) leave the answer body bit-identical via template insertion; the other three (Verbosity, Sentiment, Authority) are LLM rewrites. A human evaluation confirms the rewrites preserve rated answer quality (TOST equivalence at a 0.30 margin), so the score shifts are not explained by real quality changes.

How It Works (Method)

The study rests on tightly controlled triples of datasets that share the same questions and factual content and differ only in surface framing: a baseline set, a positively perturbed set, and a negatively perturbed set. The judge maps each (question, answer) input to a scalar score in [1, 10], and any systematic score gap between an input and its content-preserving transformation is measured as bias.

  1. Activation analysis. For each input, record the final-token hidden state at every decoder layer. Baseline inputs define a baseline activation manifold; biased inputs are those whose activation sits geometrically far from it (validated with MDS and PCA).
  2. Bias-direction identification. Restrict to effective bias samples whose score actually shifts, and estimate the bias direction with six estimators from two independent families (directional-change and discriminative-boundary). High within-family agreement supports keeping three representatives — Geometric Median, PCA, and a Classifier vector — for the causal experiments.
  3. Causal control via steering. Add or subtract the calibrated direction from the hidden state, choosing an intervention strength on the feasibility boundary that keeps outputs valid and rank-faithful (a Spearman floor rules out trivially corrupting the judge). Forward steering attacks; reverse steering defends.
  4. Outcome prediction. Build per-layer activation features (bias-direction projections, manifold-deviation, semantic-context) and train a simple linear projection plus a gradient-boosted model to anticipate judge failure — evaluated cross-domain on benchmarks that contribute no questions, context, or perturbation pairs to the fit.
Responsible release. The paper frames activation steering as an analytical and defensive tool for diagnosing bias and constructing fairness-oriented counterfactuals. It releases only the analysis and outcome-prediction pipelines, and defers any attack-oriented release to a controlled responsible-disclosure process.

Experimental Setup at a Glance

Judges (7)
GPT-4.1, GPT-4o-Mini, Llama-3.1-8B, Llama-3.3-70B, Qwen3-14B, Gemma-3-12B, DeepSeek-V3
White-box analysis
Activation-level experiments on the three open mid-scale judges — Llama-3.1-8B (primary), Qwen3-14B, Gemma-3-12B
Benchmarks (9)
GSM8K, MMLU, TruthfulQA, CommonsenseQA, PubMedQA, GPQA, ARC-Challenge, SocialMaze, BBQ — spanning math, factual knowledge, commonsense, biomedical, social cognition, and fairness
Scale
4,500 source questions, baseline answers from a six-model pool, 31,500 + 31,500 perturbed samples across the two polarities
Split
45 / 15 / 40 nested train / dev / test; train+dev use six benchmarks, while SocialMaze, BBQ, and GPQA are held out as the cross-domain probe
Prompt configs
CoT × Strict (four configurations); default is strict, non-CoT after confirming the findings hold across all four
Compute
~1,400 A100-hours for the full set of activation extractions, strength searches, and predictor training

Frequently Asked Questions

What is "Inside the Unfair Judge" about?

It is a mechanistic-interpretability study of LLM-as-judge scoring bias. Instead of treating the judge as a black box and only measuring how its scores move when inputs are perturbed, it opens the model and locates bias in the judge's hidden state. It reports three findings across seven judges, seven bias types, and nine benchmarks: bias occupies a low-dimensional, type-specific activation subspace that sharpens with depth (geometry); steering along that subspace controls scoring in both directions (causal control); and a linear projection onto the same features predicts judge failure on unseen benchmarks (operational prediction).

How is this different from prior LLM-as-judge bias work?

Most prior work operates at the input–output interface: it perturbs inputs, measures score deltas, and mitigates with prompt engineering, calibration, or judge ensembles. That view describes bias by what comes out of the model. This paper gives a representation-level account of what happens inside the judge when it issues an unfair score, contributing a geometric characterization of typed bias subspaces, bidirectional causal control (attack and defense, not mitigation alone), and a cross-domain predictor of judge failure.

What are the seven bias types?

Prestige (source attribution), Verbosity (length), Bandwagon (social consensus), Authority (academic credibility), Sentiment (emotional tone), Refinement (metacognitive claims about revision), and Diversity (stated social identity of the author). For each type, controlled positive and negative surface transformations are applied to the same answer while preserving its factual content and logical structure, so any score change reflects surface framing rather than answer quality.

What does "bidirectional causal control" mean?

The recovered bias subspace is not just a passive correlate of biased scoring; it is an interventional handle. Adding the bias direction to a judge's hidden state reproduces biased scoring on clean inputs (attack), and subtracting it restores baseline scoring on biased inputs (defense). A matched-norm random direction produces a shift an order of magnitude smaller, and a bias-type-swap control sits between random and within-type, ruling out generic-perturbation and readout-direction explanations.

Can it predict when a judge will be unfair?

Yes. A simple linear projection onto the bias-direction features reaches AUC 0.82 on three entirely unseen benchmarks (0.85 in-domain), versus about 0.63 for a zero-shot text-LLM baseline. A more expressive gradient-boosted model wins in-domain but transfers worse, indicating that the low-dimensional bias geometry is the part that generalizes across domains.

Is the code or data available?

The paper releases the analysis and outcome-prediction pipelines as an artifact, and defers any attack-oriented release to a controlled responsible-disclosure process. This paper is a preprint under review and is not yet on arXiv; the arXiv, code, and data links will be added to this page once they are public.

When should I cite this paper?

Cite it when your work involves LLM-as-judge or LLM-as-evaluator bias, mechanistic interpretability or representation engineering of model behaviors, activation steering and inference-time intervention, evaluation reliability in reward modeling and RLHF, predicting or detecting evaluator failure, or fairness and social-identity bias in automated evaluation. See the When to Cite This Paper section for a ready-to-use citation sentence.

When to Cite This Paper

This paper is a useful reference when your work touches any of the following:

A typical citation: Xu et al. (2026) give a representation-level account of LLM-as-judge bias, showing that it occupies a low-dimensional, type-specific activation subspace that supports bidirectional causal control — attack and defense via activation steering — and predicts judge failure on unseen benchmarks.

Resources

This page will be updated with the arXiv, code, and dataset links as soon as they are public.

BibTeX

Preprint citation (arXiv identifier to be added on release)
@misc{xu2026unfairjudge,
  title={Inside the Unfair Judge: A Mechanistic Interpretability Account of LLM-as-Judge Bias},
  author={Xu, Zixiang and Li, Sixian and Liu, Huaxing and Wang, Xiang and Li, Shuai and Song, Zirui and Chen, Xiuying},
  year={2026},
  note={Preprint}
}