> ...are doing so because they don't know how to hire engineers

Instead, this approach tends to yield the "least worst" candidate; the ones that have the time to waste going through a 3 week interview process.

The take home is the most egregious. I think that the solution is rather simple: what would knock your socks off if you saw it in a submission to a take home? Could you design 2-3 questions that would get right to that scenario and test for that output? It seems like it would be a far more efficient use of time.

I wrote a followup blog post on this: https://chrlschn.dev/blog/2023/10/your-interview-process-is-...

It's the companies that hire really high volumes that I see resort to leet code tests as sort of a great filter.

I rarely see small companies use leet code interviews, but that does not say much about the rest of their interview quality.