| ▲ | dingdongditchme 16 hours ago | |||||||
I used something akin to leetcode in my days as a hiring manager and would not give up on it as a tool. It's not the final rank, but it filters before the interview. If the code is perfect there is not much to talk about other than probing whether you wrote it yourself, but since perfect code doesn't exist it gives us a good basis on discussion during the interview of things that do matter on the job. If the code is poor or nonexistent then I can dismiss (maybe sometimes wrongly) the candidate and focus on more promising ones. Of course it is not great for candidates having to do a whole lot and becomes more meaningless when the answer can be vibe-coded but it does still help imho. | ||||||||
| ▲ | blurjp 9 hours ago | parent | next [-] | |||||||
[flagged] | ||||||||
| ▲ | timr 16 hours ago | parent | prev [-] | |||||||
I don't dispute that it's an effective filter. That is pretty much the only thing it is good at: winnowing a population of applicants down when you don't care about the false-negative rate. The argument that you can use the the artifact of the coding challenge as a starting point for further discussion is perhaps true, but it's like saying that you can use an applicant's resume as a starting point for discussion, once you've filtered out everyone who failed a keyword search. | ||||||||
| ||||||||