[esco27]

This is a mix of laziness and convenience. Hiring often boils down to what’s easiest, not what’s best. Leetcode is a proxy: it quickly filters candidates and spares everyone from more effort. But if you hire based on Leetcode, you’ll get Leetcode engineers. If you hire based on track record, impact, and real-world projects, you’ll likely get someone who’s better—and actually fits the role.

If you want to do your part and can afford it, turn down any Leetcode based interviews and let them know why if they ask.

[marcosdumay]

Yes, always keep basic statistics in mind. Every single proxy you apply that isn't correlated to what you really want will filter-out the outliers towards the median.

And remember what the median job candidate that applies to your place looks like. Do you want to remove the people that don't look like them? If yes, you are on the clear.

[almost_usual]

Top tier companies can filter on both, the market is saturated now.

[esco27]

That’s fair, but most software jobs aren’t at top-tier companies. HR often stays out of the process due to technical barriers, leaving engineers to handle interviews. Leetcode becomes the easiest way to offload the hassle—ironically, a self-inflicted wound on fellow engineers.