Issue 12, Oct 27, 2026

The Attention Slicing Trap

Senior ML Engineer interview at Google DeepMind, and the interviewer asks:

“You doubled attention heads from 16 to 32 with d_model fixed, expecting the model to learn more patterns. Quality is flat and throughput dropped. What did you actually change, and what should drive head count instead?”

Don’t say: “More heads let the model attend to more relationships in parallel, so it should capture richer patterns.”

Why cutting your model into thinner heads buys redundancy instead of expressiveness and the invariant rule top engineers use to protect GPU efficiency.

Share this trapShare on LinkedIn

The full answer, with the mechanism and the arithmetic, is for paid subscribers on Substack.

Read it on Substack

Get the next one

Free on Substack. Unsubscribe in one click.

More traps set at Google DeepMind