Screening Questions That Actually Filter Candidates

Screening Questions That Actually Filter Candidates

Mercedes Gordo runs delivery and customer success at Nova and spent two years at LinkedIn in Dublin. Her rule for screening calls: if you can't say in advance what answer would end the call, it isn't a screening question.

Updated 7 min read

Most screening calls are a conversation that happens to end in a decision. The good ones are a decision that happens to be a conversation.

The difference is whether you wrote down, before dialling, what answer would end the call. If you can’t say that in advance, you don’t have screening questions. You have questions.

Here’s the structure that fixes it.

The anatomy: an open question plus three routes

Every screening question has two parts, and the second one is the part people skip.

The question, which has to be open. A closed question invites the candidate to tell you what you want to hear. “Have you managed a team?” gets a yes from someone who once supervised an intern. “Tell me about the last team you were responsible for” gets you facts you can actually evaluate.

The three routes, decided before the call:

  • Dig in. The answer was vague or had no detail. You follow up for the specific: which project, which client, what their part in it was, what happened.
  • Pass. Concrete, and it clears the bar. Move on.
  • Drop. Concrete, and it doesn’t clear the bar.

Worked example, for a role with a band up to 45K:

Salary · KNOCKOUT “How are you thinking about the money side for your next move? What would you need?” Dig in → evasive, “whatever’s fair” → “Just so we’re both oriented, what range are you in?” Pass → at or under 45K, or flexible. Drop → above 45K with no movement. Before closing it, check whether they value the rest of the package.

That’s it. The routes are what turn a question into a filter, and writing them down is also what stops you deciding the threshold from the answer, which is how the same requirement ends up applied differently to two candidates.

Four to eight, and the padding is what hurts

Write one question per genuine non-negotiable. If the role has four, it’s four.

The usual mistake isn’t asking too few, it’s padding the list with things that matter but don’t disqualify. Nice-to-haves don’t belong on a screening list at all. They stretch the call, they don’t change the decision, and they push the real filters toward the end, when both of you are tired.

Each question also carries a weight, and two are enough:

  • KNOCKOUT. One fail is a clear no. Work authorization, the salary band, the one requirement the job can’t flex on.
  • STRONG SIGNAL. It matters and it allows nuance. Worth probing before you conclude.

The dimensions worth considering, dropping any that don’t apply: compensation, location and work authorization, availability and notice, languages at the level the job actually needs, the core experience requirement, and motivation. A fully local monolingual role doesn’t need a language question. Don’t ask it to be thorough.

Then add the part that makes the list yours: one or two questions that catch the typical failure of this specific profile. The one that separates someone who genuinely led from someone who was in the room. The one that separates mastery of a tool from having touched it. Those come from the brief, not from a template.

Never open with salary

This is where most screening lists go wrong, and the reason is a confusion between two things that look like one.

The weight orders your priority. It tells you what to triage on and what to write at the top of your sheet.

The arc orders the conversation. And in the conversation, the most disqualifying question is usually the wrong one to open with.

A sequence that works:

  1. Warm opening, no evaluation. You’re calling as a first contact: to get to know them, explain the role, and see whether there’s a fit for both sides.
  2. Where they are professionally. Let them talk. You’re reading the person, not scoring yet.
  3. What’s missing today. “What’s missing right now that makes you open to listening?” If you sourced them and they weren’t looking, ask what the next step would have to offer to be worth the move.
  4. The function knockouts. Quick binaries first, then the ones that need a real answer.
  5. The cross-cutting basics. Location, work model, languages, salary, availability. Framed honestly: a couple of basics so neither of us wastes time.
  6. The close. Their questions, your pitch, next steps.

And the detail worth stealing: what they tell you at step 3 is the material for step 6. They’ve just told you what’s missing in their current job. If the role has it, say so with their words. Most recruiters collect that answer and then deliver a pitch they’d have given anyone.

None of this is dogma. Cutting on salary first, out of respect for everyone’s time, is a defensible call on a high-volume role. The list and the weights don’t change, only the order.

Decide the threshold, or don’t ask

A question without a threshold is a conversation starter.

