6 ms·
Fizzbuzzed
- jpetersonmn 12y agoI've been programming for a couple years now, part time. I work in IT troubleshooting proprietary software on customer's machines. I've written several vb.net applications to automate things in the office. (Screen scraping/website automation, log file readers/parsers,, etc...) Lately I've been working in python more for my screen scraping needs and also learning web2py. I've thought about trying to apply for a programming job where I work, or at least maybe see if I can shadow a programmer to see what it's like. I've always been put off by thinking that I'd just be embarrassed because I'm not good enough and they'd laugh at my code. Nobody in my group at work does any kind of coding or scripting, and all my work is proprietary and I can't really share it on the internet for feedback. I've heard of this fizzbuzz test before, but just now looked up what it is exactly. I can't believe how easy that is, and that people are actually failing at it. Makes me feel like maybe I should apply for some of the developer jobs at our company.
- Alupis 12y ago> I'd just be embarrassed because I'm not good enough and they'd laugh at my code. I don't think one is a good programmer until one believes themself to be a bad programmer. When I was more green, I used to think "I've got this!", but as I learned more, I began to realize how little I really knew.
- gojomo 12y agoAlso look up [Dunning-Kruger effect]. You know enough to be worried you don't know enough! Definitely apply for developer positions, or work on external projects, where the details of your work can be discussed with other technical peers – not just its output as evaluated by non-technical people. It's the best way to improve.
- bichiliad 12y agoTo clarify, I don't think "Fizzbuzz" necessarily means "printing out Fizz on multiples of 3, Buzz on multiples of 5, etc." Fizzbuzz generally refers to a simple programming test to make sure candidates can actually write some amount of code.
- jeffasinger 12y agoI've interviewed people for a junior position recently. I gave the FizzBuzz test, verbatim from Wikipedia. Only about 10% were able to do it on a whiteboard, without help.
- opendais 12y agoI can't write any code effectively on a whiteboard in front of an audience. -> I'm a terrible programmer. TIL I'm a terrible programmer.
- pkaye 12y agoAn audience of one. What about on a piece of paper? In front of a computer. How would do in code reviews? You can state your concerns to the interviewer to see if they can accommodate.
- opendais 12y agoI've never seen a whiteboard interview with only one interviewer. The smallest was 2. Whiteboards are for diagramming things more complicated than lines of code. [e.g. Interactions between several web services or paths of control across entire programs] I've honestly just accepted that by the standards of many people's interviewing processes I'm a bad programmer. :)
- HeyLaughingBoy 12y agoYup. Hell, if you think you can do it, but you're put off by a whiteboard, I'll get you a laptop with a development environment on it and leave the room to let you work on the problem. Interviews are stressful. Keeping the candidate relaxed should be on the interviewer's mind.
- unoti 12y agoNo, it literally means what you said above, and the majority of applicants literally can't do it. It's shocking and sounds ridiculous, but is true.
- bcj 12y ago> I've always been put off by thinking that I'd just be embarrassed because I'm not good enough and they'd laugh at my code. The good news is that you already sound like a programmer. It's been a decade since I first started programming and I'm excited when I don't cringe at code I wrote half a year ago. The fact that you seem driven and willing to learn should be assets when you are applying.
- 3pt14159 12y agoI struggled with this when I was responsible for hiring at 500px before I moved on. The key is to ask for code samples ahead of time. It doesn't necessarily have to be open source contributions, though that slightly preferred, but I refused to interview someone that didn't have code samples. I went from 30 interviews per one hire to about 2 or 3. The most common problem being a potential candidate not knowing enough of the internet stack to be truly useful (for example, knowing only rails, but having no real knowledge of how AJAX worked, or load balancers, or databases, or DNS, etc).
- jtratner2 12y agoHow did you handle people with no open source contributions? I'd imagine most non-OSS code would be under an NDA or something.
- 3pt14159 12y agoThey just sent me code. It is up to them to make sure that they are following NDAs. Also, sometimes code isn't open source, and it isn't NDA; like 4th year assignments or small contracts.
- jasode 12y ago>There is however one last hurdle — a written test in the form of Fizzbuzz. A "last hurdle"? Shouldn't it be the first hurdle? I thought the point of using FizzBuzz in its proper context was to be a quick filter to weed out the majority of candidates. That way, you avoid wasting interview time with them.
- Alupis 12y agoNot necessarily... you can ask for code samples up front, then later in the interview see if the candidate is actually capable of living up to the expectations set by the code samples.
- eli 12y agoI don't like making job applicants do work -- even something as simple as fizzbuzz -- if it's unlikely I'm going to hire them. Just seems unfair. Also, if I'm giving someone a test, I'd prefer they work on it in front of me, which means it won't be the first screen. And finally, I don't think struggling on FizzBuzz necessarily means "No Hire." (I actually don't really give these sort of tests at all anymore. Didn't seem that useful in practice.)
- jasode 12y ago> -- if it's unlikely I'm going to hire them. But how do you get to the "unlikely" determination? Do you want to get a ballpark reading on "unlikely" within the first 10 minutes of the interview or at the very end after investing an hour? I'm not suggesting that FizzBuzz is the be-all-end-all but for the folks who already do find useful as a low-investment bs filter, it makes the most sense to use it at the beginning of the process and not at the end. Using it as a "last hurdle" makes no sense if you have a stack of resumes to plow through. If you have prior assumptions that 90% of those candidates are not competent at programming, what's the logic in using FizzBuzz as the last step? You want to identify the 10% as quickly as possible before investing too much extended interview time.
- eli 12y agoYup, you're probably right. If you're at the end of the process and on the cusp of hiring someone to write code but you're not sure whether they can write simple code then there's probably something wrong with your process.
- dcminter 12y agoI think this Spolsky article provides some insight into why this might be the case: http://www.joelonsoftware.com/items/2005/01/27.html http://www.joelonsoftware.com/items/2005/01/27.html
- lotsofcows 12y agoWe request solutions to slightly harder problems in response to an initial application. Even though this is done at home, it still filters out a large percentage of applicants. We then do something at the same level at the start of the interview. This filters out about half of the people who have got as far as an interview. We then do an SQL test, building slowly from "select * from user" to a multi-table with sorting query. This filters out the other half. We don't hire often. Anyway, this is a very long-winded way of agreeing with Joel. I meet good programmers all the time - just rarely in interviews. Alternatively, offering the going rate is too low an offer...
- tptacek 12y ago"[W]hat is your favorite programming language / platform and why" is less a predictive interview question than it is a Rorschach blot for the interviewer. In most established tech companies --- those with, say, more than 10 employees --- interviewing is performed by a semi-arbitrary selection of line developers. If you're managing the hiring process at one of those companies, you should keep in mind that for a typical software developer, being involved in the hiring process is the closest they're going to get to participating in corporate strategy. For the time that they're in the room with a candidate, they are essentially the CEO of the hiring process. The more attention I've paid to hiring processes, the more convinced I am that this goes to people's heads. In no other job capacity do software developer's subjective beliefs and opinions get applied so directly to business outcomes.
- tomp 12y agoI understood it more in the sense that "as long as candidate can answer the question, with a sensible reason, and defend the reason" - even if the interviewer disagrees with the candidate.
- eli 12y agoYes, that's what I'm looking for what I ask this question. There's no wrong answer, but if your resume says you've developed projects in C and in Java but you are not able to articulate any reasons you might pick one over the other, I'm a little suspicious. It doesn't even really have to be languages; I mostly just want to hear you have a well-reasoned opinion on something.
- mechanical_fish 12y agoMost of the time, the factually correct answer to "why did you choose to work with Language X?" is "because when I arrived on the job, the existing software was implemented in X". Is that a well-reasoned opinion? "I'd like to pay the rent this month" is a good reason. "The company doesn't have the time to reimplement working software on a different platform" is a good reason. Of course, a well-socialized programmer understands that these answers, while truthful, are insufficient, and will have duly memorized a stock answer like "You pick C when you really need runtime performance and don't mind all the segmentation faults, otherwise you pick Java."
- coreymgilmore 12y agoI've always been a fan of "walk the walk, then talk". Basically, do FizzBuzz first then follow up with questions. Reason being, if you can't do some basic coding than its not even worth the time of having a discussion. You are, after all, hiring for a coding based position.
- Scuttles 12y agoDoesn't seem very scalable if you have a lot of applicants (unless you let them do the test at home?). I think asking for code samples up front is the best way to weed out those who aren't good candidates -- you can tell a lot about someone through their work.
- dllthomas 12y agoA few places I've applied have given me coding challenges to work on from home. None has taken me more than an hour, were relatively simple and fun, and I've never failed to get an interview afterward. I'm not entirely sure what all of that means.
- jghn 12y agoAt my work we use Codility. Every applicant is given a link to a codility test and the decision to proceed to phone screen/etc is made based on their result. There are some exceptions made, i.e. it's not a flat "you need to score at least X" but it resolves the "can you actually write some code" question up front.
- xrange 12y ago>Pretty much everyone I asked to do Fizzbuzz failed …I can't help but wonder what that really means? They gave up without producing any work? The program didn’t compile because they were typing random characters into the IDE? They were unfamiliar with the IDE, and couldn’t find the "compile" button? They couldn’t get the program to compile because of missing semicolons? The program didn’t write anything out to the terminal? The program never printed out "Fizz"? They printed out "FizzBuzz" on every line? The program never printed out numbers? The program printed out commas instead of newlines after every number? They went from 1 to 101 instead of 1 to 100?
- unoti 12y agoIt means they can't succeed in writing the code. It's not a failure to understand how to use the IDE, or a failure to understand how to compile. It's that the applicant cannot actually write even the most basic code. The fact that this is so hard to believe and yet happens so often is what makes FizzBuzz so interesting.
- justinpaulson 12y agoI also wonder this same thing. I was asked to whiteboard fizzbuzz in pseudocode during an interview, and I actually made a slight mistake, I can't remember what it was now, but I think it would have duplicated the "FizzBuzz" lines. Overall, the accuracy of my 5 minute solution had little to no insight into how I would perform as a developer. Now, if they were given time to actually compile code that ran a fizz buzz program and test it out before submitting it and STILL got it wrong...that might be questionable. But I think we need more information to really see if it was a bad assessment of their abilities or truly "bad" developers.
- molf 12y agoI have done a fair share of interviewing and have asked people to do things similar to FizzBuzz in their own favourite language. When they fail, it's not about the details. (I don't mind mistakes, although I do ask and see if the candidate can spot them when given a hint.) It's amazing how many people completely and utterly fail at the task. They can't produce a loop, they can't come up with the necessary if statements, they can't even explain in pseudocode or verbally which steps need to be taken. They don't even know where to start. Sometimes it's because of anxiety or stress, but usually when it's an indication someone has no practical programming experience.
- lazyant 12y ago"[W]hat is your favorite programming language / platform and why" while a reasonably good open-ended question, students just haven't been exposed for long enough to different languages/platforms to have an opinion, although this question (as almost any other) will certainly have the "hacker in my own time" types talking.
- patrickmay 12y agoThat's why I like it. I add "and what would you change about it if you could?" to identify those candidates who really think about their tools.
- geetee 12y agoFizzBuzz is the programming interview version of asking UK Chancellor George Osborne what 7x8 is[1]. [1]http://www.bbc.com/news/blogs-magazine-monitor-28143553 http://www.bbc.com/news/blogs-magazine-monitor-28143553
- logfromblammo 12y agoFizzBuzz is just a bozo filter. Sure, it screens out unqualified applicants. But why are you even getting unqualified applicants in the first place? It's because your hiring strategy is fundamentally flawed. When I go out to look at job postings, that is all that I see. Single, standalone jobs. What I really need to see is an entire career track within the same company, from green rookie all the way up to the highest non-executive position on that track. If I saw that, I could self-select for the position that is most appropriate to my current skill level. You wouldn't need to use FizzBuzz as my bozo filter. You would have to use a more difficult task, such as prioritizing a list of bugs and feature requests in a hypothetical program, based on perceived severity, resource requirements, and business needs. But it seems like companies now only ever want developers with 5-10 years of experience in all the techs from the stack that they already use, and there are no promotions except into management. Where do they imagine those people come from? Where do they think those people go after they age out? Is there some developer nursery out there that takes green rookies, trains them up into competent developers, and then just forces them to leave? Is there a developer nursing home that hires only grizzled, jaded old veterans and pays them all handsomely to do work that never involves any training? The reason that you need an ever-increasing amount of bozo filters is because your job openings do not match the profile of job-seekers. Unqualified applicants are clogging your system because your posting is the closest thing they can find to their own skills. Bozo filters treat the symptom. The only cure is to give all those bozos their own jobs to apply for. If your company is large enough to support that many positions, you really should establish complete career tracks, across all levels of experience, and advertise them as a whole to job seekers, so they can tell you what rung of the ladder they think they should be on. In short, you advertise all the positions that already exist at your company, the number of vacancies, and how those positions are linked by promotion. Anyone applying for multiple positions spanning more than two mutually exclusive skill levels is automatically filtered out as a resume spammer.
- izzydata 12y agoMakes me feel slightly more confident in my ability as someone who recently finished my CS degree, but I still feel very far behind. I find it very weird that someone even after their freshman year in such a degree program could not understand or comprehend such a simple task. I don't think anyone in my schools department would fail at these tasks after taking the introduction to programming course. Where are all these students coming from? Perhaps there is some problem with the source. It seems like they aren't being taught to understand, but are instead being taught to copy instructions in some manner.