3 ms·
I used to give fizz buzz with zero additions. Just write me a fizz buzz in c#. We didn’t actually want to take up a lot of the interviewee’s time. There were ot
by sixothree 2y ago
I used to give fizz buzz with zero additions. Just write me a fizz buzz in c#. We didn’t actually want to take up a lot of the interviewee’s time. There were other tests, tests better than any programming tests. They had to take like one for SQL and one with nothing but logic puzzles, the latter of which is most indicative of whether a person will be competent at the job.
Fizz buzz just lets me see their coding style (single letter variables, lack of curly braces after ifs, comments, platform - console, web, service) and whether they’re willing to allow simple mistakes into their finished product. So many mistakes.
But it’s the least I can do to get some information out of a candidate who is already overburdened by the process.
- whstl 2y agoA 2 minute Fizz Buzz at the beginning of the interview is great to filter people who managed to fool the recruiter. It is also a cool opportunity to "talk shop" if they go for a strange solution.
- joseda-hg 2y agoBased on the general reacion from some of the comments here, going for strange/novel solutions is seen as something to be avoided though
- whstl 2y agoStrange comes with the territory, though. The requirements were way stranger and quirky than the solution, and wouldn’t really lead to any production-ready code… Lots of comments complaining about the code completely glossed over the requirements.