Learning Round
An interview round where you absorb unfamiliar documented material live and apply it — testing learning speed, not recall.
In a learning round you are handed documentation for something you have never seen — a bespoke library, an internal API, an odd data format — and asked to become useful in it under time pressure. It is scored on reading strategy (shape before detail, invariants before signatures), on asking one precise question about the genuinely ambiguous part, and on honestly naming what you have not understood.
Worked example: the docs mention in passing that post-install hooks do not re-run when a package is skipped as already-present; a strong candidate spots that line and predicts the failure it causes on a second machine. Gotcha: bluffing comprehension is the fastest possible fail, because the follow-up question always exposes it — and it is a direct sample of how you would behave at a customer where nobody is checking your work.