4 ms·

I think asking for particular details of an algorithm is pointless, and I wonder how many interviewers actually do that. The more common questions I've encounte

I think asking for particular details of an algorithm is pointless, and I wonder how many interviewers actually do that. The more common questions I've encountered in interviews are along the lines of "serialize a binary tree" where the data structures are basic but the problem has different possibly suboptimal ways of being solved. I'm curious if there really is an inherent and implicit bias to these sorts of questions that favors younger candidates. I'd be very sad if that's the case, as I'm more inclined to think other personal biases are in play.

mechanical_fish 12y ago
You may think you're doing the candidate a favor by offering to handwave away the details, but the vaguer question might actually be worse. "Can you write a correct implementation of an AVL tree on this whiteboard, in any programming language, in the next thirty minutes" is a terrible interview question, but at least it has a factual answer. [1] "Can you riff on the subject of serializing a binary tree" is an open-ended question that will inevitably be graded on an imaginary curve. And the first rule of human psychology is: When you're asked to grade people on an imaginary curve, your intuition spits out a decision that is built on unconscious bias. [1] edit: that is to say, it has a factual answer if you ask the question and then fall totally silent. Which would be evil, of course, so in practice you and the candidate will naturally turn this question into a back-and-forth repartee, and it will reduce to the same exercise of unconscious biases as the vague question is.