It works to make your interviewer position you inside of a scope of possible choices. The closer you are to an “advanced” level developer, the higher your chances of getting a job.
In today's video, I'll outline the most essential JS questions you should prepare for when it comes to coding interviews and how each one might affect you when it comes to getting you the job or not.
Transcript Of The Video
Are you using ES6? Yes, no? If so, yes and why or no and why? I expect an answer either way and I want some really good understanding here of like, yeah, I'm using ES6, which the why doesn't have to be super compelling because ES6 on it's own is very compelling to use for all the different features it provides. If you say yes, though, I do expect your favorite feature and that would be my followup question then. What is your favorite feature you're using? Mine is destructuring, absolutely love it. It makes my life really easy. So what is yours?
Another question I like to ask generally in a coding dow question where I'll give him a fiddle or something to that nature is what is hoisting or I'm going to show them a hoisting problem and just see if they can solve it. With that being said, hoisting is much more advanced and running the hoisting issues is not always common for a lot of people, but it will show me the level of developer you're at.
The difference being between Async and synchronous and showing you a synchronous code and asynchronous code and telling me the difference between them, but I'm going to make them look very similar but I'm gonna want you to tell me which is synchronous, which is asynchronous, because a problem far too often is people write code and think it's going to be synchronous because of how they wrote it, but truth be told it's not. It's asynchronous. Maybe they didn't put a return in. Maybe they didn't use callbacks correctly. There's a lot of things that can go on between async and synchronous code that people can screw up all the time and this is one of the places I like to check to see that you know how to code between the two because it's an easy problem to have and then creates timing issues down the road. That one is a little more advanced too, but this is also where I'm gauging based on these answers I'm going to give you, easier or harder coding question.
I'm also going to ask this question. I'm going to look and see if you know the difference between global and block level scope. This is a much more basic question. It's if you have a VAR, not even VAR, just you have a let outside of all functions at the very top of the file, that is global.
Dot verse bracket notation. When do you use one over the other? I see it much more as a basic question because if you want to be dynamic, you need bracket and if you know your variables you can just use dot.