Depends on the position. If they're interviewing for frontend it definitely should be. For backend is going to depend on what they happen to use. For your first job they may or may not expect you to be familiar with their language of choice and instead have you writing pseudo code during the interview. More on reddit.com

Any tips on what kinda things would come up?

• arrays

• objects

• functions

• inheritance

• scope

• closure

• ajax/xmlhttprequest

• unit testing

• node.js

• DOM

• favorite tools

• code organization

• thoughts on build tools/dependencies

• accessibility

• security

• events

• event loop

• promises

• callbacks

• A/B testing

• thoughts on frameworks: angular, react, ember

• thoughts on code extending utilities: lodash, backbone, jquery, express

• thoughts on vanilla js

If I were interviewing you I would start with abstract subjects I would expect experts to know and then gradually dial back my questions until I can pinpoint your approximate level of expertise. I wouldn't ask anything super specific, because that is what references are for and I am not trying to be an ass. I also wouldn't ask you to solve any code problems, but I might ask you to demonstrate an answer with code if words aren't enough for me to understand your position. A good interviewer wants to help the candidates relax and feel comfortable because they get much better (and honest) answers to consider. Not everybody is a good interview though.

More on reddit.com

I dislike these kinds of tests in interviews, but in the interests of a good and useful discussion here... JavaScript is not multi-threaded. No way, no how (setting aside WebWorkers and what-not). So the setInterval call says, "make a note to yourself to run this function no less than every 1,000 milliseconds, or one second." Then you are told that the loop takes four seconds to run. But during those four seconds, it never cedes control of the single execution thread. So func1 is still sitting there, waiting to be executed. When the loop completes, the JavaScript engine looks around to see if there's anything to do and yes, func1 is overdue by three seconds. So it executes func1 once and then queues it up to be executed no less than 1,000 milliseconds later. UPDATE: four times right after each other, because four seconds had passed. So the answer is, it doesn't execute at all during those four seconds that JavaScript is executing the loop. Normally I try to use these opportunities to pimp my JavaScript book, but speaking very frankly, I avoided this topic entirely and it can't help you :-( More on reddit.com

Makes me feel better (or worse 🤔) as I go into an interview tomorrow haha. Thanks for sharing.

More on reddit.com