Re:The Non-Programming Programmer
by Retric on Monday February 22, 2010 @10:50AM
(#1142885)
Google lost a lot of good people by dragging out their interview process. It's not all or nothing, but if I disliked the first interview I am unlikely to be interested in doing a second one. In the back of my mind I can't help but wonder if I want to work for people desperate enough to jump though these hoops.
[ Parent
| on HN ]
Re:The Non-Programming Programmer
by RiderOfGiraffes on Monday February 22, 2010 @11:03AM
(#1142930)
You make it sound like it's a big deal to write 10 lines of code before being interviewed. I agree that some candidates, possibly including me, would be put off by being asked to solve a problem requiring 10s of hours before interview, but we're not talking about that. We're talking about getting someone to demonstrate 10 lines of working code.
And if a potential candidate can't be bothered to do that, how bothered will they be to make small, uninteresting changes to working code? How interested will they be to fix a corner case they don't care about? How careful will they be about details when releasing code?
Not being willing to "jump through hoops" is an indication of fit, as much as many other things. My job is to make the hoops as big as possible, and as easy to jump through as I can make them. If people can't be bothered, then I guess I won't employ them.
Yes, it biases the selection process, but it's a huge save not interviewing people who can't, or won't, produce FizzBuzz (or similar).
The issue is showing up for a second, third, or fifth day of interviews. If you want to know something about my technical competence fine, figure that out over the phone or use a webbapp.
You obviously haven't interviewed at google. I had 6 technical interviews, 7 if you count the phone screening. From the day their recruiter called me to the day they called and said they weren't interested spanned about 3-4 months.