> My feeling on those who use LeetCode as some sort of indicator.
I'm fine if you need me to at least demonstrate _basic_ competency with a few simple Leetcode questions. There are a LOT of candidates who don't actually know what they're doing (either they're new or incompetent). It's okay for you to make sure that I have half a clue of what I'm doing. The problem becomes when Leetcode is used as an actual measurement of competency ceiling.
The best engineers I work with would completely fail at Leetcode challenges because they've found easier, simpler ways to implement something.
For example, anything that lodash provides is Leetcode/HackerRank under the hood (not a dig a lodash, just the type of problems Leetcode tends to ask about). I would expect a senior engineer to be able to replicate any of that code, but I'd first expect them to know that it's not worth their time to replicate that code. Instead, they should find a well tested tool instead.
I'm fine if you need me to at least demonstrate _basic_ competency with a few simple Leetcode questions. There are a LOT of candidates who don't actually know what they're doing (either they're new or incompetent). It's okay for you to make sure that I have half a clue of what I'm doing. The problem becomes when Leetcode is used as an actual measurement of competency ceiling.
The best engineers I work with would completely fail at Leetcode challenges because they've found easier, simpler ways to implement something.
For example, anything that lodash provides is Leetcode/HackerRank under the hood (not a dig a lodash, just the type of problems Leetcode tends to ask about). I would expect a senior engineer to be able to replicate any of that code, but I'd first expect them to know that it's not worth their time to replicate that code. Instead, they should find a well tested tool instead.