Callback Hell Interview Questions in JavaScript

Callback Hell Interview Questions in JavaScript

Callback hell is a common interview topic. Here are the most asked questions with answers.

Q1: What is callback hell?

Deeply nested callbacks (pyramid of doom) that are hard to read, debug, and maintain. It happens when async operations depend on each other.

Q2: How do you fix callback hell?

Use promises (.then chains) or async/await (synchronous-looking code with try/catch). If stuck with callbacks, use named functions to keep the code flat.

Q3: What is inversion of control in callbacks?

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 wrong arguments. Promises fix this.

Q4: How do you handle errors with callbacks?

The error-first convention: the callback's first argument is an error. Always check if (err) first and return early. Propagate errors to the caller.

Q5: How do you run callbacks in parallel?

Use a manual counter: track completed tasks, store results in order, call the final callback when all are done. Or use Promise.all (much cleaner).

Q6: How do you convert a callback to a promise?

function promisify(fn) {
  return (...args) => new Promise((resolve, reject) => {
    fn(...args, (err, result) => {
      if (err) reject(err);
      else resolve(result);
    });
  });
}
``
### Q7: What are the good parts of callbacks?

Simplicity, universality (work everywhere), synchronous use (map, filter, reduce), event handling (addEventListener), and closures (access outer variables).

### Q8: What are the bad parts of callbacks?

Callback hell, inversion of control, repetitive error handling, hard to run in parallel, hard to cancel, and unclear stack traces.

### Q9: Why are promises better than callbacks?

- Once-only settlement (no inversion of control).
- Flat chaining (`.then`) instead of nesting.
- One `.catch` for all errors.
- `Promise.all` for parallel operations.
- Async/await (built on promises) looks synchronous.

### Q10: What is the error-first callback convention?

The callback's first argument is an error (`null` if no error). The second argument and beyond are the result. Used in Node.js (`fs.readFile`, `http.get`).

### The Takeaway

Callback hell interview questions test: the definition (pyramid of doom), fixes (promises, async/await, named functions), inversion of control, error-first convention, parallel execution (manual counter vs `Promise.all`), promisification, good/bad parts, and why promises are better.