Screen Expected CTC Before You Burn a Recruiter Call

A TA lead at a fintech told us about a recruiter on her team who spent a full morning doing intro calls for a mid-senior product manager role: five 30-minute calls, five candidates who all sounded promising on the resume. Three of them stated a salary expectation more than 40% above the approved band, on the call, almost as an afterthought near the end. Two and a half hours had already gone into conversations that a two-minute question at the start would have prevented.

This is the expected-CTC problem, and it’s a version of the same mistake that lets notice period slip to offer stage: a fact that determines whether the hire can happen at all gets asked last instead of first.

Why salary expectation gets buried in the call

Recruiters avoid opening with a salary question because it feels transactional. Asking about money before establishing rapport can read as rude, or worse, like the company only cares about getting someone cheap. So the convention is to build rapport first, walk through the role, gauge interest, and only then circle to compensation, usually near the end of the call. That ordering makes social sense. It makes almost no operational sense when the point of the call is to filter, not to sell.

The result is a structurally backwards process: the most disqualifying question, whether this person’s number and our number are even in the same range, gets asked after every other filter has already run. A candidate can pass a resume screen, pass a phone screen’s soft-skill read, and still be a non-starter purely on budget, and nobody finds out until 25 minutes into a call that was scheduled for 30.

How a CTC knockout question works on HireQwik

The mechanism is the same phase-0 knockout structure used for any JD-specific disqualifier: the recruiter writes the question into the screener build for that role, sets a pass range, and the AI voice interview asks it in the first minute or two, before the substantive screening begins. For expected CTC, the recruiter isn’t trying to extract an exact number. They’re checking whether the candidate’s stated expectation falls inside a band wide enough to be negotiable. A candidate whose answer falls outside that band gets a Reject verdict tagged “knockout,” visible in the review queue with the specific figure they gave, so the recruiter isn’t guessing why the call ended early.

A candidate whose answer falls inside the band continues into the rest of the interview: the two-evaluator speech-quality layer, the role-specific questions, everything the AI screen is actually built to assess. What that call looked like before the candidate ever uploaded a resume is the same pipeline a compensation knockout sits inside, not a separate system layered on top of it. The knockout question doesn’t replace the recruiter’s negotiation; it just makes sure the recruiter’s time only goes toward candidates where a negotiation is realistically possible.

Setting the range wide enough to be useful

The most common mistake in building this knockout is setting the range too tight. A recruiter who knows the approved band is ₹18-22 LPA might be tempted to knock out anyone quoting above ₹22 LPA outright. That’s usually a mistake, because approved bands often have flex built in that the recruiter can access with a strong justification. A candidate at ₹24 LPA with the exact skill set the team has been missing for two quarters is worth a conversation, not an automatic reject.

A better pattern is to set the knockout threshold at the point past which no realistic approval process would close the gap, say, 25-30% above the top of the band, and let anything inside that wider range pass through to a human recruiter’s judgment. The knockout question is there to catch the candidates who are structurally unreachable, like someone expecting double the role’s ceiling, not to enforce the exact number on the approval sheet. Treat the knockout as a coarse filter for “is this conversation possible at all,” and leave the fine negotiation to the recruiter who actually has room to move.

This threshold isn’t a set-once decision either. A recruiter running the same JD for three or four weeks can watch the knockout log and see whether the market is answering with numbers that cluster just above the current threshold, a sign the approved band itself might be under market for this role, not that candidates are overreaching. That’s a different problem than the knockout question was built to solve, but the knockout log is often the first place it becomes visible, well before a hiring manager would otherwise notice the requisition is stalling on compensation.

A worked example: two candidates, one JD

Say a JD for a senior data engineer has an approved band of ₹28-35 LPA, and the recruiter sets the knockout threshold at ₹42 LPA, roughly 20% above the top of the range. Candidate A states an expectation of ₹38 LPA on the call: above the band, but inside the knockout threshold, so the interview continues, and the transcript flags “compensation above stated band, needs approval discussion” for the recruiter to see alongside the verdict. Candidate B states ₹55 LPA, well past the threshold, and the call ends there with a Reject tagged “knockout, compensation,” saving what would otherwise have been a 20-30 minute conversation with someone the role could never realistically afford.

Neither candidate was wrong to state their number, and neither answer reflects badly on them. The knockout question just makes sure the mismatch shows up in minute two instead of minute twenty-five, before anyone’s calendar has been touched.

Where this differs from the notice-period knockout

It’s worth being explicit about how a CTC knockout is different from a notice-period knockout, because they look structurally similar but fail in different ways. Notice period is close to binary: a candidate either can or can’t hit a start date, with a buyout as the main variable. Expected CTC is a range problem with a negotiation built in on both sides. Budget approval can often move, and candidates often quote a number they’d flex on if the rest of the offer is strong. A recruiter who treats a CTC knockout like a hard notice-period cutoff will reject candidates who would have happily negotiated down, and lose good hires to an overly literal threshold. The band needs to be set with that flexibility in mind: wide enough to admit genuine negotiations, tight enough to still filter out the calls that were never going anywhere.

