This right here is exactly the problem. In the interview you are expected to write a fault tolerant k-way distributed sort and publish it to production, in 3 hours. Once you are embedded in your team they'll have you fixing typos on the landing page.
"Our interview process is good at finding people who are good at interviewing, not good at their job." ~ Someone I follow on Twitter
None of the interviews had any filter for finishing tasks on time, writing good tests, improving team cohesion, or any of the many important characteristics of a great software developer.
But, gosh, I can definitely explain how Aho-Corasick works.
Similarly, you could test for ability to architect a Git commit history. Git uses some important algorithms (e.g. content addressable store, tree traversal) and people who demonstrate an understanding of how to leverage it well are likely to be more effective candidates.
There is actually an incredible amount of technical nuance in this question and you can ask this both on junior interviews and senior ones.
On top of their hoop jumping game.