Pre-Screening Questions: Examples, Questionnaire + Scoring

Short answer: Good pre-screening questions are short, job-related, and answerable in one line. Ask five to seven per role, split into two or three hard eligibility questions (work authorization, required license, availability) and three or four qualifying questions about the specific work. Ask every applicant the identical set, score the answers against criteria you wrote before the posting went live, and never auto-reject on a single answer.

Last updated July 2026.

What are pre-screening questions?

Pre-screening questions are the short set of questions an applicant answers before anyone on the hiring team talks to them. They sit on the application form or in a follow-up questionnaire, and their job is narrow: separate the people who can actually do the role as posted from the people who applied because the title looked close enough.

They are not interview questions. An interview question invites a story and gets judged on the quality of the answer. A pre-screening question has a right answer, or a small range of acceptable answers, and gets judged in about two seconds. If you find yourself wanting to read a paragraph to decide, you have written an interview question and put it in the wrong place.

How many pre-screening questions should you ask?

Five to seven. Below three and you are not filtering anything meaningful. Above eight and application abandonment starts eating your funnel, which is a real cost that nobody measures because the people who quit halfway never show up in your ATS.

The split that works:

Question type	How many	What it does	What it looks like
Eligibility (knockout)	2 to 3	Confirms hard, non-negotiable requirements	"Are you legally authorized to work in the US without sponsorship?"
Qualifying	3 to 4	Measures depth in the specific work	"How many years have you processed medical claims for a licensed carrier?"
Logistics	0 to 1	Catches practical non-starters early	"This role is on-site in Dallas five days a week. Does that work for you?"

Notice what is missing. No culture questions, no "why do you want to work here", no salary expectation buried at question nine. Those belong to a conversation, and asking them at the pre-screen stage mostly generates text nobody reads.

Pre-screening questions by category

Eligibility questions

These are the ones with a genuine pass or fail answer. Keep them to the requirements that would actually stop someone from doing the job on day one.

• Are you legally authorized to work in the United States without employer sponsorship, now or in the future?
• Do you hold a current [license or certification] valid in [state]?
• Are you able to work the posted schedule of [specific shift]?
• Does the role's requirement for [travel percentage / on-site days / physical requirement] work for you?

The work authorization question is legal to ask in the US, and asking it is standard practice. The risk is not in the question, it is in asking it inconsistently or asking for documentation before an offer. Federal law prohibits treating applicants differently based on citizenship or national origin, so the same wording goes to everyone applying to that req. Run your exact phrasing past counsel once and then reuse it.

Qualifying questions

These are where most teams get lazy and write "How many years of experience do you have?" Years of what, doing which part of the job, at what scale? Specific questions produce answers you can rank; vague ones produce a column of numbers that all look the same.

• How many years have you [done the specific core task], and in what setting?
• Which of the following have you personally used in a production environment: [list four to six]?
• What is the largest [volume metric relevant to the role] you have handled directly?
• Describe in one sentence the last [core deliverable] you shipped.

The scale question is the underrated one. Someone who has managed a two-person team and someone who has managed forty both answer "yes, I have managed people," and the difference matters enormously for the role you are filling.

Questions to leave out

Anything protected or proxying for something protected: age, graduation year, family status, disability, arrest record where prohibited, and in a growing number of states, salary history. Also drop the preference questions. "Are you comfortable in a fast-paced environment?" has a 100 percent yes rate and tells you nothing except that the applicant can read.

How to score pre-screening answers

Write the scoring rule before the posting goes live, not after the answers come in. Once you have seen the pool, your criteria bend to fit the people who applied, and at that point the whole exercise is just a formalized gut call.

A workable structure: eligibility questions gate, qualifying questions score. Give each qualifying question a weight based on how much it predicts performance in the role, define what a low, middle, and high answer looks like in concrete terms, and total them. The detailed version of this is in our guide to building a candidate scoring model, and the mechanics of turning scores into a shortlist are covered in how to shortlist candidates.

The reason to write it down is boring and important: consistency is what makes a screening process defensible. Disparate impact liability under Title VII applies to screening criteria regardless of whether a human or a tool applied them. A documented, job-related question set applied identically to every applicant is the thing that holds up. "We knew it when we saw it" does not.

Should pre-screening questions auto-reject candidates?

No, and this is where a lot of hiring software makes a choice you might not want. Many applicant tracking systems let you flag an answer as disqualifying and remove that applicant from the pool automatically, with no human ever seeing the file.

The failure mode is quiet and expensive. A question with an ambiguous wording, a required certification that renews in three weeks, a candidate who misreads a dropdown: each one silently deletes someone qualified, and because they are gone, you never learn it happened. At volume, a single badly written knockout can remove a double-digit percentage of a pool.

The better pattern is to flag and rank. An applicant who misses a hard requirement drops down the list with the reason attached, a recruiter sees it, and the recruiter decides in about three seconds. That costs almost nothing and keeps a human on every outcome. It is how applicant eligibility screening software should behave, and it is worth asking any vendor directly which of the two models their product uses.

Pre-screening at volume

Question sets work beautifully for the first forty applications. The trouble is the same trouble every manual screening step has: consistency decays with volume and fatigue. Somebody reviewing answers on Monday morning with a full hour applies a different standard than the same person on Thursday between two intake calls, and the answers themselves still need to be read against the resume to mean anything.

That is the case for automating the pass. Candidate prescreening software asks your question set, checks each answer against the criteria you defined, reads the resume alongside it, and ranks the pile with a written reason under each name. The standard applied to applicant 400 is identical to the one applied to applicant 4. A recruiter opens an ordered list instead of a folder, and still makes every call.