Two answers that don’t fit a clean number

CTC in Indian compensation packages is rarely one clean number, and not every candidate gives one. A candidate might quote a figure that’s entirely fixed, or a figure that bundles in a variable bonus that pays out at 60% most years, or a figure that includes ESOPs valued at a strike price nobody can verify from a screening call. Two candidates who both say “₹32 LPA” can mean very different things by it, and a knockout question that only captures the headline number risks passing a mismatch through, or rejecting a candidate whose real fixed component is perfectly in range. The fix is to make the knockout question specific about which number matters for the range check: if the approved band is a fixed-CTC figure, ask for fixed compensation specifically, not “total CTC,” and expect candidates to need a follow-up prompt to separate the two, since most people quote whichever number is larger by habit.

A related but different answer is no number at all. Some candidates, especially more senior ones, deflect a direct compensation question, saying something like “I’m open, let’s discuss” or “depends on the role scope,” as a negotiating tactic learned from years of being told never to name a number first. A knockout question built around an exact figure handles this poorly: a deflection isn’t a knockout-worthy answer, but it’s also not a usable one. The better design treats a genuine deflection as a pass-through rather than a fail, since punishing caution isn’t the same as catching a real budget mismatch. The knockout should fire only on a stated number outside the range, not on an unwillingness to state one. Routing that case to the “Needs review” band, with a note that the candidate deflected the CTC question, keeps a strong but cautious candidate in the pipeline instead of losing them to a filter that assumed silence meant disqualification.

A failed knockout isn’t always the end of the road

The math behind a 60%+ auto-reject rate applies here too: a large share of any Reject bucket, CTC-tagged or otherwise, is a routing problem more than a quality problem. It’s worth building for the case where a candidate fails a CTC knockout on one JD but is a genuine fit for a different open role with a higher band. This happens more often than recruiters expect, especially at companies running several lateral searches at once: a candidate whose expectation is 25% above a mid-senior JD’s ceiling might sit comfortably inside a senior JD’s band that opened the same month. Treating a knockout fail as a dead end for that candidate rather than a role-fit signal wastes a sourcing effort that already happened.

The practical version of this is simple: when a knockout fires on compensation, the recruiter’s own note in the review queue is the moment to ask whether this candidate belongs on a different requisition instead of being closed out entirely. HireQwik doesn’t route this automatically, since matching a candidate to a different open role is a judgment call, but the knockout reason being visible and specific (the exact figure the candidate gave, not just “rejected”) makes that judgment call fast rather than requiring a fresh look at the resume from scratch.

Why this matters more in lateral hiring than campus

The setup choices that separate a campus drive from a lateral search run deeper than compensation alone, but compensation is where the difference shows up first. Campus hiring runs on a fixed stipend or CTC band that’s the same for every candidate in a batch, so there’s rarely a mismatch to screen for. The number is set before the drive even opens. Lateral hiring is the opposite: every candidate arrives with their own number, shaped by their current pay, their market read, and how many other offers they’re weighing. That variance is exactly why a CTC knockout question earns its place in a lateral screener and rarely makes sense for a campus one. There’s variance to catch on one side and none on the other.

Why the savings compound across a funnel, not just one call

The value of catching a CTC mismatch early is easiest to see in a single call, but it compounds faster than it looks across a real lateral hiring funnel. A recruiter running a search for one senior role might screen 15-20 candidates before shortlisting three or four for the hiring manager. If a third of those calls end in a late-discovered compensation mismatch, that’s not one wasted call. It’s a third of the recruiter’s week on that requisition spent on conversations that were structurally unwinnable from the first minute. Traditional phone screens already run ₹85-150 and 10-15 minutes each even when they end cleanly; a screen that runs the full 25-30 minutes before a mismatch surfaces costs proportionally more, and it costs the recruiter’s attention on top of the raw time.

That compounding is also why the knockout question earns its place even on roles where the recruiter feels confident they already have a good read on the market rate. Confidence about the market doesn’t protect against an individual candidate’s specific number. Someone coming from a higher-paying industry, or someone who’s been offered a competing package this same week, breaks the pattern the recruiter expects, and that’s exactly the case a two-minute question catches before a 30-minute one has to.

What we’re seeing in the broader India hiring data

The pattern behind this post isn’t unique to any one company. Indian senior-role offer acceptance runs at roughly 55-65%, well below the roughly 74% figure typically cited for the US market (hire22.ai, 2026). Part of that gap traces back to how large a jump candidates expect when they switch jobs at all: lateral moves in competitive Indian tech skills routinely carry 30-to-50% increment expectations, well above what a static approved band anticipates when it was set months earlier (The Hire Hub, 2026). A compensation gap discovered at offer stage, after weeks of interviews, a background check, and an approval cycle, is exactly the kind of late-stage surprise that widens that gap further. The same mismatch discovered in the first two minutes of a screening call costs nothing more than that call.

If you’re building a lateral screener and want help setting a CTC knockout range that’s wide enough to stay fair but tight enough to save real recruiter time, book a walkthrough and we’ll build it with you against your actual approved bands.