3 ms·
Knowing that they can is useless because a) their job is never going to involve solving FizzBuzz or 99 bottles of beer, and b) it is not indicative of anything
by johncoltrane 3y ago
Knowing that they can is useless because a) their job is never going to involve solving FizzBuzz or 99 bottles of beer, and b) it is not indicative of anything useful.
Knowing that they can't is equally useless… and for the same reasons.
It is totally irrelevant.
- qd011 3y agoIt tests whether you can write a simple loop with a couple of ifs - not being able to do it is definitely an indicator that you won't be able to complete more advanced programming tasks. And pretty much any other programming task is more advanced.
- johncoltrane 3y agoThe technical interview stage is a tiny bit too late for wondering if the candidate can write a simple loop.
- hnfong 3y agoBefore you do a technical interview, you send them a website and ask them to write that FizzBuzz equivalent for you, or if you want to be seen to be nice, schedule a 30 minute interview with them and ask the FizzBuzz thing. It doesn't have to be asked during the full technical interview stage.
- johncoltrane 3y agoAgain, I see zero value in those silly tests so I won't force them on anyone, at any stage of the process. That would be a waste of everyone's time.
- paulcole 3y agoWhy would you do fizzbuzz in a technical interview and not have them talk through it in the first 15 minute phone screen?
- johncoltrane 3y agoNot even one minute. Those things are worthless.
- paulcole 3y agoOh sorry, didn’t realize.