The most useful thing we learn in an interview is what a candidate does with a task that is missing a detail on purpose.
We hand over a small payment flow and leave the retry behaviour unspecified. Most people write correct code for the task as written. The one we bring onto the team stops and asks what happens when the same request arrives twice, because in payment work the expensive bugs are rarely broken code. They are correct code built on a question nobody asked.
So we hire for the question rather than the keystrokes. We would like to hear the one question you wish a new hire had asked in their first week.