I think that a deeply understanding of callback, promises, and asynchronous things are top questions atm More on reddit.com

All our js is front ends for APIs, so I’d definitely ask about promises, familiarity with REST APIs (how to call them, handle responses). I usually ask a few more basic questions about truthiness and things like double equals vs triple equals. More general web stuff/software dev stuff would be things like responsive design, css/sass, git, agile, unit testing, etc. Personally I wouldn’t care much if you know how to do DOM manipulation if we’re using React, but everyone is different. One piece of advice is don’t try to BS any answers. If you don’t know, be straightforward and ask them about it. Showing interest to learn should be a large part of what they are looking for, and there’s nothing worse than being called out on your own BS. More on reddit.com

I wouldn't care if a candidate doesn't know about hoisting, debouncing and throttling. I don't see these as core JS concepts. Well, I take that back, hoisting obviously is. But I've been doing JS development since '97 professionally and I can't honestly think of a single instance where I had to know anything about hoisting. Maybe that's simply because I've always written code in a logical way, hence hoisting doesn't tend to be a factor. Debouncing and throttling are ideas you can easily learn if and when the need arise, not something you have to know cold in my opinion. The rest are reasonable to test for, though I personally wouldn't consider someone that didn't know some of them disqualified immediately. It would just be one factor among many to consider. More on reddit.com

Thanks for sharing this - looks great! Will be helpful for a lot of people. More on reddit.com