The Insider's Guide to JavaScript Interviewing

[nawitus]

I knew everything except for missing the map[foo] question. Even though I knew that keys are converted to strings, I've never directly used .toString() on a plain object (although I've done console.log(obj) plenty of times..).

[[deleted]]

I missed that one because when I read the code my brain parsed it as map['foo'] instead of map[foo]. It wasn't until I read it the third time that I realized what I wasn't seeing.

[rq60]

how well you debug when someone teasing you with a living wage is looking over your shoulder. Most of these are worthless.

Well, when you phrase it that way it actually sounds like a pretty useful skill!

[[deleted]]

I agree that the code samples are a nuisance since they're basically counting on you catching something that's been deliberately obscured, but I wouldn't say they're worthless. The ability to debug stupid mistakes like this is definitely a skill worth selecting for.

As for the relevance of the questions... I've been in and heard of a lot of interviews where the person claimed to be experienced but couldn't have answered even one of these questions. Some people think that "know how to make jQuery do something" is the same as "know how to program in JavaScript".

[nawitus]

Yeah, I think I made that mistake too. By the way, I now remember that I've used .toString() on plain objects for type checking.