Earlier quoted context omitted.
The problem space for computer science algorithms is gigantic and many of these companies testing for this knowledge then immediately throw new engineers onto line of business CRUD apps and bug fixes, which rarely have the engineer implementing any of these algorithms from scratch. Unless you have a super targeted problem space that interviewing employees know about, then you are doing about as well as drawing a rand…
The problem space for computer science algorithms is gigantic and many of these companies testing for this knowledge then immediately throw new engineers onto line of business CRUD apps and bug fixes, which rarely have the engineer implementing any of these algorithms from scratch. A programmer worth his salt should retain enough 1st principles knowledge to not create a O(n^3) bottleneck in production or otherwise st…
The majority of development work does not have you working through every comp sci algorithm in existence on a frequent enough schedule that the average engineer, or even a great engineer, will remember them all. That is going to garuntees that interviews are a game of chance. The more algorithms and the trick question associated with them that you can memorize the greater your odds, but it's still down to luck of the draw for what questions you are asked.
If you're looking for devs to show that they understand the ideas, you'd be better off telling them the problem space ahead of time so that they can prepare for it, and then deeply questioning their knowledge in that space