Re:We analyzed thousands of interviews on everything from la...
by Sacho on Wednesday June 14, 2017 @11:40PM
(#14557775)
You can always find something to talk about in the code, though. You can start by just describing what each line does, in your opinion. Then you can go back and start to group the lines - e.g. "lines 1-3 are the initialization, lines 4-6 are probably intended to flurb the glorb", etc. Yes, it's possible that you can find an interviewee who is great technically but shuts down during an interview. The question is how much time and effort you want to invest digging for that person, especially in light of such studies.
Re:We analyzed thousands of interviews on everything from la...
by surement on Wednesday June 14, 2017 @06:25PM
(#14556591)
You could look at a more complicated piece of code, let them think about it for a bit, and if they don't have that aha moment you can still discuss it with them. For example, pick a problem you someone on your team struggled a bit with, something that you wouldn't necessarily expect a candidate to solve during an interview, and discuss solutions with them. I think you could learn a lot about the interviewee this way.
Re:We analyzed thousands of interviews on everything from la...
by javabean22 on Thursday June 15, 2017 @01:53AM
(#14558189)
omg, are you me. No ahas at interviews. Good to great ahas at random times. Fuck whiteboarding interviews.
As it happens most of my "aha!" code-related moments come when I'm either under the shower or when I'm washing the dishes. Very rarely did it happen for me to look at a piece code while in front of my computer and then immediately be stuck by what that code does or by some hidden bugs in it. It's all sort of mechanical, at least while I'm sitting at my desk. I'd say it would be very hard for people like me to reproduce that "aha!" moment during an interview, in front of some other people who expect me to have those moments of enlightenment right there and at that precise moment.