Knockout question
Also called:disqualifying question, screener question
When to use one
Knockout questions are appropriate only when the answer is genuinely binary and non-negotiable:
- “Do you have authorization to work in the EU?” (visa)
- “Do you hold a valid driving license?” (delivery driver)
- “Are you fluent in conversational German?” (front-line support role)
Anything that has nuance — years of experience, specific tools — is not a knockout. Those go in the screening call.
Why teams overuse them
The temptation is real: a knockout question removes 50% of incoming applications instantly. The cost is hidden: every false negative is a candidate who would’ve been a strong hire but couldn’t prove it through a yes/no.
Three rules of thumb:
- Maximum three knockouts per role. More than three and you’re filtering for compliance with the form, not for fit.
- No experience knockouts. “Do you have 3+ years of experience?” excludes the candidate with 2.5 great years.
- No “preferred” knockouts. Knockouts are for must-haves only.
What they look like in practice
A knockout question on an application form has three pieces: the question itself, the disqualifying answer, and a polite rejection email that fires automatically when the disqualifying answer is given. The candidate gets a clear answer within a day or two instead of weeks of silence.
Where Join fits
Join’s screening questions have three tiers, set per question: Optional, Required, Knockout. Only Knockout rejects: a failing answer auto-rejects the candidate and triggers a localized rejection email the next day, preserving candidate experience while saving reviewer time. Every decision is logged with the answer and the rule that triggered it, and a recruiter can restore a wrong rejection: the candidate isn’t hidden or deleted. See the features page.
