JavaScript Interview Blog
In-depth articles on the JavaScript concepts that come up most in frontend interviews. Written by developers, for developers.
Both iterate over arrays. But they have completely different purposes. Choosing the wrong one doesn't just make your code less readable — it leads to bugs when the return value matters.
Read article →Arrow functions aren't just shorter syntax. They have fundamentally different behavior around this, arguments, constructors, and generators. Knowing when each applies makes the difference between code that works and code that subtly breaks.
Read article →JavaScript has four Promise combinator methods and each handles failure differently. Picking the wrong one means either crashing when partial failure is acceptable, or missing errors when they should abort the operation.
Read article →Both mean "no value" — but they mean it differently. undefined is the engine saying a value was never set. null is a developer saying this is intentionally empty. Knowing the difference prevents bugs and bad API design.
Read article →Triple equals is the safe default — but understanding why double equals works the way it does reveals something important about JavaScript's type system. Here's the full picture.
Read article →var, let, and const aren't just stylistic choices — they have fundamentally different scoping rules, hoisting behavior, and reassignment constraints. Here's exactly how each works and when to reach for each.
Read article →Not a list of definitions — these are the 50 questions that actually separate candidates in frontend interviews, with the kind of answer that makes interviewers write "strong hire."
Read article →Not a changelog — a curated guide to the ES6+ features that changed how JavaScript is written, with honest explanations of what each one actually does and when to reach for it.
Read article →Most JavaScript error handling is defensive theater — try/catch blocks that swallow errors and log nothing useful. Here's how to build a system that actually tells you what went wrong and where.
Read article →Most performance advice is about symptoms. This guide targets causes — how V8 compiles your code, why layout thrashing is expensive, and which optimizations move the needle vs which are cargo cult.
Read article →Scope isn't just "where variables are accessible" — it's the system that determines variable lookup at every single line of your code. Getting this right fixes bugs you've been working around for years.
Read article →Hoisting isn't the engine moving your code around — it's the engine processing declarations before execution. Understanding the difference explains every hoisting surprise you've ever encountered.
Read article →Classes didn't change JavaScript's object model — they just gave it a cleaner face. Understanding prototypes means understanding what actually runs when you call any method in JavaScript.
Read article →`this` isn't random — it follows exactly five rules in a fixed priority order. Once you know them, every `this` question becomes a lookup, not a guess.
Read article →The event loop isn't just an interview topic — it's the reason asynchronous JavaScript works at all. Once you understand how the call stack, microtask queue, and macrotask queue interact, every async execution order question becomes predictable.
Read article →Closures aren't a quirky JavaScript feature — they're the mechanism that makes most of the language work. Here's the model that makes them click, plus every closure question you'll face in an interview.
Read article →Most developers use Promises and async/await daily but can't explain why a setTimeout with 0ms delay still runs after a resolved Promise. This is the guide that fixes that gap — from the execution model up.
Read article →These aren't trick questions — they're diagnostic tools. Each one exposes a specific gap in how JavaScript actually executes. Work through these before your next interview.
Read article →Every article in this blog has an interactive practice section in JSPrep Pro.
Start Practicing Free →