Ask HN: What % of your job interviewees pass FizzBuzz type questions?
21–30 of 120 posts
Re: Ask HN: What % of your job interviewees pass FizzBuzz type questions?
#22Re: Ask HN: What % of your job interviewees pass FizzBuzz type questions?
#23The last time I was a part of this activity in a company (1997-8), using similarly rigorous pre-screening, we had about the same results, only 50% of the people we interviewed could program their way out of an (EDIT) wet paper bag.
Re: Ask HN: What % of your job interviewees pass FizzBuzz type questions?
#24I'm curious what candidates are getting stuck on. Is it the testing for divisibility that's tripping them up?
Re: Ask HN: What % of your job interviewees pass FizzBuzz type questions?
#25On average it takes people around 5 minutes to do.
We have people do it on a whiteboard to get them standing up and moving.
Re: Ask HN: What % of your job interviewees pass FizzBuzz type questions?
#26Earlier quoted context omitted.
Ok fair enough, but I'm still curious where the sticking point is. Can they at least code the loop? I'm wondering if it's just that peoples' math skills are typical pretty rusty and if using another set of conditions would give you better results. Edit: For example, iterate through this string every time you hit an 's' print fizz etc...
For some reason this is the most common mistake I see from students: for i in range(0,n): if i % 3 == 0: print 'fizz' elif i % 5 == 0: print 'buzz' elif (i % 3 == 0) and (i % 5 == 0): print 'fizzbuzz' else print i It's not so much arithmetic that's the problem but reasoning about overlapping boolean conditions.
I wonder if people are getting such bad results on this because it's always the first question they ask and the candidate isn't comfortable yet.
Re: Ask HN: What % of your job interviewees pass FizzBuzz type questions?
#27Of those that passed: one had Masters in Library Science looking to change careers. The other was a fresh out of college CS major from Illinois State.
Next batch, I think we'll add another trivial question: count the number of vowels (a, e, i, o, u) in a string.
Re: Ask HN: What % of your job interviewees pass FizzBuzz type questions?
#28Earlier quoted context omitted.
Ok fair enough, but I'm still curious where the sticking point is. Can they at least code the loop? I'm wondering if it's just that peoples' math skills are typical pretty rusty and if using another set of conditions would give you better results. Edit: For example, iterate through this string every time you hit an 's' print fizz etc...
For some reason this is the most common mistake I see from students: for i in range(0,n): if i % 3 == 0: print 'fizz' elif i % 5 == 0: print 'buzz' elif (i % 3 == 0) and (i % 5 == 0): print 'fizzbuzz' else print i It's not so much arithmetic that's the problem but reasoning about overlapping boolean conditions.
I think the problem is the old adage about not being able to to see the forest for the trees.
They break it down to the simple components and write those fairly easily but the forget about big picture of all 3 conditions working together.
Re: Ask HN: What % of your job interviewees pass FizzBuzz type questions?
#29Just curious if you expect perfect code on a sheet of paper or give them an IDE and say go for it. As I remember fizzbuzz (print numbers 1 thru x, then fizz if divisible by 3, buzz if divisible by 5, fizzbuzz if divisible by both) I did it in a text editor in under a minute. Got two errors because I did it without thinking, fixed it, and had a working solution in 90 seconds. It's taking me longer to write this respon…
These sorts of tests are low pass filters, they're not designed to find good or great programmers, just confirm that the person can program at all (as we define it). Since most people who call themselves programmers really aren't, they're highly useful. Anyone who's looking for perfection of this nature in an interview and who fails a candidate for lacking that is doing the latter a favor by not hiring them.
Re: Ask HN: What % of your job interviewees pass FizzBuzz type questions?
#30I wish we would run at least some kind of sample problem before hiring people. sigh