This is a great point. Reading code is such an important skill and how most of an engineers time will be spent. The ability to reason about code that was written by someone else (including your past self) and update/expand it in a clean/maintainable way is a better indicator of success IMO then writing a little chunk of code that solves a brain teaser.
Read code, explain what it does and discuss how you would expand it to add additional functionality or fix a bug. I feel that would be a better approach than most of the current leetcode style interviews.
Read code, explain what it does and discuss how you would expand it to add additional functionality or fix a bug. I feel that would be a better approach than most of the current leetcode style interviews.