3 ms·

Yes, I see people fail at basics in interviews all the time. But I keep wondering how much of that is people being poorly qualified, and how much of it is inter

Yes, I see people fail at basics in interviews all the time. But I keep wondering how much of that is people being poorly qualified, and how much of it is interviews being poor indicators of true skill. I've seen people barely sneak through technical interviews, whose subsequent performance justified the concerns I had at the time. I've seen others hired against my personal recommendation who turned out to be brilliant at their jobs.

Keyframe 6y ago
Of course. That's the primary reason I'm personally against tasks on the interview itself or whiteboarding. That's usually a shitshow. We first do an interview where we talk a bit about our company and the interviewee, we get to know each other out a bit and try to find out if we're a good match for each other, based on the talk itself. If that's the case, we give a small (really small and basic, unless a senior position) assignment to take home and get back to us in five days. People have schedules, obligations, we understand. During the period we're always available for any questions, doubts, whatever you need. Assignment itself takes a couple of hours at most for someone that knows / has used the tech. At home, you can use google, stackoverflow, friends, books, I don't care. No one cares, as long as you show up with a consistently-looking code that works and that we can comment together on. You know, same as at work. Something to talk about for a bit, if at all. It's the basics. A damn good filter, it turns out.