2 ms·
> 1 hour of pairing/programming during an arranged face to face interview. If the test is well designed, touches on a number of areas and self contained, I thin
by dahart 9y ago
> 1 hour of pairing/programming during an arranged face to face interview. If the test is well designed, touches on a number of areas and self contained, I think this was sufficient for me to assess their skills.
Sounds great. I've done this too, but I've never done it before screening candidates. I don't have enough time to screen candidates by programming with them.
> "Mimic real life" means no puzzles (unless I've literally experienced them in real life), no binary tree reversals and no big O notation questions.
Understood. My goal with my coding quizzes and knowledge questions is not to mimic real life. It's to asses the boundaries of the candidate's education and experience, without regard to skill.
> I think that type of thinking leads to embarrassments like this
There always have been and always will be false negatives, even with lengthy face-to-face interviews, even with pair programming, and even with paid internships.
One high profile false negative anecdote, while unfortunate, doesn't imply there's a widespread or unexpected problem. Applying for jobs always comes with a risk of not getting the job for a wide variety of factors that are outside the candidate's control. If it's a job you really want, all you can do is try hard.
I love homebrew, and I'm sure @mxcl is a fabulous coder, but the tweet you shared does make it sound like he expected to get the job without an interview, and might have come across that way, or might have not prepared at all.
- crdoconnor 9y ago>I've never done it before screening candidates No me neither. I screened with a 5 minute fizz buzz like task and CV fits. Bad programmers slipped through the net (and were caught by the test) but I never got anybody who literally couldnt code. I was happy with that balance. I was afraid if I made it longer than 5 mins we'd filter out good candidates who couldn't be bothered with our bullshit. >One high profile false negative anecdote, while unfortunate, doesn't imply there's a widespread or unexpected problem. It does imply that it just doesn't prove it. A wanton disregard for realism in interviewing is, in my experience, very clearly systemic and industry-wide. >tweet you shared does make it sound like he expected to get the job without an interview Seriously wtf? I think you're starstruck by Google and that is affecting your judgement. Asking him about binary trees was dumb. Unless Google place him somewhere patently unsuitable for his skill set (kernel hacking/low level database code), he won't be using binary trees.
- dahart 9y ago> It does imply that it just doesn't prove it. @mxcl's experience doesn't imply it either. The only evidence for a widespread problem is the number of people who have that problem. I have never had an interview where I felt rejected for what I thought was a single dumb question, ever. And I've never seen it happen to someone I know personally, or at a company I've worked for. > A wanton disregard for realism in interviewing is, in my experience, very clearly systemic and industry-wide. I don't necessarily disagree with this, but could you elaborate more on what bad things are actually happening that affect people? Are good coders, by and large, not able to get jobs? Are good coders having statistically significant problems getting paid or finding enjoyable work? I don't think so. Please elaborate on what actual damage is being done, I'm not seeing any. > Seriously wtf? Seriously. I don't know what happened, but I'm not automatically on the side of @mxcl because he was turned down or because I'm a fan of Homebrew. He might be exaggerating what happened. Do you know for a fact that it was specifically the binary tree question and nothing else in his interview that lost his chances there? For all I know, the binary tree question was put there just to see if he would scoff at actual programming questions given his high profile status, and he failed because he scoffed and not because he got it wrong. > I think you're starstruck by Google and that is affecting your judgement. Why? What have I said that suggests I'm a fan of Google at all? It seems to me like you're making wild assumptions here. > Asking him about binary trees was dumb. That's an opinion. One that is based on not knowing why the question was there, or what the other questions were. I do ask questions on topics that I don't expect the candidate to use in their job. I'm interested in whether they paid attention in school. I'm interested in what they know, regardless of their skill. I'm interested in what they don't know, and where their limits are. I'm interested to know if people are curious about software. I'm interested to know how people react to questions they don't know the answer to. And I have a rule to specifically reject candidates that get upset about being asked technical questions. Those are people I don't want to work with. None of that precludes asking some realistic questions about things people will use on the job, in addition to any unrealistic ones.
- crdoconnor 9y ago>I have never had an interview where I felt rejected for what I thought was a single dumb question, ever. This is moving the goalposts. That is not the same thing as a wanton disregard for realism. Have you been asked interview questions and set tasks which were not related to what you actually do day in day out? I have. LOTS. >I don't necessarily disagree with this, but could you elaborate more on what bad things are actually happening that affect people? Are good coders, by and large, not able to get jobs? Are good coders having statistically significant problems getting paid or finding enjoyable work? I don't think so. Please elaborate on what actual damage is being done, I'm not seeing any. Um, more false positives and more false negatives. It honestly feels weird having to justify why realism in testing is important. It feels so damned obvious to me. Would you design a purposefully unrealistic scientific experiment? Create a deliberately unrealistic automated test? What's special about interviewing that realism is of secondary or tertiary concern? What is more important than realism? >I'm not automatically on the side of @mxcl because he was turned down It feels kind of like you're automatically on Google's side. The part that made me go what the fuck was when you said "he makes it sound like he expected to get the job without an interview" when he neither said nor implied anything of the sort. And, earlier you took it as a kind of article of faith that everybody at google was obviously super smart, because Google. There's definitely some bias there. >I'm interested in whether they paid attention in school. That's cool. I'm interested in whether they can do their job and I think it's kind of weird how people are seemingly so keen on setting tasks that test anything but that. >None of that precludes asking some realistic questions Strictly speaking asking what their favorite kind of chocolate is doesn't preclude that either, but there's a limited time available to interview and a limited amount that can be learned from asking them that - or indeed - anything else of tangential relevance.