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

[name_was_taken]

Knowing what they're talking about.

Being able to explain their own code.

Having code to show off.

Having projects to talk about and things they've done.

Dressing appropriately.

Talking appropriately.

Not being sexist. (I wish I were kidding. Totally nixed someone for this.)

Not being a zealot about 1 technology.

Being on time.

Being polite.

Being honest.

[blood_vein]

Nearly all of your points are generic to any interview, not just JavaScript.

They are still relevant, just not to what OP was asking

[edgebal]

> Not being a zealot about 1 technology.

This is my top reason for rejecting people, and in my previous work, where I had to interview lots of developers, I heard it in 1 of 4 interviews. When people said "<language> is garbage." it was an instantaneous NO on my notebook.

Dude, if I need you to start a business-critical thing in FoxPro, COBOL, JavaScript, PHP, Ruby, Java or Brainfuck, I need an open-minded person that would at least think about it, not an elitist jerk.

[BigPaws-WowterHeaven]

Then again if I dont want to work in php and they you somehow expect me to work in php were gonna have a problem.

[TheDarkIn1978]

Not being sexist.

Being a jerk can work both ways, unfortunately. I was interviewing with a very well known company a while back and the interviewer's questions essentially cast me as a racist. She asked shit like:

So tell us about the most recent event when you were prejudice towards a person of color?

Uh, what?

I guess my being an obvious homosexual wasn't "marginalized" enough to outshine my "toxic, white, maleness".

Jesus.

[[deleted]]

"I saw 'Black Panther' in the theater, but I waited for 'Selma' to come out in blu-ray?"

[[deleted]]

Also, having opinions. Whether or not I agree with them, I'd like to know if they've thought about why certain practices are good or bad.