Quote:
Originally Posted by adios
I realize that this is a simple exercise but not sure it is accomplishing what your organization wants it to accomplish. This seems like an exercise to weed out people who are lying about their development skills. If they can't meet expectations in doing this problem they're not really competent. In my view interviews are stressful so flubbing a problem like this, especially in an interview setting, may not be that big of a deal. A sloppy solution to me from an otherwise competent candidate wouldn't necessarily be a deal breaker. How often does your organization demand that developers design algorithms that require the skills to solve FuzzBuzz like problems?
I can understand if a lot of people are getting interviews that aren't competent but not sure this kind of test means all that much. If the candidate is writing code on a white board I'm sure it doesn't mean that much. The candidate will probably developing code on a workstation. Just an example.
A simple programming question done early in a phone screen is by far, like not even close, the single best interviewing question/technique. It doesn't require much time investment, gives you very few false negatives, and probably weeds out about 50% of the people you choose to interview.
Very few people are so nervous that they flub basic programming questions. And even if it is a matter of nerves, it means I'm just not going to be able to figure out what skills they have in a standard interview. I'm always going to prefer passing on the rare nervous good candidate then hire people that I can't verify know how to program.
Quote:
Originally Posted by adios
A sloppy solution to me from an otherwise competent candidate wouldn't necessarily be a deal breaker. How often does your organization demand that developers design algorithms that require the skills to solve FuzzBuzz like problems?
And just on this part, what kind of programming job doesn't require regular use of for loops and if statements? Thats the whole point of a FizzBuzz type problem, the 'algorithm' if you will is obvious and its just up to the candidate to use simple programming techniques to implement it.