Why run a JavaScript test before the interview?
A CV tells you which frameworks someone has used. It does not tell you whether they understand the language underneath. A ten-minute JavaScript screen shows that quickly and the same way for every applicant, so your engineers only spend interview time on people who already know the basics.
What this template covers
- Types and equality:
typeofquirks, primitives and strict comparison. - Scope and declarations: when to use
const,letorvar. - Arrays:
map,findandreduce, including the edge cases. - The event loop: microtasks, timers and the order things actually run in.
How to run it well
Keep the screen short. Eight to twelve questions with a 10–15 minute limit is enough to filter without putting good people off. Turn on question and option shuffling so candidates who apply together can't share an answer sheet. A pass mark around 60–70% works for mid-level roles. Raise it for senior hires and add a few harder event-loop questions.
Mix question types. Single-choice questions are quick to answer. A short-answer question such as naming an array method shows whether someone recalls the answer or only recognises it. Then look at the per-question stats: if almost nobody gets a question right, it is probably worded badly, not too hard.
Who this test is for
Use it for junior to mid-level front-end, full-stack and Node.js roles, for graduate and bootcamp intakes, and for agencies that place developers with clients. It also works as a quick self-check for your own team before a training budget is spent, because the results show exactly which parts of the language people are unsure about.
Make it yours
Your copy of the pack lives in your own question bank, so you can edit every question, add your stack (TypeScript, React or Node APIs) or ask the AI generator for ten more questions on a topic like closures or promises. Answers are checked on the server and never sent to the browser, so the key can't be found with developer tools. That matters when your candidates are developers.