This pattern is not unique to hiring. Any business where a flood of inbound requests has to be qualified before a human spends real time on it ends up in the same place, which is why service firms now let software run the initial discovery consultation and qualify the prospect before anyone books a calendar slot. Same logic, different funnel: ask the short set of decisive questions early, and spend human attention on what survives.

What is a pre-screen questionnaire?

A pre-screen questionnaire is the short, identical set of questions every applicant answers as part of the application, before any human reads their resume. It is not an interview and not an assessment. Its only job is to collect the two or three facts that decide eligibility and the three or four that separate a plausible candidate from an unlikely one, in a form you can score consistently.

The format matters more than people expect. Yes or no and single-select answers can be scored the same way every time and are what make automated ranking possible. Free-text answers give you nuance, but every one you add is another thing a human has to read, so keep them to one, at most two, per role. Never make an open-text box mandatory for an eligibility question, because you have then turned a clean gate into a judgment call.

Here is a workable structure you can copy for a generic mid-level role and adapt per requisition.

#	Question	Format	Purpose
1	Are you legally authorized to work in the United States for this employer?	Yes / No	Eligibility gate
2	Will you now or in the future require sponsorship for employment visa status?	Yes / No	Eligibility gate
3	This role is onsite in [city] five days a week. Can you work that schedule?	Yes / No	Eligibility gate
4	How many years have you [done the specific task the job is mostly about]?	Single select bands	Qualifying, scored
5	Which of these have you personally used in the last two years?	Multi select	Qualifying, scored
6	What is your earliest available start date?	Date	Planning, rarely a gate
7	Describe the most recent project where you [core task]. Two or three sentences.	Free text	Qualifying, read for the shortlist only

Write the questions once per role family and reuse them. Rewriting the set for every requisition is how two openings for the same job end up with different bars, and it is the fastest way to lose the consistency that made the questionnaire worth building.

Pre-screening interview questions for a 15-minute phone screen

The pre-screen interview is a different instrument from the questionnaire and should never repeat it. By the time you are on a call you already have their answers. The call exists to test whether the strongest claim on the application holds up, to give the candidate real information about the job, and to surface the two things that kill offers late: compensation and timing.

Fifteen minutes, five questions, decision at the end. That is enough for a competent recruiter to sort a maybe into a yes or a no.

• Walk me through the [specific project] you mentioned. What was your part of it? The single most useful question in the whole call. Real ownership survives a follow-up question. Borrowed credit usually does not.
• What are you looking for in your next role, and what is missing in your current one? Tells you whether the job you have actually solves their problem. A mismatch here predicts a declined offer better than anything on the resume.
• The range for this role is [x] to [y]. Does that work for you? Ask it out loud, in the first call, with a real number. Many states require the range on the posting anyway, and discovering a gap in week five wastes everyone's time.
• What does your timeline look like, and are you in process anywhere else? Not to pressure anyone. You need it to sequence interviews and to know whether you have two weeks or two days.
• What questions do you have about the role? The quality of the questions is genuinely diagnostic, and skipping this is how you lose good candidates who had a fixable concern.

Ask the same five in the same order for every candidate on the requisition, and write your notes against each one before you take the next call. Structured phone screens are more predictive than unstructured ones for the same reason structured interviews are: you are comparing answers to the same question rather than comparing impressions.

Frequently asked questions

What is the difference between pre-screening and screening?

Pre-screening is the first filter on the raw applicant pool, before any contact from the hiring team. Screening is everything after: the phone screen, structured interviews, and assessments. Pre-screening decides who is worth a conversation, screening decides who is worth an offer.

What are good pre-screening questions for a phone screen?

A phone screen should not repeat the application questions. Use the call to confirm the two or three answers that carry the most weight, ask one open question about the most recent relevant project, and cover compensation range and start date. Fifteen minutes, four questions, decision at the end.

Can pre-screening questions be discriminatory?

They can, which is why the wording matters. Questions that touch protected characteristics directly, or that act as a proxy for one, create exposure even when nobody intended it. Requirements that are not genuinely required are the most common problem, since they narrow the pool for reasons unrelated to job performance. Keep every question tied to a documented job requirement.

How long should applicants take to answer?

Under two minutes total. Application completion rates fall off sharply past that, and the applicants most likely to abandon a long form are often the ones with options, which is exactly the group you wanted.

What are good screening questions?

A good screening question is job-related, answerable in one line, and produces an answer you can score the same way for every applicant. It maps to a requirement you wrote down before the posting went live. If two reviewers could read the same answer and reach opposite conclusions, the question is too vague to keep.

What is the difference between a pre-screen questionnaire and the application form?

The application form collects identity, contact details, work history and the resume. The pre-screen questionnaire collects decisions: the small set of answers that determine eligibility and rank. They usually appear in the same submission flow, which is why people conflate them, but only the questionnaire is designed to be scored.

Should you ask for salary expectations in pre-screening?

Post your range instead and ask whether it works. Several states and cities now require pay ranges in job postings, and asking candidates to name a number first is banned in a number of jurisdictions. A yes or no against your published range gets you the same information, filters the genuine mismatches, and stays clean everywhere.

How many pre-screening questions is too many?

Past about eight, completion rates drop and the extra answers rarely change the decision. If you find yourself wanting twelve, the usual cause is that the questions are doing interview work. Move anything that needs a conversation into the phone screen and keep the questionnaire to the decisive few.

Can you use AI to score pre-screening answers?

Yes, and it is the main reason question sets scale past a few hundred applicants. The requirements are the same as for any automated screening: disclose to candidates that AI is used, keep a bias audit you can produce, show the criteria behind each score in plain language, and make sure nothing rejects an applicant without a human reviewing it.