Skip to content
mlmentorship

Preference data and reward models

Preference optimization is a measurement system: sampling policy, annotator protocol, disagreement, calibration, and shift determine the signal.

Published · 5 min read ·Role-specific ·Advanced

Summary

Preference data records comparative judgments among model outputs, and a reward model learns a scoring function that predicts those judgments for training or evaluation.

RLHF diagrams often compress the hardest part into “collect preferences.” The signal depends on the sampled prompts and responses, the judges, the rubric, and the treatment of disagreement. It also changes as the policy moves away from the reward model’s training distribution.

A powerful optimizer amplifies measurement defects. Better preference-data design can matter more than another RL algorithm.

Learning objective: explain why reward-model validation on collected comparisons does not guarantee reliable rewards after the policy is optimized.

Optimization can move responses beyond the proxy accuracy that was tested

A tested reward proxy can become untested after optimizationThe proxy was validated on the original response distribution. Optimization shifts responses, so original accuracy does not certify the new region.Each claim needs its own observedevidenceoriginal response accuracy+shifted response accuracy?
Derivation
Optimization can move responses beyond the proxy's validated coverageFictional outputs R1 and R2 have proxy/human scores four/four and six/five. Optimized R3 has proxy nine and fresh human score one, outside the represented proxy-score band three to six. It is an illustrative possible shortcut, not an inevitable optimization result. New on-policy comparisons must revalidate the proxy.Fictional outputs; possible failure, not aninevitable curveFresh human rubric score (0 to 5)0135036910R1R2R3Proxy reward (arbitrary units, 0 to 10)Dashed band: represented proxy-score range, 3 to6Optimized R3: proxy 9, fresh humanscore 1possible style shortcut; inspect itnew on-policy pairs -> revalidateA high proxy score outside coverage is notvalidation.
R3 improves the proxy while failing the fresh rubric in this toy example. A score-range band is not full distributional coverage. Inspect on-policy outputs and revalidate; do not assume every run diverges.
Check: Why can high held-out pair accuracy coexist with poor judgments on newly optimized responses?
Read it this way: The proxy was validated on the original response distribution. Optimization shifts responses, so original accuracy does not certify the new region.
Does original-distribution validation certify the newly shifted response region?

Constructing comparisons

For prompt , sample responses and from policies and decoding settings chosen to expose meaningful differences. Ask an annotator which response better satisfies an explicit rubric, allows a tie, or marks both unacceptable.

Pairwise judgments are often easier than absolute scores, but sampling determines value. Comparing one obviously broken answer with one strong answer teaches less than a near-boundary pair that isolates factuality, instruction following, style, or safety.

Useful sampling strategies include:

  • policy checkpoints across training;
  • multiple temperatures and seeds;
  • uncertainty or disagreement sampling;
  • known failure slices;
  • adversarially generated pairs;
  • human and model-written alternatives;
  • active selection near the current reward boundary.

Annotator protocol

Define the target construct before collecting labels. “Which is better?” mixes correctness, relevance, verbosity, style, and safety differently across annotators.

A sound protocol includes:

  • rubric and precedence among criteria;
  • examples and counterexamples;
  • tie and both-bad options;
  • qualification and calibration tasks;
  • blind randomization of response order and model identity;
  • duplicate items for consistency;
  • escalation for high-impact ambiguity;
  • slice-level agreement and quality monitoring;
  • privacy and worker-welfare constraints.

Disagreement is data. It can reveal ambiguous prompts, plural user values, or a broken rubric rather than a bad annotator.

Reward-model objective

A common Bradley-Terry form models:

The loss encourages the preferred response to receive higher reward. Only differences are identified; the absolute reward scale is arbitrary without further calibration.

Evaluate the reward model

Use held-out prompts and behavioral families. Measure:

  • pairwise accuracy and calibration;
  • performance by criterion and slice;
  • agreement with independent humans;
  • order, length, style, and verbosity bias;
  • out-of-distribution behavior;
  • adversarially optimized outputs;
  • ranking stability across policy checkpoints;
  • uncertainty and abstention quality.

High random-split accuracy can coexist with failure on a new policy because response distribution changes during optimization.

Reward hacking and shift

Once a policy optimizes the reward model, it searches for outputs the model scores highly, including shortcuts absent from ordinary samples. Mitigations include on-policy data refresh, adversarial sampling, reward ensembles, uncertainty penalties, KL constraints, independent verifiers, and held-out audits.

None remove the need to inspect what the optimized policy discovers.

Common confusions

  • “More preference pairs always help.” Redundant easy pairs add little signal.
  • “Annotator disagreement is noise.” It can expose underspecified values or prompts.
  • “Reward accuracy equals reward quality.” Calibration, slice behavior, and optimization robustness matter.
  • “The reward score is utility.” It is a learned proxy with arbitrary scale and bounded coverage.
  • “DPO removes preference-data problems.” It removes the explicit reward model, not bias or coverage in the comparisons.
  • “Model graders eliminate humans.” They inherit model biases and require independent calibration.

In an interview

Describe prompt and response sampling, rubric, annotator quality, disagreement, objective, held-out families, calibration, policy shift, reward hacking, and the online outcome the proxy is meant to improve.

Related: RLHF and DPO, PPO, and design post-training data and an RL environment.