Earlier quoted context omitted.
Much of the industry uses algorithm and data structure problems as a way of assessing "smartness" in interviews -- the idea is that even though it's often not needed for the job, giving people the challenge of learning that area at the intersection of computer science and software engineering correlates with how strong a contributor they'll be. I.e. if you don't know it but can pick up an area like that, that's a goo…
Just like with dating preferences, leet code interviews are merely a fast rejection heuristic. Because there needs to be some kind of filter. And we haven't found any better. If we took more time, with dating and interviewing, we'd probably find a lot more diamonds in the rough. But ain't nobody got no time for all that.
Until interest rates get hiked.