I really loved the uno reverse card interview the author recommended. "Let's debug this piece of broken code"
This can spark so many interesting discussions, from syntax, architecture, cs, product etc
It is literally the job that engineers do 99% of their time yet we don't interview on this.
Debugging exercises reveal not just technical knowledge but also communication patterns - how candidates ask clarifying questions and explain their reasoning reveals more about their daily work habits than most algorithm puzzles.
I also loved the idea.
Except it was wildly unpopular amount the other interviewers as t was seen as setting traps and watch if the poor guy falls into them.
And interviewees were sometimes dumbfounded looking at the code, and we didn't know if they were just crushing under the stress or had never looked at code in their life.
All in all, it wasn't that different from a straight leetcode interview.
Code reviews were basically the same, nice on paper but hard to judge in practice.