> I don’t think it would be fair to name and shame them.
I disagree, but of course that's entirely up to you.
The FizzBuzz that did not get me the job
11–20 of 460 posts
Re: The FizzBuzz that did not get me the job
#12I think you’re an A player. You were rejected by a B player that was looking to hire C players.
Apply to other companies. In this case it’s not you, it’s them.
Re: The FizzBuzz that did not get me the job
#13I love FizzBuzz as an interview question and then dive into tail recursion and compiler optimization. I learned a lot from candidates. I miss my interviewing days.
[deleted]
Re: The FizzBuzz that did not get me the job
#14I predict that very soon you are going to be offered a remote job paying more than €50,000/year.
That’s due to this excellent post about your excellent abilities and reasoning appearing on HN.
¡Mucha suerte!
Re: The FizzBuzz that did not get me the job
#15I've created a joke Python library, hoping that I would get asked to code it in an interview. No luck so far
Re: The FizzBuzz that did not get me the job
#16I 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.
Re: The FizzBuzz that did not get me the job
#17I loved the article and would probably have hired this person. But as a suggestion to them: if an interviewer says "I don't think that will be a good idea" just take the hint that it won't be what the expect and change it. Also reminded me of my compiler class, we had some homework to write a pascal/C transpiler and a friend of mine somehow managed to implement it via bison errors(?). The teacher was not happy but ha…
At work, would you rather have a boss that makes you implement dumb ideas? Or would you prefer a boss who recognises that your idea is better, then rewards you for it?
You are interviewing them too.
I would also have hired the candidate.
Re: The FizzBuzz that did not get me the job
#18This article describes everything that's wrong with tech hiring these days. There is zero evidence that success on these arbitrary programming riddles have any correlation with success on the job, and yet we force candidates through a gauntlet of completely unrealistic brain teasers solving problems that they will literally never have to solve on the job.
I've recently completed half a dozen 2-4 hour coding challenges, gotten a perfect score according to the tests provided, and after a couple of weeks, gotten a boilerplate rejection email.
What's the point?
Re: The FizzBuzz that did not get me the job
#19I've worked for companies in NL whose tech interview wasn't nearly this involved but the wages offered were comparable or better; I seriously doubt any of the skills asked or demonstrated in the interview would actually be necessary for this job, not when it's just node which in all likelihood means it's mostly REST like APIs and some business logic. (I'm making some sweeping generalizations here)
Re: The FizzBuzz that did not get me the job
#20I love FizzBuzz as an interview question and then dive into tail recursion and compiler optimization. I learned a lot from candidates. I miss my interviewing days.
They solved a lot of our problems we didn't find good solutions for! (/s)
I never had, sadly, compiler optimization problems, I mostly did simple web database frontends for 30 years. Code monkey stuff.