clearly a code review is an easier task, and so provides a weaker signal.
When people have time to prepare for the test and the incentives are high enough, you only get what you measure. The leetcode fans don’t seem to understand this.
I actually really like this concept. The main benefit is that this approach allows a more conversational interview and also allows to cover a broader range of real-world problems.
There is almost 0 correlation between candidates ability to be effective collaborator and their ability to solve leet code problems. The former is a lot more important to us than your ability to chew out code.
Does this translate to creative problem solving and thinking? To productivity when encountering novel tasks? To being a good teammate? There is a stronger correlation with "having free time" and "solving leetcode" than being a great engineering teammate, IMO.
If you don’t think it shows problem solving, why would you prefer a test that involves no writing or creation?
Reading is very practicable m. and there is an issue that you can’t evaluate someone smarter than you.
What's your argument that code reviews aren't a good representation of skills?