Earlier quoted context omitted.
It’s still hard to know what this means. For example, all the senior engineers I currently work with are great at telling a story about how they look to hire based on talent, self-awareness, critical thinking, and many soft skills, and that the technical particulars are only incidental guideposts. Then they proceed to ask candidates to derive a card shuffling algorithm on a whiteboard in 30 minutes and fail them from…
Then they proceed to ask candidates to derive a card shuffling algorithm on a whiteboard in 30 minutes and fail them from the interview if the running time complexity would be too high or if they can’t mathematically prove the result would be a uniform draw from the space of permutations of the cards. For a company that runs an online game server, let's say, this really isn't that high a bar. I know off the top of my…
Unless you have a super targeted problem space that interviewing employees know about, then you are doing about as well as drawing a random problem from a hat.
Most developers I know just brush on as many algorithms as they can remember when they are going to interview for a new job. Then they just go through interviews until they find a company that manages to pick an algorithm out of the ones they memorized. This is a giant waste of effort to create a system that is effectively a lottery if you can get past the, admittedly large, bump of being able to understand any comp sci algorithms