Knockout Questions: Examples, and Why They Should Flag, Not Reject
What knockout questions are, 25 examples by type, how to word them so a good candidate isn't lost on a technicality, and why a flag beats an auto-reject.
A knockout question asks about a hard requirement of the job, such as a license, a shift pattern or a pay range, so that nobody spends time on a match that can't work. Used well, it flags an answer for a recruiter to look at. Used badly, it quietly rejects people who could have done the job.
This guide covers what knockout questions are, 25 examples grouped by type, how to word them, and why a knockout should raise a flag for a person rather than reject anyone automatically.
What is a knockout question?
A knockout question is a screening question with a deal-breaker answer. "Can you work 12-hour night shifts, three nights a week?" is a knockout question for a night-shift role: if the honest answer is no, the job doesn't fit, however strong the candidate is otherwise.
Most knockouts are yes-or-no questions about one of a handful of things: a license or certification, a schedule, a location, a start date, experience with a specific tool, travel, or pay. They show up in two places:
- On the application form. A short list of questions every applicant answers before submitting. This is what most people mean by knockout questions for applications.
- In the first-round screen. The recruiter, or an AI interviewer, asks them early so the rest of the conversation isn't wasted.
A knockout question is not the same thing as a screening question. "Why are you interested in this role?" is a screening question: no answer to it ends the conversation. A knockout question has one answer that means the job can't work, which is exactly why it deserves more care than it usually gets.
Why do recruiters use knockout questions?
Volume, mostly. Employ's first Hiring Benchmarks report, a vendor report covered by HR Dive in January 2026, found an average of 257.6 applications per job in 2025, up from 207.2 in 2024. No recruiter can hold a conversation with that many people per role, and a share of them can't work the shift, the location or the pay. Knockouts find those mismatches before anyone books time. If that's the scale you're working at, the high-volume hiring playbook covers the rest of the funnel.
Knockouts also respect the candidate's time. Someone who needs a remote job would rather learn on the application that this one is on site five days a week than in a third interview.
They are a small part of a first-round screen. For the open questions that make up the rest of it, see 50 pre-screening interview questions.
25 knockout question examples, by type
Each example states the requirement inside the question, asks for a yes or a no, then asks the candidate to tell you more, so a recruiter has context when the answer isn't a clean yes. Replace the bracketed parts with your own details.
Licenses and certifications
- This role requires an active registered nurse license in [state]. Do you hold one? Tell me more: which state issued it, and when does it next renew?
- Do you hold a Class A commercial driver's license? Tell me more: how long have you held it, and what have you driven with it?
- Do you have a current Basic Life Support (BLS) certification? Tell me more: when does it expire?
- This role requires a journeyman electrician license in [state]. Do you have one? Tell me more: what work have you done under it most recently?
Schedule and shifts
- This role works 12-hour night shifts, 7 p.m. to 7 a.m., three nights a week. Can you work that schedule? Tell me more: have you worked nights before, and how did it go?
- The schedule includes every other weekend. Can you work alternate Saturdays and Sundays? Tell me more: if you can work some weekend days but not others, which can you work?
- Shifts start at 5:30 a.m. Can you be on site and ready to work by then? Tell me more: have you worked early starts like this before?
- This role is on call one week in four, responding to after-hours problems within 30 minutes. Can you take on-call weeks? Tell me more: what on-call arrangements have you worked with before?
Location and commute
- This job is on site at our [city] warehouse five days a week, with no remote days. Does that work for you? Tell me more: if five days on site won't work, what would?
- The role is hybrid, with three days a week in our [city] office. Can you commit to that? Tell me more: which days would you plan to come in?
- This role is based in [city], and we don't offer relocation support. Could you be working from [city] by your start date? Tell me more: what would your timeline be?
Start date
- We need someone to start by [date]. Could you start by then? Tell me more: if not, what's the earliest date you could start?
- If you're working now, how much notice do you need to give? Tell me more: is there any flexibility in that?
- The job begins with a paid two-week training class, [date] to [date], Monday to Friday, 8 a.m. to 4:30 p.m. Can you attend every day? Tell me more: are there any days in that window you would miss?
Minimum experience with a named tool or skill
- Have you used Salesforce as your main CRM in a sales or customer-facing job? Tell me more: what did you use it for day to day?
- This role writes SQL every day. Have you written SQL queries as part of a job? Tell me more: what's the most complex query you've written, and what was it for?
- Have you run payroll for a company with more than 50 employees, in any payroll system? Tell me more: which system, and which parts of the payroll did you own?
- Have you charted in Epic or another electronic health record in a clinical job? Tell me more: which system, and for how long?
Travel
- This role travels about 30% of the time, usually two nights a week. Can you travel that much? Tell me more: what's the most travel you've done in a past job?
- Most days involve driving between client sites across [region]. Is a job with that much driving workable for you? Tell me more: have you had a job with daily driving before?
- The role includes one week at our head office in [city] every quarter. Can you make those trips? Tell me more: have you traveled for work on a similar schedule before?
Pay range fit
- The pay for this role is $21 to $24 an hour, depending on experience. Does that range work for you? Tell me more: where in that range would you expect to be, and why?
- The base salary is $68,000 to $78,000, plus a bonus of up to 10%. Is that in line with what you're looking for? Tell me more: is there anything else about the package you'd need to know?
- About half of this role's pay is commission. Are you comfortable with pay that changes from month to month? Tell me more: what commission plans have you worked on before?
- This is a six-month contract at $55 an hour, without benefits. Does that work for you? Tell me more: is the six-month length a fit too?
Notice what isn't on the list: nothing about age, health, family, religion or nationality. A knockout asks about the job's requirements, not about the person, and none of those belongs on yours.
How do you word a knockout question?
Ask about the actual requirement
Write the requirement down first, then the question. If the requirement is "works alternate weekends", the question is "Can you work alternate Saturdays and Sundays?", not "Are you flexible?" or "Are you available weekends?". The vaguer versions leave the candidate guessing whether you mean one weekend a month or every one of them.
Put the numbers in the question: hours, days, the share of time spent traveling, the pay range, the start date. A candidate can only answer the question they understood.
Avoid proxies
A proxy asks about something that usually goes with the requirement instead of the requirement itself. Proxies screen out people who meet the requirement and wave through people who don't.
| Instead of this proxy | Ask about the requirement |
|---|---|
| Do you have a car? | Can you get to [site] for a 5:30 a.m. start every shift? |
| Do you have five years of experience? | Have you run payroll for more than 50 employees? (or whatever the five years was meant to prove) |
| Do you have a bachelor's degree? | Have you done this work in a job before? Tell me about it. |
| Are you currently employed? | Could you start by [date]? |
| Where do you live? | This job is on site in [city] five days a week. Does that work for you? |
| Are you an expert in Excel? | Have you built a pivot table from raw data at work? What was it for? |
Self-ratings deserve a special mention. "Are you an expert in Excel?" measures confidence, not skill. Ask about something the person has done.
Use yes or no, plus a short "tell me more"
The yes-or-no answer is what makes a knockout quick to review. The "tell me more" is what makes it fair: it turns a bare "no" into "no, but I could start two weeks later" or "no, my certification renews next month". Keep it to one sentence, and on an application form, make the text box optional.
One requirement per question
"Can you work nights and weekends?" is two questions. A candidate who can do nights but not Sundays doesn't know whether to answer yes or no. Split it.
Why should a knockout flag an answer instead of rejecting automatically?
Because a knockout rule is only as good as the question and the answer, and both go wrong more often than anyone plans for. A flag puts a person in front of the answer. An automatic rejection doesn't, and nobody ever finds out what it cost.
People misread questions
A candidate applying on a phone taps the wrong option. Someone reads "Are you willing to travel?" and pictures weekly flights when the job means one trip a quarter. A nurse whose license renewal is still being processed answers "no" to "Do you hold an active license?" because they're being careful. Each of them could be a qualified person who failed a rule, not the job.
Requirements have exceptions
Hiring managers bend requirements when the right person turns up. The start date moves by two weeks. The certification can be earned in the first month. The top of the pay range stretches for someone with exactly the right experience. A rule can't know which requirements are firm this month. A recruiter can ask.
Losing a good candidate costs more than reading a flag
Reviewing a flagged answer is quick. An automatic rejection of a good candidate is expensive and invisible: you paid to attract them, they're gone, and your reports show one more unqualified applicant. Nothing in the system tells you the question was badly worded.
There's a candidate side, too. A rejection that arrives seconds after someone clicks submit tells them exactly how much attention their application got.
What reviewing a flag looks like
A flagged answer should reach the recruiter with the candidate's own words, so one read is enough to decide:
- A clear mismatch with no room to bend: decline, politely and quickly.
- An unclear answer: ask one clarifying question.
- A mismatch the hiring manager might bend on: take it to them with the candidate's answer attached.
The decision is still fast. It's just made by someone who can tell a misread from a mismatch.
How does DIO handle knockout questions?
DIO, the AI interviewer Dio makes, holds a structured voice interview with each candidate in the browser, and its knockout questions follow the rule this guide argues for: flag, don't reject. A knockout answer is flagged for the recruiter's review. The flag never ends the interview and never rejects anyone: the interview carries on, and a person on your team makes the decision with the candidate's full answer in front of them.
Two other details help with misreads. Candidates can ask DIO to repeat a question they didn't catch, and DIO asks a follow-up when an answer is thin or vague, so a one-word reply doesn't have to be the end of the story. For how this compares with phone bots and one-way video, see AI screening interviews compared.
What are the most common knockout question mistakes?
Too many knockouts
Every knockout is one more way for a good candidate to fall out. Three to five is plenty for most roles. If you have twelve, most of them are preferences.
Treating "preferred" as "required"
If the job description says "Epic experience preferred", Epic can't be a knockout. Ask the hiring manager: would you hire someone excellent who doesn't have this? If the answer is yes, it's a nice-to-have, and it belongs in the interview rather than the knockouts. Sorting the two is the first step in turning a job description into interview questions.
Vague wording
"Are you flexible?", "Do you have reliable transportation?" and "Are you comfortable in a fast-paced environment?" knock almost nobody out, and when someone does answer no, you don't know what they meant. If you can't write the requirement as a number, a time or a place, it probably isn't a knockout.
Hiding the requirement
"What are your salary expectations?" makes the candidate guess at your budget. "The range is $21 to $24 an hour; does that work?" gets you a real answer, and you don't lose the person who would have taken $23 but asked for $26 to be safe.
Never revisiting the list
Requirements change. The night shift becomes a rotation, the role goes hybrid, the range moves. Review your knockouts whenever the job description changes, and look at which ones flag the most people. A knockout that flags half your applicants is either a real constraint you should state more clearly in the job posting, or a badly worded question.