Re:Allow “Phone a Friend” during Technical Interviews?
by bencollier49 on Monday February 04, 2013 @12:21PM
(#5165470)
I agree. Generally, open ended questions give you a pretty good idea of a candidate's aptitudes. I had a guy come to interview who'd supposedly got a CS degree with first-class honours from a fairly well-ranked British uni. He couldn't tell me what functional programming was, which I thought was pretty peculiar.
I tried to call the uni to verify his degree but they wouldn't confirm it without consent (Data Protection Act), and I wasn't going to employ him (for several reasons), so I didn't take it any further.
Re:Allow “Phone a Friend” during Technical Interviews?
by capsule_toy on Monday February 04, 2013 @10:02PM
(#5168772)
I don't think not knowing functional programming is peculiar at all. When I went to school, the dominant language was Java. Aside from a few courses, some of which covered functional programming, every other course and project was written in Java. It'd be very easy for me to imagine a good graduate making it through University and not remembering functional programming at the end.
Re:Allow “Phone a Friend” during Technical Interviews?
by bencollier49 on Tuesday February 05, 2013 @07:52AM
(#5170365)
Not that he didn't know it. He didn't know what it was.
Re:Allow “Phone a Friend” during Technical Interviews?
by Jabbles on Monday February 04, 2013 @12:37PM
(#5165615)
I agree. Generally, open ended questions give you a pretty good idea of a candidate's aptitudes.
I would still have to test their ability to code something, as I know how good I am (if I may say so) at blagging my way through open ended questions.
I wouldn't like put one of my friends in such a position when answering an interview question. Nor would I like to be (partly) responsible for a friend's performance in theirs.
Anyway, surely a candidate that can do the question on their own is better than one that can't. And surely the friend that can answer the question is better than the candidate?
A technical interview question shouldn't be about specific knowledge of particular problems (although bad ones often are, usually having "Aha!" moments). They should test areas of knowledge: reversing a linked list is checking if they understand how pointers work, something which is not really possible to learn in 5 minutes of Googling, even if they can then answer the question. Questions should test general technical problem solving skills, which are not easily Googled, even if a specific instance is.
Finally, if a candidate requires knowledge of a particular API (e.g. the order of parameters to a function), then the interviewer should tell them. If the interviewer doesn't know, then they must acknowledge that it's not really important, and allow the candidate to just pseudocode it.