Yes and no - part of a coding interview shouldn't just be can they get to the answer, but how do they get to the answer. If the solution to someones FizzBuzz is

Yes and no - part of a coding interview shouldn't just be can they get to the answer, but how do they get to the answer. If the solution to someones FizzBuzz is simply pre-coding the answers and printing them to the screen line by line, checking that you haven't reached the X limit in the request, then yes - you made it output everything correctly, but seriously, that's not someone who I would want working for me. In this case, you should also be judging how someone makes the sausage, and how they use the casing machine. On the other hand, another part of a good interview should be the conversation surrounding the coding exercise. Seeing if someone can come up with a better solution, or even explaining their thought process. Just because they cranked the casing machine to the left doesn't mean it is wrong either. Either way you should definitely be reserving your thoughts and evaluation until the end, since people can easily make mistakes and quickly turn around and impress you.