roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Explain how JavaScript really behaves in a front-end or full-stack language round. Covers types and coercion, closures and prototypes, the event loop and promises, modules, the DOM and fetch, and memory.
621 of 621 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 621 new. 0 cut, outside your plan.
Front-end hiring is where JavaScript is examined for its own sake; elsewhere it is mostly the language a problem happens to be written in. Front-end and full-stack loops usually spend the technical conversation after the screen on it, and often the live coding round too; Node backend loops raise it inside a wider talk about the runtime. The conversation runs on short snippets and what the console shows for each: a `var` loop that schedules three timeouts and logs one number three times, a zero-delay timeout that runs after a promise callback queued later, a `fetch` that gets a 404 and lands in the success branch. Live coding asks you to rebuild what the language normally hands you: `Promise.all`, a debounce, a deep clone, an event emitter. Seniority shows in where the follow-ups stop. Knowing that `==` converts before it compares is where they begin; predicting which conversion runs, explaining why an imported `let` throws inside a circular import, or finding in a heap snapshot the detached subtree a forgotten listener keeps alive is what a senior loop listens for.
[Types and coercion](/topics/lang-javascript-types-coercion) lead because nearly every later answer depends on saying what a value is and what it becomes under `==`, `+` or an `if`. [Errors and the built-ins](/topics/lang-javascript-errors-builtins) sit beside them: the everyday vocabulary of snippets, and the error model rejected promises reuse later. Functions & Scope turns from values to names: which binding an identifier resolves to, what [a closure keeps alive](/topics/lang-javascript-scope-closures), how `this` is fixed at the call. Its [iterators and generators](/topics/lang-javascript-functions-collections-iteration) look like a side road, but async iteration later reuses their protocol. [Prototypes](/topics/lang-javascript-prototypes) wait until functions and `this` are in place, because a constructor is an ordinary function, `new` binds `this` and links the chain, and `class` adds less on top than its syntax suggests. Asynchrony puts the [event loop](/topics/lang-javascript-event-loop) ahead of [promises and async/await](/topics/lang-javascript-promises-async), so ordering puzzles get answered from the queues rather than from memory. [Modules](/topics/lang-javascript-modules) need that grounding: `import()` returns a promise, and top-level await holds back every module that imports the one awaiting. In the Browser starts with the language's short pass over the DOM and over how browser globals differ from Node's, then widens into the platform's [event model](/topics/fe-browser-platform-dom-events), from capture and bubbling to listener teardown, and into networking with [fetch](/topics/fe-browser-platform-network-fetch-api), cancellation and the XMLHttpRequest older code still carries. Memory comes last because a leak is assembled from pieces met earlier: a closure, a listener nobody removed, a timer, a detached node held in a map. The stretch runs from [reachability](/topics/found-memory-management-gc-reachability) and the collectors built on it through [weak references](/topics/found-memory-management-gc-weak-references) to [leaks in single-page apps](/topics/fe-performance-runtime-memory-leaks) and the [profiling workflow](/topics/fe-performance-measurement-profiling-workflow) that finds one.
Snippet questions are where a short runway pays back. With a front-end loop a week or two away, importance trimmed to must know is the one change the controls need, as study order already opens on by frequency; put the saved hours into writing each output down before reading the answer, because being wrong on paper is cheaper than being wrong aloud. A Node posting moves the weight off the browser stretch and onto modules, where interop and circular imports get asked more than event delegation. Given two or three months, move study order over to by topics; then write `Promise.all`, a debounce and an event emitter by hand as the modules reach them, since a version you have debugged survives follow-ups. Seniors can lift the bottom of level past junior, but not skip memory: senior loops use it to learn whether you have chased a real leak. The plan teaches the language without static types or a framework. If the posting says TypeScript, generics, narrowing and the rest of its type system are on the [TypeScript roadmap](/roadmaps/typescript); Node appears here through its globals and its CommonJS modules; its streams, worker threads and servers belong to the [Node.js roadmap](/roadmaps/nodejs).
Front-end hiring is where JavaScript is examined for its own sake; elsewhere it is mostly the language a problem happens to be written in. Front-end and full-stack loops usually spend the technical conversation after the screen on it, and often the live coding round too; Node backend loops raise it inside a wider talk about the runtime. The conversation runs on short snippets and what the console shows for each: a var loop that schedules three timeouts and logs one number three times, a zero-delay timeout that runs after a promise callback queued later, a fetch that gets a 404 and lands in the success branch.
Live coding asks you to rebuild what the language normally hands you: Promise.all, a debounce, a deep clone, an event emitter. Seniority shows in where the follow-ups stop. Knowing that == converts before it compares is where they begin; predicting which conversion runs, explaining why an imported let throws inside a circular import, or finding in a heap snapshot the detached subtree a forgotten listener keeps alive is what a senior loop listens for.
Types and coercion lead because nearly every later answer depends on saying what a value is and what it becomes under ==, + or an if. Errors and the built-ins sit beside them: the everyday vocabulary of snippets, and the error model rejected promises reuse later.
Functions & Scope turns from values to names: which binding an identifier resolves to, what a closure keeps alive, how this is fixed at the call. Its iterators and generators look like a side road, but async iteration later reuses their protocol. Prototypes wait until functions and this are in place, because a constructor is an ordinary function, new binds this and links the chain, and class adds less on top than its syntax suggests.
Asynchrony puts the event loop ahead of promises and async/await, so ordering puzzles get answered from the queues rather than from memory. Modules need that grounding: import() returns a promise, and top-level await holds back every module that imports the one awaiting.
In the Browser starts with the language's short pass over the DOM and over how browser globals differ from Node's, then widens into the platform's event model, from capture and bubbling to listener teardown, and into networking with fetch, cancellation and the XMLHttpRequest older code still carries. Memory comes last because a leak is assembled from pieces met earlier: a closure, a listener nobody removed, a timer, a detached node held in a map. The stretch runs from reachability and the collectors built on it through weak references to leaks in single-page apps and the profiling workflow that finds one.
Snippet questions are where a short runway pays back. With a front-end loop a week or two away, importance trimmed to must know is the one change the controls need, as study order already opens on by frequency; put the saved hours into writing each output down before reading the answer, because being wrong on paper is cheaper than being wrong aloud. A Node posting moves the weight off the browser stretch and onto modules, where interop and circular imports get asked more than event delegation.
Given two or three months, move study order over to by topics; then write Promise.all, a debounce and an event emitter by hand as the modules reach them, since a version you have debugged survives follow-ups. Seniors can lift the bottom of level past junior, but not skip memory: senior loops use it to learn whether you have chased a real leak.
The plan teaches the language without static types or a framework. If the posting says TypeScript, generics, narrowing and the rest of its type system are on the TypeScript roadmap; Node appears here through its globals and its CommonJS modules; its streams, worker threads and servers belong to the Node.js roadmap.