sevensevens

@BЈовић - Hopefully the OP read that as "2 drinks worth of alcohol" so no tall doubles, high-gravity beers, or shots.

If you want to address low morale and turn-over, you have to directly ask people what they are unhappy about, and hope they trust you enough to tell the truth.

Are you Dolores Umbridge?

@NeilSlater - The main point of my post is that even knowing the answer ahead of time, 3.5 minutes is probably not enough to accomplish even a trivial task.

I ask FIzzBuzz during interviews, and just timed how long it took me to write it out in a text editor, and run it in the terminal. It was 2 minutes 11 seconds. That is without cutting-and-pasting and giving my code a quick read-over before running it in the terminal. That's not timing checking the output, which I'd expect any programmer to do before moving to the next task. Simply writing and checking FizzBuzz nine times in 30 minutes would be difficult. (NOTE: It's likely possible to write FizzBuzz a bit faster)

Don't think this has much to do with the "Tough curveball interview questions" as the OP list several questions that are quite odd. I'm assuming they are looking for clarity to those.

@cgTag - Several people have flat out failed Fizz-Buzz. As in 20 minutes of writing and have a loop that won't work. This includes "senior" developers.

@SandraK - mine generally doesn't either. If someone writes Fizz-Buzz with a loop and some if statements, I don't type it in because it's very obvious if the logic flow is correct. One-liners are usually pretty dense, and I'm asking what almost everyone would consider a super easy question so you can demonstrate minimum programming skill.

This blog post might be interesting nomoreharvarddebt.com/2012/08/03/six-figures-aint