Explain the event loop including the call stack and callback queue.
PICTURE THIS: JAVASCRIPT EVENT LOOP
Simple meaning
Synchronous code runs on the call stack until it is empty.
WHY — JavaScript instead of guessing?
Why interviewers care about JavaScript:
who only read docs from people who shipped.
and tied to Frontend work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Synchronous code runs on
the call stack until it is empty.
- 2Browser APIs like setTimeout
put callbacks in the macrotask queue, and Promise then goes to the microtask queue.
- 3After each stack drain,
microtasks run first, which is why Promise then beats setTimeout zero.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Synchronous code runs on the call stack until it is empty. Browser APIs like setTimeout put callbacks in the macrotask queue, and Promise then goes to the microtask queue.