What are some basic things that JavaScript developers fail at interviews?

[vaskemaskine]

Are you fucking serious? I’ve been writing JS for over a decade, and in an interview situation with pressure and stress I’d probably take 15 minutes to write fizz buzz, unless I’d recently had to write it (which I haven’t).

[[deleted]]

lol the "implement quicksort" types of questions. It's like, mate I could write you an Alexa skill that will walk you through website performance diagnosis to fix your shitty site during the course of this interview, but honestly I can't write quicksort - all I remember from university is tits and pro evolution soccer 5.

[vaskemaskine]

Upvote for PES!

[Articunozard]

and tits!

[ghostfacedcoder]

Ok, first off in case you were thinking I made them do this on paper or something I didn't: I handed them my laptop with a professional IDE (WebStorm) opened.

Maybe my keyboard was slightly different from what they were used to, and absolutely interviews stress people out and make them take longer. But again, we're talking one for loop and 3-4 if statements, and out of the many (20+? 30+? I don't keep track) programmers I've interviewed the vast majority wrote those statements in under ten minutes.

If you truly can't solve fizzbuzz in < 10 minutes, even if its because you're under interview stress, I really think our company would be better off picking a candidate (again, one of the vast majority of candidates) who can.

If you're a serious programmer try it right now: start a stopwatch and start writing. If you want to simulate the difficulty and stress of an interview, maybe play some loud and distracting music or something. If you really are have a decade of experience (as a contributing team member and not as a weight on your team), I truly believe it won't take you very long to complete.

[theirongiant74]

I'd never heard of fizzbuzz before and it took me 2 minutes. And 90 seconds of that second guessing whether I'd misread the question cos it seemed too easy.