Technical screening questions
Ask for one example per question and listen for specifics.
- How does the event loop work? A good answer: Phases, non-blocking I/O and how blocking code hurts.
- How do you handle errors in async code? A good answer: Try and catch with await, rejections and central handlers.
- How do you structure a Node API? A good answer: Layers, validation, services and testing.
- How do you scale a Node service? A good answer: Clustering, stateless design and caching.
- How do you manage dependencies and security? A good answer: Lock files, audits and updates.
Quick screening questions
Use these when you have only a few minutes.
- How do you handle blocking work in a Node service?
- Express or NestJS, and why?
- Describe how you structure error handling in an API.
What separates the levels
Match the level to the requirement before you submit.
- Junior: builds endpoints.
- Mid: owns services and tests.
- Senior: designs systems and performance.
Red flags
Any of these is a reason to probe further.
- Callback-only experience.
- Cannot explain the event loop.
- No tests.
Tools you should hear mentioned
A Node.js developer with real experience usually names several of these without prompting.
- Node.js
- Express or NestJS
- TypeScript
- MongoDB or PostgreSQL
- Jest
- Docker
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a Node.js developer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.