Re:A Strategy For The Dreaded Interview Coding Question
by jmillikin on Wednesday July 25, 2012 @01:50PM
(#4292092)
Rather than memorizing the answers to bad questions, technical interviewers should memorize the questions themselves. Then if any of those show up in an interview, walk out -- one doesn't want to work at those sorts of companies.
[ Parent
| on HN ]
Re:A Strategy For The Dreaded Interview Coding Question
by cdr on Wednesday July 25, 2012 @02:34PM
(#4292317)
That's a bit much - it's rare that a company doesn't have something broken about its hiring process, even good/great companies. If you want to work there otherwise, what does it hurt to learn the expected answer for fluff questions and recite it when asked?
Re:A Strategy For The Dreaded Interview Coding Question
by MartinCron on Wednesday July 25, 2012 @02:40PM
(#4292350)
It is a bit much. Good managers can be crappy interviewers (and vice-versa). I would take it into account when considering my options, though.
Re:A Strategy For The Dreaded Interview Coding Question
by Retric on Wednesday July 25, 2012 @02:31PM
(#4292295)
As an interviewer I often ask questions not because I care what the answers are, but rather to change the tone of the conversation. There is little point in grilling people for an hour vs mixing in a few probing questions and keeping the interview light.
AKA, I see you got a CS degree and 5 years of development experience. Looking back what do you think your most (useful, fun, memorable) class was? What's language that you don't know are you most interested in learning / using?