3 ms·
1) If you're doing FizzBuzz at an on-site interview, you've failed in your process. FizzBuzz is something you use as early as possible to weed out clearly incom
by henrikschroder 11y ago
1) If you're doing FizzBuzz at an on-site interview, you've failed in your process. FizzBuzz is something you use as early as possible to weed out clearly incompetent developers.
2) I can see how a clever developer might get stuck in analysis paralysis, but even then you should be able to coax them out of it, and at least get them to write down a little bit of code that does a loop and an if statement, because that's what we're really checking: Can this individual write working code from scratch?
(And if you can't coax them out of it for this, how the hell are you going to be able to do the same for real problems?)
- talmand 11y agoBut how do you administer something FizzBuzz outside of an on-site interview? How do you know they actually completed the task without being with them when they did? I'm guessing Skype interview or something similar?
- henrikschroder 11y agoI'm using a simple shared editor such as collabedit or similar. You send the link to the shared space along with the phone number for the interview, and you let the candidate know that there will be some simple shared exercises so they need to be at a computer. And then you ask your questions, and do FizzBuzz or similar, and watch them code.