3 ms·
> If you think about joining a dev team where no one checked if any candidate could FizzBuzz, you can imagine the workplace environment that can end up with. T
by 908B64B197 5y ago
> If you think about joining a dev team where no one checked if any candidate could FizzBuzz, you can imagine the workplace environment that can end up with.
That sounds hilarious How could a dev team not be able to write 5 lines?
- pc86 5y agoYou would be surprised how many people legitimately can't wrap their heads around a fizz buzz style problem, but also how many people who can yet completely freeze in an interview setting.
- rytor718 5y agoThis. I think most people devs, including low skill, understand Fizzbuzz, but performing on the spot is just very difficult for many people. Its the same reason why a top notch, genious writer can turn out to be terrible at giving speeches, even if they're reading from a script. Performing an interview is a different skill from writing code.
- cwalv 5y ago> Performing an interview is a different skill from writing code. I think this is true for the day-long leetcode interviews, but to succeed as an engineer, even at the entry level, I think you need to be able to talk through how you would solve fizzbuzz. A big part of the job is communicating trade offs with other engineers.
- rytor718 5y agoYou're not wrong, but the problem is that interviews aren't actually about jobs. The average person interviews because they need the money. So from the start they're not thinking in the programming space. The pressure for them is to make the interviewer believe they are worthy of the job. I think if I could describe my personal experiences, I'd say that on a subconscious level, I know that how I speak and articulate details will be observed by the interviewer through a cultural lens more often than not. This may be unique to my personal background, so maybe this is different for other groups. But interviewers often get hung up on the use of different language/terminology, the types of jokes/jests that enter the conversation, how I respond to their language. And there's sometimes been an unwillingness to allow different terminology, perhaps because that's all the interviewer themselves knows and understands. All that to say, a code interview doesn't always come down to the quality of the code.
- sergiotapia 5y agoIt is hilarious but man, you would be really surprised how people choke on this. It's weird. People with 10+ years writing software can't do this sometimes.
- jlund-molfese 5y agoI was once accused of lying about my work experience by a $FORTUNE500 interviewer when I failed to articulate what a CSS flexbox was for a backend dev position. Such an eye-opening experience! Now that I’m on the other side of the table these days, I understand the importance of making interviewees feel comfortable and asking questions that allow them to start off strong.
- Igelau 5y agoI'd believe it. I got shitlisted at one place for being the only dev with the mathematical insight to know that multiplying pesos by a dollars:yen ratio doesn't yield a correct conversion of pesos to yen. They let that one slide without fixing it, but the final straw that got me frogmarched was refactoring an if-else to a switch.
- verall 5y agoRefactor to switch?? All of those break statements are evil!!
- 908B64B197 5y agoSounds like a hidden arbitrage opportunity if they accept to honor that conversion rate!
- pryelluw 5y agoLast year I did a project for an org that has a similarly sized team of developers. They could not figure out html and css. Hadn’t heard about git. And worse is that they developed on the production server. I’m not making this shit up. They saw me as a god for fixing their shit and offered to hire me. No thanks!