> Whether they will be productive at your company/project. That got a highlight in the article, but not a lot of text to explain it. > they have to fix a bug

> Whether they will be productive at your company/project. That got a highlight in the article, but not a lot of text to explain it. > they have to fix a bug in an unknown codebase Creating those scenarios costs a lot of time and resources. --- I think the LeetCode stuff is just fine. There are some issues with it: - People can cheat by being LeetCoders that specialize on solving LeetCode, not being actual day-to-day programmers. - You might end up with a monoculture team. Overall, though, it seems to be the safest approach.