skip to content

A linear probe hits 68% where full fine-tuning hits 79% - what does that gap tell you?

level: seniorimportance: should knowfreq 45%

answer

  1. the gap prices reshaping the features
  2. missing, non-linear, shifted, or wrong layer
  3. rule out an under-trained probe first
  4. two-layer head separates two of the causes
  5. sizes the mismatch, does not localise it

basics

~20 s

An eleven-point gap says the target task needs structure the frozen features do not expose linearly - the encoder either discarded it during pretraining or holds it in a form only updated weights surface. The gap sizes the mismatch, not its cause.

solid answer

~50 s

The gap is the value of being allowed to reshape the features, measured in accuracy on this one target. Eleven points is a real mismatch between what pretraining preserved and what the target labels depend on, and there are four candidate causes: the pretraining objective genuinely discarded the discriminating signal; the signal is present but encoded non-linearly; the target domain has drifted far enough from the pretraining data that the frozen features land in a region the encoder never modelled; or the layer you probed has specialised away from the property. Before believing any of them, rule out measurement artefacts - an under-trained or over-regularised probe, or a fine-tune scored on a small validation split where eleven points is inside the seed-to-seed noise. To localise the cause, probe several layers, refit with a small non-linear head, and compare probe accuracy on pretraining-like data against target data.

go deeper

for a junior

Recall that a probe only fits a linear read-out on frozen features while fine-tuning changes the features, so fine-tuning is normally the higher number.

for a middle

Explain the candidate causes of a gap - discarded signal, non-linear encoding, domain shift, wrong layer - and name the cheap test that separates the first two.

for a senior

Demonstrate the diagnostic sequence and the artefact checks: probe hyperparameter budget, matched preprocessing, repeated seeds, per-class error breakdown, before you attribute the gap to the representation.

for a principal

Own what the gap does and does not license across a portfolio of tasks. Argue when a single-target gap is enough evidence to change an encoder strategy and when it is one noisy measurement.

## What the two numbers are The 68% comes from a frozen encoder plus a fitted hyperplane: the features are fixed and only the read-out adapts. The 79% comes from letting every encoder parameter move on the target labels, which changes the features themselves. The difference is therefore *the return on being allowed to reshape the representation for this task* - not a generic property of the encoder, and not a property you can quote without naming the target. ## Four substantive causes **1. The pretraining objective threw the signal away.** Every objective is a compression rule about what to keep. If the target depends on a distinction the pretraining task never had to make - fine-grained texture, a rare category, an attribute deliberately made invariant by the augmentations used in pretraining - the frozen features simply do not carry it, and no read-out recovers it. Fine-tuning can rebuild it from the lower layers. **2. The signal is present but not linearly decodable.** The classes may sit in a curved or interleaved arrangement that no hyperplane separates. Here the information is there; only the read-out is too weak. A small non-linear head on the same frozen features will close part of the gap and is the cheapest test of this hypothesis. **3. Domain shift.** Frozen features are only meaningful on inputs that resemble what the encoder was trained on. Move to a different sensor, a different language register or a heavily different image statistic, and the frozen vectors become poorly spread and near-degenerate for the new inputs. Fine-tuning adapts the early layers to the new input statistics, which is exactly where a large gap most often comes from. **4. Wrong layer.** You probed one layer. If that layer has specialised toward the pretraining objective, the property may live several blocks earlier. Probing a range of depths often recovers points without touching the encoder. ## Artefacts to rule out first A gap can be manufactured rather than real: - **An under-fitted probe.** Probes need enough epochs and a sensible regularisation strength. A probe stopped early or regularised hard is a weak measurement, and the missing points belong to the probe, not the features. - **Unequal preprocessing.** If the fine-tuning run saw augmentation and the cached probe features did not, part of the gap is a data-pipeline difference. - **Noise on a small target set.** With a few thousand validation examples, eleven points may be two or three standard deviations of seed-to-seed variation - or may not be. Repeat both sides across seeds before treating the gap as a finding. - **Fine-tuning overfitting a favourable split.** A fine-tuned model has far more capacity to exploit leakage or near-duplicates between train and validation; a frozen encoder with a linear head largely cannot. Check the split before crediting the extra points to representation reshaping. ## How to localise the cause A workable diagnostic ladder, cheapest first: 1. Refit the probe properly with a real hyperparameter budget. If the gap shrinks, it was measurement. 2. Probe several layers. If a middle layer beats the one you used, the property was there and you were reading the wrong depth. 3. Fit a two-layer head on the same frozen features. If it closes much of the gap, the information is present but non-linear; if it barely moves, the information is genuinely missing. 4. Compare probe accuracy on target data with probe accuracy on data resembling the pretraining distribution. A large drop points at domain shift rather than task difficulty. 5. Look at *which* classes lose. A gap concentrated in a few confusable classes reads very differently from one spread evenly. ## Reading the size of the gap A **near-zero gap** says the frozen representation already exposes everything the target needs along linear directions; extra capacity buys nothing, and any remaining error is task noise or label noise rather than representation quality. A **modest gap** is the normal case for a target close to the pretraining domain. A **very large gap** - the probe near the majority-class rate while fine-tuning works well - usually means the encoder is being used far outside the distribution it was trained on, and the fine-tune is effectively relearning features rather than adapting them. One caution: the gap ranks nothing beyond this target. Two encoders with identical probe scores can have very different fine-tuning ceilings, and a probe-versus-fine-tune gap measured on one dataset does not transfer to the next one.

  • What would make you suspect the gap is a measurement artefact rather than a property of the features?
    A probe trained with no hyperparameter budget, stopped early, or regularised hard; augmentation present in the fine-tuning pipeline but absent when features were cached; a validation split small enough that seed-to-seed variance covers the gap; or a split with near-duplicates that a high-capacity fine-tune can exploit and a hyperplane cannot. Fix each and re-measure before drawing conclusions.
  • The probe and the fine-tune land within a point of each other. What does that tell you?
    That the frozen representation already exposes what the target needs along linear directions, so extra capacity has nothing left to reshape. The remaining error is task or label noise rather than representation quality. It also means probe accuracy is, for this target, a trustworthy cheap stand-in for the expensive measurement.
  • How would you tell 'the information is absent' apart from 'the information is not linearly decodable'?
    Refit on the same cached features with a small non-linear head and, separately, probe several depths of the encoder. If either recovers most of the gap, the information was present and your read-out or your layer choice was the limit. If both stay flat while fine-tuning still gains, the encoder is not preserving the signal and the gain comes from rebuilding it.

saying these in an interview costs you the question

  • Reads the gap as proof the encoder is bad in general
  • Never questions whether the probe itself was trained properly
  • Assumes the missing information cannot be in the features at all
  • Ignores domain shift as a source of the gap
  • Treats one dataset's gap as a general property of the encoder
  • Quotes the gap without repeated seeds or a validation-size sanity check

context