Screen for Notice Period in the First Call, Not Offer Stage

A recruiter at a mid-size Indian IT services firm once described her worst month this way: four candidates cleared two technical rounds and a manager round for a lateral backend opening, and all four had 90-day notice periods against a role that needed someone in six weeks. Nobody had asked. It wasn’t on the interview scorecard. It came up in the offer call, as a throwaway line before salary negotiation, and by then three panelists and two weeks of scheduling had already been spent on candidates who couldn’t start on time.

That’s the pattern this post is about: notice period is treated as an offer-stage formality when it should be a first-call filter.

Why notice period gets asked too late

Most interview processes are built around skill fit first, logistics second. A JD goes out, resumes get screened for keywords or experience, and the first live conversation, whether it’s a recruiter call or a technical round, spends its time validating whether the person can do the job. Joining timeline comes up only once an offer is close, because it feels like a “detail” compared to whether someone can architect a service or lead a team.

The problem is that joining timeline isn’t a detail for a role with a fixed start date. If a hiring manager needs someone onboarded before a project kickoff, a candidate serving a 90-day notice with no buyout option isn’t a strong-but-slow candidate. They’re not a candidate for that role at all, no matter how the technical rounds go. Screening skill before logistics means the expensive part of the process (panel time, manager time, offer approvals) runs before the cheap disqualifying question does.

How HireQwik’s knockout questions work

HireQwik’s phase-0 knockout questions sit at the start of the AI voice screen, before the substantive part of the interview begins. Their entire design goal is protecting the hours a recruiter would otherwise spend on interviews that were never closeable, not adding another gate for its own sake. A recruiter builds them per job description: they’re not a fixed list HireQwik ships with, they’re questions the recruiter writes for that specific role, based on what would actually disqualify a candidate for it. Notice period fits naturally here. If a JD has a hard start-date requirement, the recruiter adds a knockout question that asks for it directly.

If the candidate’s answer fails the recruiter’s threshold, the call ends early, typically inside the first one to two minutes, with a Reject verdict tagged “knockout” that’s visible to HR in the review queue. The recruiter sees exactly why the call ended short: not a vague “did not proceed,” but the specific disqualifying answer. If the candidate passes, the interview continues into the substantive screening HireQwik is built for: communication assessment, role-specific questions, the two-evaluator scoring layer, the same as any other call.

This is the mechanism working as designed, not a shortcut. The Reject tag means “didn’t meet a stated requirement for this role,” which is a different, more useful signal than “scored low.”

What “knockout” actually means for notice period, and what it doesn’t

It’s worth being precise here, because notice period isn’t a binary pass/fail the way a work-authorization question is. A knockout question about notice period doesn’t mean HireQwik auto-rejects every candidate with a 90-day notice. It means the recruiter set a threshold for the role, say, “flag anyone whose stated notice exceeds 45 days,” and the AI interview asks the question and applies exactly that threshold, consistently, to every candidate in the funnel.

What the recruiter does with a failing answer is still a recruiter decision, and that’s deliberate: the knockout mechanism is built to surface a fact consistently, not to make a judgment call the recruiter is better placed to make. Some teams reject outright, because the role genuinely can’t wait. Others use the knockout flag as a routing signal: a 90-day-notice candidate with a strong resume gets a manual note instead of an automatic reject, and a recruiter decides whether a partial buyout conversation is worth having. The knockout mechanism surfaces the fact early and consistently; the recruiter still owns the judgment call about what to do with it. That distinction matters, because a notice-period mismatch on a strong candidate is often solvable, whether through an early buyout conversation, a flexible start date, or a different open role at the same company, and none of that is possible if the question doesn’t get asked until offer stage.

A worked example: senior backend hire, six-week start window

Take a lateral senior backend engineer JD with a hard six-week start requirement, tied to a client project date. The recruiter builds the screener for this JD with two phase-0 questions: current notice period, and whether a buyout is possible if notice exceeds four weeks. A candidate who answers “90 days, no buyout” fails the knockout, and the call ends at minute one with a Reject tagged “knockout, notice period.” A candidate who answers “60 days, buyout possible for 30 of it” passes the knockout and the interview proceeds into the full screen. The recruiter sees a Go or Strong Go verdict alongside a flag that a buyout conversation is needed before offer.

Compare that to the old flow: both candidates clear two technical rounds, the panel spends four hours combined across both, and the notice-period mismatch surfaces in the offer call for the first candidate, after the client project date has moved closer and the hiring manager has already mentally committed to a start date that can’t happen.

Why a resume filter can’t catch this

It’s tempting to think this is a resume-screening problem rather than an interview-screening one: surely notice period could just be a field on a candidate form. In practice it rarely is, because notice period isn’t a fact that sits on a resume the way experience or skills do; it depends on the candidate’s current employer, their exact date of joining there, and whatever internal exceptions or ongoing project commitments affect their release date. HireQwik’s resume scoring is relevance-aware: it checks whether a candidate’s skills and experience genuinely match the role, which is a different question entirely from when that candidate can start. A resume can score Strong Go on relevance and still be operationally useless for a six-week hiring window. The two filters are answering different questions, and conflating them is exactly how a recruiter ends up interviewing a perfectly-matched candidate who was never actually available.

