The answer
Deeply nested callbacks that are hard to read and maintain. Each async operation depends on the previous one, leading to a pyramid shape. Fix with promises (chain .then calls) or async/await (flatten to synchronous-looking code).
Callback Interview Questions in JavaScript
What is callback hell in JavaScript?
More FAQs in Callback Interview Questions in JavaScript
When you pass a callback to a function, you give up control of when and how it is called. The function might call it multiple times, not at all, or with unexpected arguments. Promises solve this by guaranteeing the callback is called once.
The Node.js convention: the first argument is an error. Always check if (err) first and handle it. In promises, use .catch instead. Never ignore the error argument in a callback.
No. map, filter, and reduce call their callbacks synchronously. setTimeout, event listeners, and fetch call their callbacks asynchronously. The timing depends on the calling function, not the callback itself.
Still have questions?
Browse all our FAQs or reach out to our support team
Want to upskill yourself?
Your learning library
Small steps. Big possibilities.
Find your next course. Build something great.