This doesn’t assess anything meaningful, it’s an ego trip for the interviewer. Ugh.
This doesn’t assess anything meaningful, it’s an ego trip for the interviewer. Ugh.
However, all of these "don't use the right tools" and "write extremely compact code" rules mostly select for people who are good in code golf, not for people who can solve actual business problems or write maintainable software.
And it seems like this was the only programming challenge in the whole interview?!
The extra rules presented sequentially and their interactions might have revealed more about both parties, but it's hard to tell without seeing them in person.
FizzBuzz works well enough as a lowest common denominator screening test, but it doesn't scale up. At its core, it's an entirely made up problem with no relevance to anything you may ever do at a job. How do you evaluate requirements for a problem that is not real?
The higher level the skills you want to test, the more realistic your questions have to get.
A few have a trick or insight but I haven’t ran across those in interviews.