That’s why the knockout question sits inside the voice interview rather than the resume-scoring stage. It’s the first point in the pipeline where a real conversation happens, which means it’s the first point where a candidate can be asked directly and answer in their own words. “Yes, 60 days, and I can likely negotiate down” carries more information than any checkbox on an application form would.

What shows up in the review queue

A candidate on the other end of a 90-second call experiences that ending very differently than HR does reading about it afterward, which is worth keeping in mind when writing the question in the first place. On the HR side, the entry isn’t just a name with no verdict. It shows the Reject verdict, the “knockout” tag, and, because the call was recorded, the exact words the candidate used that triggered it. A recruiter scanning the queue can tell at a glance whether a batch of rejections came from genuine skill gaps or from a logistics mismatch on an otherwise promising slate of candidates, without having to relisten to a single call to find out. That second case is a useful signal on its own: if half of this week’s applicants for a senior role are failing on notice period, the JD’s start-date requirement might be unrealistic for the current talent pool, and it’s worth loosening before the recruiter burns another two weeks on the same funnel. A knockout log that’s silent on skill and loud on logistics is telling the recruiter something about the JD, not just about the candidates.

The candidate who’s already resigned

One case is worth separating out explicitly: a candidate who has already resigned versus one who hasn’t yet. “90 days, but I’ve already handed in my resignation, so the clock is running” is a materially different answer than “90 days, and I haven’t resigned because I’m still deciding.” The first candidate has a fixed, counting-down date; the second candidate’s 90 days hasn’t even started, and won’t until they accept an offer and formally resign, which could add weeks before the notice period itself begins.

A knockout question that only asks “what’s your notice period” collapses this distinction, since both candidates might give the same number. Asking “have you resigned yet, and if so, what’s your last working day” instead gets the recruiter an actual date rather than a duration that hasn’t started ticking. For a role with a genuinely fixed deadline, that difference can be the whole ballgame: a candidate who’s already resigned with 30 days left might comfortably make a six-week window that a candidate who hasn’t resigned yet, even with the same “90 days” answer, cannot.

There’s a practical reason to nail this detail down fast too: a growing share of Indian tech employers now accept a shorter 30-to-45-day payout in place of the contractual 60-to-90-day term (The Hire Hub, 2026). A recruiter who pins down the real number in call one, instead of assuming the contractual figure applies, has a materially better shot at hitting a tight start date.

The logistics gap this closes for lateral hiring

This sits inside a broader pattern in lateral hiring: campus drives run on a fixed calendar where everyone’s start date is roughly the same, but lateral hiring runs against whatever start date a specific role needs, and that date is almost never asked about until very late. Voice AI screening works for lateral hiring the same way it works for campus drives: the difference is what the recruiter chooses to screen for. A campus JD’s knockout questions are usually about eligibility criteria; a lateral JD’s knockout questions are usually about logistics, because logistics is what breaks lateral hires that skill fit alone wouldn’t catch.

Notice period is the first of these. Expected CTC and location or hybrid-work fit are the same category of problem: a logistics mismatch a recruiter could screen for in minute one, but that traditionally only surfaces after a candidate has cleared every substantive round.

What to build if you’re setting this up

A notice-period knockout question is worth writing into a lateral JD’s screener whenever the role has a real start-date constraint, whether that’s a project kickoff, a backfill for someone already gone, or a client commitment. It’s not worth adding to every JD; a role with flexible onboarding doesn’t need to disqualify on notice period at all, and adding a knockout question where there’s no real constraint just creates false rejections. The question to ask before writing one: is there an actual date this role needs someone by, and would a 90-day-notice candidate genuinely not work for it? If yes, put the question in phase 0. If the honest answer is “we’d probably wait for the right person,” don’t gate on it. Let the recruiter make that call in the “Needs review” band instead of having the AI screen make it automatically.

Wording the question matters more than it seems. “What’s your notice period?” gets a number but nothing else. “What’s your notice period, and is a buyout possible?” gets the number plus the one fact that actually determines whether the mismatch is fixable. A recruiter writing the knockout question should think about what answer would change the decision, not just what fact would confirm a suspicion. The second phrasing surfaces a partial pass that the first would have quietly rejected.

It’s also worth deciding upfront where a partial pass goes. A candidate who says “90 days, but I can push for a 30-day buyout” doesn’t cleanly fail or pass a hard threshold, and this is exactly the kind of judgment call HireQwik’s knockout questions are built to defer, not resolve automatically. HR sets the pass/fail rule for the knockout itself, but a genuinely ambiguous answer can route to the “Needs review” band alongside the AI’s other borderline verdicts, rather than getting auto-rejected on a technicality. That keeps the speed benefit of an automated first filter without losing a candidate over one negotiable fact.

India’s IT sector still runs long notice periods for experienced hires: the same 2026 industry analysis that put NASSCOM’s 90-day figure at the norm for roughly two-thirds of established IT companies hiring experienced professionals also notes that startups and smaller product companies tend to run shorter, 30-to-45-day notice periods (The People’s Board, 2026). That spread is exactly why a knockout threshold has to be set per JD rather than as a company-wide rule. The right cutoff for a services-firm lateral hire and a startup lateral hire aren’t the same number.

If you’re building your first lateral screener on HireQwik and want to see how a phase-0 question interacts with the rest of the scoring pipeline, take the live demo interview yourself, or book a walkthrough and we’ll build the knockout list for your JD with you.