The event loop, streams, and building backends that scale.
This is a spoken, conceptual discussion, not a live-coding exercise. You explain your reasoning out loud — concepts, tradeoffs, and "what would happen and why" — while the interviewer follows up and pushes on anything vague or surface-level.
Can you explain how Node's event loop differs from the browser's, especially around things like process.nextTick and setImmediate?
Can you explain what a Node stream is, and why you'd use one instead of reading a whole file into memory?
Can you explain what middleware is in a framework like Express, and how the request/response cycle flows through it?
How do you handle errors in asynchronous code in Node — what's different about handling a rejected promise versus a synchronous throw?
How do you decide on a versioning strategy for a REST API?
Can you explain the difference between CommonJS and ES modules in a Node context, and why that transition has been messy?
Can you explain why Node is single-threaded, and how you'd take advantage of multiple CPU cores anyway?
Can you explain the difference between authentication and authorization, and give an example of getting one right but the other wrong?
These are a few examples — each real session pulls 5 questions at random from a larger pool across every category above, so repeat sessions won't repeat the same set.
5 free interviews every month, any track, no card required.