The interview stage worth copying: give the candidate a small piece of someone else's code to review, instead of a blank page to write on.
Most of the work on a long-running product is reading: a system you didn't design, written by someone who has since moved on, that still has to take payments on Monday morning. So we hand over a short change with a few things quietly wrong in it: a retry that could charge a customer twice, an error swallowed instead of logged, a change shipped with no test. What they flag first tells us how they weigh risk. What they walk past tells us more.
It also shows something a coding task cannot: how a person says "this is wrong" to a colleague. On a team where every change passes through cross review, that tone is a technical skill, not a personality trait.
If you hire engineers, it's probably worth asking whether your process tests writing or reading.