> is to ensure the programmer does not try to write this exact code I agree with your thoughts around the language constraints, but I see more room for what yo

> is to ensure the programmer does not try to write this exact code I agree with your thoughts around the language constraints, but I see more room for what you once could have gotten from using FizzBuzz as a minimum-skill filter. It depends on the level you're hiring at. From a novice engineer I would be content if they're demonstrating awareness that multiples of 15 represent an edge case without it being included in the instructions. If I'm hiring someone more senior, I'd expect them to provide (or iterate to) a more optimized solution to FizzBuzz. But in a further tangent - I think this using this type of question as a minimum-talent filter stopped becoming viable as soon as it became commonly used. In the time since, it's become more a minimum-knowledge filter -- and that doesn't tell you anything about the candidate's methods in solving a problem with derivable requirements.