Technical screening questions
Ask for one example per question and listen for specifics.
- How do you make a page accessible? A good answer: Semantic HTML, labels, keyboard use and contrast checks.
- How do you improve load time? A good answer: Fewer and smaller assets, lazy loading, caching and measuring first.
- What is the difference between flexbox and grid? A good answer: One-dimensional versus two-dimensional layout, with a use for each.
- How do you handle state in a large page? A good answer: Local state versus shared state and when a store is worth it.
- How do you debug a layout bug in one browser? A good answer: Developer tools, isolate the rule and check browser support.
Quick screening questions
Use these when you have only a few minutes.
- Show me a site you built and what you owned.
- How do you make a page load faster?
- How do you test a layout on mobile?
What separates the levels
Match the level to the requirement before you submit.
- Junior: builds pages from designs.
- Mid: builds applications and owns quality.
- Senior: sets front-end standards.
Red flags
Any of these is a reason to probe further.
- No live work to show.
- Cannot explain the box model.
- Ignores accessibility.
Tools you should hear mentioned
A Web developer with real experience usually names several of these without prompting.
- HTML and CSS
- JavaScript or TypeScript
- React, Angular or Vue
- Browser developer tools
- npm and a bundler
- Git
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 Web 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.