FizzBuzz Coding Interview Disaster

few hours semi-worked OMG MATH. I don't really understand the point of the question. my technical skills are sharp. serious Googling. embarrassed impossible MATH FizzBuzzed. When it came time for a technical interview with the lead developer, I felt pretty confident. Except for JavaScript 'engineering' and anything related to algorithms, my technical skills are sharp. She went him with a great talk about style guides, Sass, the designer/developer phenomenon, atomic design, content, all those awesome things that get me super stoked. Then came the coding portion. I was anticipating questions about git-ty positioning, semantics, maybe some UI based JS stuff, and development workflow. The first question was: Interviewer: Are you familiar with Fizz Buzz? Me: Um, to be honest, no. Interviewer: Ok, well, you have to write a program where multiples of three print 'Fizz' instead of the number and for the multiples of five print 'Buzz'. For numbers which are multiples of both three and five print 'FizzBuzz'. So it would look like '1, 2, Fizz, 4, Buzz, Fizz, 7, 8, Fizz, Buzz, 11, Fizz, 13, 14, FizzBuzz' Me: (OMG MATH. I tried to talk through it a bit, but then said: Me: Ok, again to be honest, my JS knowledge is more regarding UI/UX based tasks. And I don't really understand the point of the question. Like, what's the use case? When would this come up in the role? Interviewer: Well, it's an exercise in programmatic thinking. No worries, let's move on to the next question. Write a function that takes 2 timecode string and turns it into seconds. Again I started talking through it, but it was impossible for me to figure it out with someone watching. I needed to do some serious Googling. He said I could email back my solutions. I toyed with the idea of calling up and saying, "forget it, this isn't for me" but I decided to stick it out. After spending a few hours coming up with something that semi-worked, I found the solution on StackOverflow and, in my honesty, linked to it in the code. Unsurprisingly, a few days after I sent my solutions I got a "you don't have enough experience for the position, but we'd like to keep your resume on file". In my imposter-prone state, I felt like I could eat as a just googling and maybe? Query developer. I was embarrassed.

The image shows a chaotic collage of repeated reactions surrounding a central story about a software developer failing a technical interview. The punchline is that the candidate is confident in design and frontend skills but cannot solve basic FizzBuzz and timecode problems without Googling, turning ordinary programming questions into “OMG MATH” panic. It is shared as a reaction to imposter syndrome, interview anxiety, or developers who rely heavily on searching for solutions. EN: The image shows a chaotic collage of repeated reactions surrounding a central story about a software developer failing a technical interview. The punchline is that the candidate is confident in design and frontend skills but cannot solve basic FizzBuzz and timecode problems without Googling, turning ordinary programming questions into “OMG MATH” panic. It is shared as a reaction to imposter syndrome, interview anxiety, or developers who rely heavily on searching for solutions.

• @right_wing_dev_squads / 525 2020-11-09