Use knockouts for hard requirements only.

A knockout question is a yes/no or multiple-choice question where one answer means the candidate can’t do the job as offered. They can’t work the shifts, don’t hold a license the role requires, or can’t start before the project begins. Good knockouts save everyone time, the candidate included. Bad ones quietly filter out capable people for reasons that have nothing to do with the work. This guide covers how to tell the two apart, what good knockouts look like, the cautions worth knowing, and how to apply them fairly.

What makes a question a knockout

A real knockout has four properties:

• It’s a genuine requirement. The job can’t be done without it, not merely done more comfortably.
• It’s factual. The candidate can answer it without judging themselves. “Can you work Saturdays?” is factual. “Are you a strong communicator?” isn’t.
• It applies to everyone. You’d turn away any candidate who can’t meet it, including the strongest one you’ve seen.
• It’s specific. “Can you work at least two Saturdays a month?” is clearer than “Are you flexible about weekends?”

The quickest test: if an excellent candidate answered “no”, would you still end the process? If you’d make an exception, it’s a preference, not a knockout. Preferences belong in the interview and the scorecard, where they can be weighed against everything else.

Good knockout questions

These are examples of requirements that are often genuine. Whether each one is a real knockout depends on your role.

• “This role needs at least two weekend shifts a month. Can you work them?” (Yes / No)
• “Which of these shifts can you work?” (Multiple choice. A knockout only if the candidate can’t work any of the shifts you need.)
• “This role is on site in [city] five days a week. Can you work from there?” (Yes / No)
• “This role involves driving a [vehicle type]. Do you hold a valid license for it?” (Yes / No)
• “[Certificate] is required by law for this role. Do you hold one, or can you get one before your start date?” (Yes / No)
• “Our training cohort starts on [date]. Can you start by then?” (Yes / No)
• “The pay for this role is [range]. Does that work for you?” (Yes / No)
• “Are you legally authorized to work in [country]?” (Yes / No)

Notice how many of these explain the requirement inside the question. That helps candidates answer accurately, and it shows them the question isn’t arbitrary.

Questions that shouldn’t be knockouts

• Degrees, when the job needs skills. A degree requirement for a role that doesn’t need one shuts out people who learned the work another way.
• Minimum years of experience. “At least five years” screens out fast learners and people returning from a break. Use the interview to test the skill.
• Specific tools that can be learned quickly. Someone who knows one ticketing or accounting tool will usually pick up another.
• Employment gaps. A gap tells you nothing about ability, and asking about it as a filter often touches on health, caregiving or family.
• Anything about protected characteristics. Never ask about age, marital status, pregnancy or family plans, religion, health or disability, race, national origin or similar. These aren’t knockouts. They shouldn’t be questions at all.

Legal cautions

This isn’t legal advice, and the rules differ by country and state. A few general points hold widely:

• Tie every knockout to the job. Write down why each one is a requirement. If you can’t explain it in a sentence, reconsider it.
• Ask about authorization, not nationality. “Are you authorized to work in [country]?” is a different question from where someone was born or which passport they hold.
• Watch the effect, not only the intent. A requirement that looks neutral can screen out one group far more than others. This is called adverse impact, and it’s worth checking your knockouts for it.
• Offer adjustments where they’re reasonable. Where a requirement relates to physical tasks or schedules, describe the task and be open to reasonable adjustments.
• Check local rules on pay questions. Some places restrict asking about salary history. Asking whether a stated pay range works is a different question, but check what applies to you.

For more, see the AI hiring laws guide, and ask your own counsel before relying on any of this.

How to apply knockouts fairly

Put requirements in the job post first. If the job needs weekend shifts, say so in the post. Most people who can’t meet it won’t apply, which is kinder than asking them to fill in a form first.

Ask knockouts before the interview. Nobody should spend twenty minutes on an interview only to be ruled out by a fact you could have asked up front.

Keep the list short. One to three knockouts is plenty for most roles. A long list usually means preferences have crept in.

Leave room for edge cases. Add a short-text question like “Anything we should know about your availability?” A candidate who can’t work weekends this month but can from next month is worth knowing about.

Apply them the same way to everyone. Decide in advance what counts as a “no”, and don’t bend it for candidates you like.

Review the outcomes. Every few weeks, look at who your knockouts removed. If they’re removing people you’d want, change them.

Tell people clearly. If you won’t be moving forward, say so kindly and promptly. The rejection after screening email template is a starting point.

Knockouts in LessRounds

In LessRounds, screening form questions (yes/no, multiple choice and short text) are shown on each candidate’s page, but they aren’t scored and never reject anyone automatically. Only the AI interview is scored. That’s deliberate: a person applies the knockout.

In practice, that means reading the form answers first when you open a candidate. If someone can’t meet a hard requirement, move them to Rejected yourself. Nobody is emailed about the outcome, so you decide what to tell them, and anyone can be moved back if you misread an answer. This takes a few seconds per candidate, and it means the candidate who wrote “weekends from March” in the notes field gets read by a person instead of filtered out by a rule.