I've been trying to weed out a lot of these problems from my team's interviewing set- they filter for CS students, not practical development knowledge. I can honestly say I've never used a linked list in 15 years of being paid to develop software. I've been pushing interviewers to come up with a problem based on code they've actually written in the past and use that for their interview question.
I'm starting to think I might have better luck having a pre-built some code with some poor practices and asking a candidate to refactor and improve it- evaluating their ability to at least know what clean code is supposed to look like.
That being said, I'm not willing to give up my whiteboard code interviews yet- they are too useful a filter. I still get candidates that sound fine talking about their previous experience and then say things like "oh man, its been a while since I've used arrays" when asked to code.
I'm starting to think I might have better luck having a pre-built some code with some poor practices and asking a candidate to refactor and improve it- evaluating their ability to at least know what clean code is supposed to look like.
That being said, I'm not willing to give up my whiteboard code interviews yet- they are too useful a filter. I still get candidates that sound fine talking about their previous experience and then say things like "oh man, its been a while since I've used arrays" when asked to code.