New ask Hacker News story: Ask HN: Why is tech hiring so focused on leetcode?

Ask HN: Why is tech hiring so focused on leetcode?
5 by CharlieDigital | 5 comments on Hacker News.
Talked to a dev currently going through interviews. Apple, Meta, Google -- all leetcode interviews so he has invested his time optimizing solely for that. Things that I find more interesting in a candidate: - Can structure modular code - Writes testable code; knows _how_ to test code - Clear communication - Good documentation - Can read, work around, and isolate janky code - Understands higher order concepts and structural organization of code (class and inheritance hierarchies in OOP for example; lambas and closures in FP) - Shows a sense of curiosity and eagerness to learn I place much more value in a candidate that can write code that is well-structured and easy to maintain rather than one that has optimized for solving specific technical puzzles unless those specific algorithms are key to your business and a competitive advantage (versus just using a standard off-the-shelf implementation). What's the appeal of leetcode interviews? If you or your team have used them as a primary filter, did it work out?

Comments