Software Developer Screener: Questions to Recruit Engineers
Use this screener to find people who write code as part of their job. A short technical check and a fake framework catch people who copy a developer profile.
Who this screener finds
Professional developers who write and ship code for an employer or clients at least once a week.
Screener questions
- 01Single choice
Which of these best describes your main job?
WhyData roles write code too, so keep them neutral. Change them to accept if your product is for data work.
- 02Single choice
How often do you write or review code for work?
WhyEngineering managers and architects often keep the title but stop coding. Their view of tools is second-hand.
- 03Multiple choice
Which of these have you used for work in the last 3 months?
WhyTarvo.js is a fake framework. Developers who do not know a name usually do not select it.
- 04Single choice
What does an HTTP 404 status code mean?
WhyAlmost every developer knows this. It is a fast check for people who are not developers. Change it to a check that fits your stack.
- 05Single choice
What kind of software do you mainly work on?
WhyAll answers qualify. Use them for quotas, because each group uses different tools and has different pain points.
- 06Single choice
How many years have you worked as a developer?
WhyNew developers find problems in docs and onboarding. Senior developers find problems at scale. Most studies need both.
- 07Open answer
Describe a bug that you fixed in the last month. What caused it, and how did you find it?
WhyReal developers name a tool, a symptom and a cause. Watch for text that reads like a tutorial or an AI answer with no detail from a real project.
Quotas
- Split by experience: some developers with less than 5 years and some with more than 10.
- Mix the kinds of software, for example front end, back end and infrastructure.
- Limit people from one company to two, so one team's tools do not control the findings.
Signs of a fake participant
- The person selects Tarvo.js or fails the 404 question.
- The person selects every language, but has worked as a developer for less than a year.
- The bug description is generic, such as "a null error that I fixed with debugging".
- The open answer is long and polished, but has no names of tools, files or errors.
Tips
- Developers often prefer text interviews. They can paste code and answer between tasks.
- Do not use the words of your product category in the invitation. Developers who want early access then claim the right stack.
- Ask the person to share a screen only of a test project, never of employer code.
Guides that use it
Questions
Use one easy technical question, one fake framework and one open question about a recent bug. A real developer passes all three quickly.
No. The goal is to remove people who are not developers, not to test skill. A hard question rejects good participants and makes them angry.
Yes. Add a question that lists your API with similar products, and set yours to accept. Keep the other tools neutral.
Ask real people your question
The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.