The threshold comes from the material: the salary band, the years required, the language level the job actually needs. If the brief doesn’t give you one, leave it blank and flag it. Don’t invent it, and don’t improvise it mid-call, because an improvised threshold is one you’ll set differently for the next person.

That’s often the most useful output of writing the list: you find out the hiring manager never specified what the bar is, and that’s worth a five-minute conversation before you talk to twenty candidates against a standard nobody agreed.

A knockout is a reason to probe

One more rule, and it’s the same principle that runs through the interview scorecard: the tool filters, the person decides.

A salary above the band may be negotiable, or may look different once the package is on the table. A gap in a CV has a thousand legitimate explanations, most of which are nobody’s business. The follow-up exists so that the candidate gets to give the explanation before you conclude anything.

Same bar for everyone, and the bar is about the job. Never style, accent, age, origin, appearance or personal life. If a brief asks you to filter on any of those, the useful move is to find the legitimate requirement underneath it: “someone young” is usually seniority and adaptability, “good presence” is usually how they handle clients and stakeholders. Filter on that instead, and ask it the same way of everybody.

What happens after the screen

The screen tells you who’s worth an hour. It doesn’t tell you who’s good, and the questions that do that are a different set with a different structure: each one with the answer you’re hoping for and the red flag underneath it. We wrote that guide separately, with examples by competency.

For any team screening more than a handful of candidates a month, writing the three routes next to each question is the highest-return hour of preparation there is, because it converts the call from an assessment you make afterwards into a decision you made in advance. If you screen occasionally, even just fixing the salary question and the one trap question for the role will carry most of the benefit.

And if you’d rather not build the list by hand, this method is one of eleven free AI skills our customer success team packaged up. You give it the job description and the brief, it extracts the non-negotiables, confirms them with you, and returns the questions with their routes and thresholds in the order you’d ask them.

The part that doesn’t change: the list narrows, a person decides.

Frequently asked questions

What are screening questions?

The questions on a first call whose job is to decide whether the candidate continues, measured against the role's non-negotiables. They're not an interview guide. An interview explores how good someone is; a screen establishes whether there's any point in having that conversation at all, on things like salary expectation, work authorization, availability and the one or two requirements the job genuinely can't flex on.

How many screening questions should you ask?

Four to eight, and the number comes from the role rather than from a template. You write one per genuine non-negotiable, so if the job has four real knockouts it's four questions. Padding the list with nice-to-haves is the common failure: they stretch the call, they don't change the decision, and they push the real filters to the end when attention has gone.

Should you ask about salary at the start of a screening call?

No, and this trips up a lot of people because salary is usually the most disqualifying thing on the list. Priority and sequence are different questions. Open by letting the candidate talk about where they are professionally, validate that they've actually done the job, then handle salary, location and availability together near the end, framed as basics so neither side wastes time. Cutting on salary first is a defensible choice for high-volume roles, but it's a choice, not the default.

What makes a screening question open rather than closed?

A closed question invites the candidate to tell you what you want to hear. "Have you managed a team?" gets a yes from someone who once had an intern. "Tell me about the last team you were responsible for" gets you something you can evaluate. The test is whether the answer can contain facts you didn't supply.

Can a screening question automatically reject someone?

It shouldn't. A failed knockout is a signal to probe before concluding. A salary above the band may be negotiable or may look different once the whole package is on the table, and a career gap has a thousand legitimate explanations. The follow-up exists to give the candidate a chance to explain, and the decision stays with you.

Sources and method

The method described here is the one behind Nova's Killer Questions skill, built and published by the customer success team. It's free to download as part of the Inbound pack.

Mercedes Gordo
Mercedes Gordo

Head of Delivery and Customer Success

Mercedes Gordo is Head of Delivery and Customer Success at Nova. Mercedes spent two years at LinkedIn in Dublin as a relationship manager and account director, and previously ran Customer Alliance's Spanish operation.

Connect on LinkedIn →
Sourcing and outreach How to Screen CVs Without Throwing Away Good Candidates Sourcing and outreach The Interview Scorecard: How to Score Candidates on the Same Yardstick