One candidate did badly on the coding exercise. Then we showed him a payment flow that was quietly charging some customers twice, and the first thing he asked was whether the retry came from our side or the provider's.
He was the only one that week who asked that. The others went straight to guessing at fixes.
An hour earlier we had almost passed on him, and the lesson stuck: we were testing how fast someone writes code, when the expensive skill is knowing which question to ask before touching anything. Now every interview includes a broken system and no explanation of why it is broken.
We would be glad to hear what you look for in an interview that a resume leaves out.