In an interview, the thing we actually watch for is what a candidate does when the task we hand them is missing a detail on purpose. That tells us more than what they can build.
One recent decision came down to exactly that. Two people wrote comparable solutions: one asked what should happen when the same payment is retried, the other quietly picked an answer and moved on. We hired the one who asked. In payment work a silent guess about retry behaviour doesn't fail in code review, it fails on a customer's statement, weeks later.
If someone joined your team and turned out to be a great hire, we'd like to hear what you noticed about them in the very first conversation.