Describe the concept of 'scope' in JavaScript.

Q: Describe the concept of 'scope' in JavaScript.

**Target Audience:** Engineers preparing for JavaScript fundamentals interview questions. **Difficulty:** Easy > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . Every result below was actually run on Node.js v24.19.0 — the printed output is real, captured output, not illustrative sample text. ## 1. Why This Even Matters — A Story First Picture a program as rooms inside rooms: a house (global scope) contains a kitchen (a function), and the kitchen contains a pantry (a block, like the body of an if). Standing in the pantry, a name can be looked up in the pantry itself, then the kitchen, then the house — inner rooms can always see outward. But standing in the kitchen, nothing inside the pantry is visible unless it was explicitly handed out. Scope is exactly this: which room a name was declared in decides who can find it, and the search only ever travels outward. ## 2. The Core Idea 📌 **Interview term:** **Sc

The problem

Question presented to candidate: "Explain what scope means in JavaScript, and walk me through the practical difference between how var, let, and const each decide where a variable lives."

What a strong answer should cover:

Scope is the region of code where a given variable name can be looked up; a name lookup walks outward through enclosing scopes (the scope chain) but never inward.
var is function-scoped (or global-scoped at the top level) — it ignores block boundaries like if and for, so a var declared inside a block is still visible after that block ends.
let and const are block-scoped — confined to the nearest enclosing curly-brace block.
let and const are hoisted but sit in the temporal dead zone until their declaration line executes, so reading them earlier throws a ReferenceError; var is accessible (as undefined) before its own declaration line runs.
The classic var-in-a-loop-closure bug: closures built inside a var-based for loop all share one variable and see its final value; a let-based loop gives each closure its own per-iteration binding.

Clarifying questions expected:

"Should I also cover the temporal dead zone, or just the block-versus-function distinction?"
"Is this specifically about lexical scope, or should I also touch on this-binding, which is a separate mechanism?"

Code / implementation expected: Yes — a short, runnable snippet demonstrating var leaking out of a block, the TDZ throwing on early access, and the classic var-vs-let loop-closure difference.

scope
variables
functions
global

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Engineers preparing for JavaScript fundamentals interview questions. Difficulty: Easy

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. Every result below was actually run on Node.js v24.19.0 — the printed output is real, captured output, not illustrative sample text.

1. Why This Even Matters — A Story First

Picture a program as rooms inside rooms: a house (global scope) contains a kitchen (a function), and the kitchen contains a pantry (a block, like the body of an if). Standing in the pantry, a name can be looked up in the pantry itself, then the kitchen, then the house — inner rooms can always see outward. But standing in the kitchen, nothing inside the pantry is visible unless it was explicitly handed out. Scope is exactly this: which room a name was declared in decides who can find it, and

The solution is hidden so you can try first

8 min read · 9 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.

JavaScriptScope in practice: var leaking past a block, the TDZ, and the var-vs-let loop-closure bug (run directly)