Interviews rarely test obscure trivia. They test whether you understand the few mechanics that the whole language rests on.
Get comfortable explaining these out loud and most questions become variations on a theme.
The short list
- Closures: why a returned function still remembers its scope.
- The event loop: how promises and timers actually get scheduled.
this: how it is decided at call time, not at definition time.- Prototypes: what really happens on a property lookup.
Practice narrating your reasoning, not just reciting the answer. An interviewer learns far more from "here is how I would reason about it" than from a memorized definition.
Placeholder article: the full write-up with runnable examples is coming soon.