10 JavaScript concepts you need to know for interviews
Self-Learning
There are thousands of people learning JavaScript and web development in the hopes of getting a job. Often, self-learning leaves gaps in people’s understanding of the JavaScript language itself.
It’s actually surprising how little of the language is needed to make complex web pages. People making entire sites on their own often don’t have a good grasp of the fundamentals of JavaScript.
It’s rather easy to avoid the complex topics and implement features using basic skills. It’s also easy to create a website by relying on Stack Overflow without understanding the code being copied.
If you’re looking to master JavaScript interviews, check out Step Up Your JS: A Comprehensive Guide to Intermediate JavaScript
Interviews
The problem is that questions testing your understanding of JS are exactly what many tech companies ask in their interviews. It becomes clear very quickly when an applicant knows just enough to have scraped by, but doesn’t have a solid understanding the language.
Here are concepts that are frequently asked about in web development interviews. This is assuming you already know the basics such as loops, functions, and callbacks.
Concepts
- Value vs. Reference — Understand how objects, arrays, and functions are copied and passed into functions. Know that the reference is what's being copied. Understand that primitives are copied and passed by copying the value.
- Scope — Understand the difference between global scope, function scope, and block scope. Understand which variables are available where. Know how the JavaScript engine performs variable lookup.
- Hoisting — Understand that variable and function declarations are hoisted to the top of their available scope. Understand that function expressions are not hoisted.
- Closures — Know that a function retains access to the scope that it was created in. Know what this lets us do, such as data hiding, memoization, and dynamic function generation.
this
— Know the rules ofthis
binding. Know how it works, know how to figure out what it will be equal to in a function, and know why it’s useful.new
— Know how it relates to object oriented programming. Know what happens to a function called with new. Understand how the object generated by using new inherits from the function’s prototype property.apply
,call
,bind
— Know how each of these functions work. Know how to use them. Know what they do tothis
.- Prototypes & Inheritance — Understand that inheritance in JavaScript works through the
[[Prototype]]
chain. Understand how to set up inheritance through functions and objects and hownew
helps us implement it. Know what the__proto__
andprototype
properties are and what they do. - Asynchronous JS — Understand the event loop. Understand how the browser deals with user input, web requests, and events in general. Know how to recognize and correctly implement asynchronous code. Understand how JavaScript is both asynchronous and single-threaded.
- Higher Order Functions — Understand that functions are first-class objects in JavaScript and what that means. Know that returning a function from another function is perfectly legal. Understand the techniques that closures and higher order functions allow us to use.
More Resources
If the links included aren’t enough, there are countless resources out there to help you learn these concepts.
Here are resources which I’ve read or watched at least some of and can recommend. The first one is my own work.
- Step Up Your JS
- You Don’t Know JS
- JavaScript is Sexy
- javascript.com
- Frontend Masters
- Eloquent JavaScript
Good luck on your interviews.
If you found this useful, please give it a clap below so others see it as well.
Feel free to check out some of my recent work.
Step Up Your JS: A Comprehensive Guide to Intermediate JavaScript
What I learned from attending a coding bootcamp and teaching another one
Great list. I think a few things overlap. @getify, who writes many of the books and courses you mention, would tell you that ‘hoisting’ isn’t real. I think that calling something ‘closure’ just distracts from the concept of scope / which, if you understand, already takes care of that entire ‘concept’. ‘Higher order functions’ seems to be similar to ‘closure’ in the way that it names something that already exists without need for a name. Functions are values - and of course, can be passed to other functions based on the rules of JavaScript. I slowly undo things like this as I learn - and I’ve come to feel that sticking to the basic principles / instead of naming the clouds of confusion helps me better understand.