Technical and non-technical tips for rocking your coding interview

Re:Technical and non-technical tips for rocking your coding ... by spatley on Wednesday September 27, 2017 @12:25AM (#15344916)

The question we ought to ask though is: Is a candidate that freezes when asked to reverse a list be an employee that would be incapable of basic coding? Or more interestingly (to me) is the candidate that can easily write the reverse pseudocode on an interview whiteboard one that will be a good employee?

When I interview, I ask for her to write some code, yes. But I make it very simple: fizzbuzz, or reverse a string. But then inform the canditate that I am looking for style, craft and personality. Somewhat akin to a chef being asked to fry an egg

[ Parent | on HN ]

Re:Technical and non-technical tips for rocking your coding ... by IncRnd on Wednesday September 27, 2017 @04:42AM (#15345935)

> Or more interestingly (to me) is the candidate that can easily write the reverse pseudocode on an interview whiteboard one that will be a good employee?

You're looking at it backwards. That type of question catches people who misstated their qualifications. It's a buy-in to sit at the table.

People can debate whether they should have to answer questions, but in the real world one or two small qualifying questions of this nature save the employer a lot of money and time in the hiring process.

[ Parent | on HN ]

Re:Technical and non-technical tips for rocking your coding ... by onikolas on Wednesday September 27, 2017 @01:46AM (#15345208)

And how do you quantify "style, craft and personality" ?

I ask about quantification because I see it as the only way to reduce/eliminate bias.

[ Parent | on HN ]