Screening Location Fit for Senior Roles: Onsite vs Hybrid

Two India GCCs, hiring for similar mid-senior data roles the same month: one runs a five-day, in-office mandate tied directly to variable pay and promotion decisions; the other asks for three days a week and counts six hours as a full day. A recruiter working both requisitions told us she kept forgetting which policy applied to which call, and twice scheduled a technical round for a candidate who, it turned out, was looking specifically because their current employer had just moved to the stricter policy, the exact opposite of what the new role offered.

That mismatch is avoidable, and it’s avoidable in the same place notice period and expected CTC mismatches are avoidable: the first two minutes of the screening call, not the third interview round.

Why location fit became a real filter again

For most of the last decade, “location” on a JD meant a city, and the screening question was simple: are you local, or will you relocate. Hybrid and return-to-office policies have made that question genuinely more complicated. It’s no longer binary. A candidate might be fine with three office days but not five, fine with a 45-minute commute but not 90, or actively job-hunting because their current employer just tightened a policy that used to be flexible. None of that shows up on a resume, and none of it is captured by a simple checkbox question like “based in Bangalore: yes/no.”

This matters more for senior and lateral hires than for campus hiring, because senior candidates usually have an existing job with an existing attendance policy, and they’re comparing the new role’s policy against the one they’re trying to leave. A campus hire has no baseline to compare against; a lateral hire almost always does, and that comparison is often the actual reason they’re interviewing at all.

Setting up the knockout question

The mechanism is the same phase-0 knockout structure used for logistics screening on any lateral JD: the recruiter writes a question specific to the role’s actual attendance policy, not a generic “are you open to hybrid work” that every candidate will answer yes to regardless of what they mean by it. A useful version names the specifics, something like “can you commit to three in-office days a week at the Bangalore office, effective from your start date,” because the vague version produces vague answers that don’t actually filter anything.

A candidate whose answer doesn’t match the policy gets a Reject verdict tagged “knockout,” visible in the review queue the same way any other knockout rejection is, along with what they actually said. A candidate whose answer matches continues into the rest of the interview, same as any other passed knockout. The point isn’t to make the policy itself the topic of the interview. It’s to rule out, in the first minute, a mismatch that would otherwise surface in the third round when a hiring manager asks about start date and the candidate mentions they’re actually looking for fully remote.

The relocation edge case

Location screening has one edge case that a hard knockout threshold handles badly: the candidate who isn’t currently local but says they’re willing to relocate. That’s not the same situation as a candidate who’s simply unwilling to meet the attendance policy, and treating it identically, an automatic reject for anyone not already in the right city, throws away candidates who might be exactly who the role needs.

The better design routes a stated relocation intent to the “Needs review” band rather than auto-rejecting it, treating it as a fact worth a second look rather than a fact worth an automatic verdict. HireQwik’s knockout mechanism gives the recruiter this choice: a knockout question can be written narrowly enough to only fail candidates who explicitly decline the policy, while anyone who says “yes, willing to relocate” or “yes, planning to move by [date]” passes through with that answer flagged for the recruiter to evaluate. A relocation claim is worth a human read, since whether the timeline is realistic and whether the role’s start date allows for it are judgment calls in a way a hard current-location filter can’t make on its own.

Why “the company’s policy” is rarely one answer

Attendance policy at a large GCC or IT services firm isn’t always uniform across the company, and it isn’t always one city either. One business unit might run a strict five-day mandate while a sister team two floors down runs a genuinely flexible hybrid arrangement, because policy rollout happened team by team rather than company-wide. A knockout question written against “the company’s policy” fails here, because there isn’t one single answer to check the candidate’s response against. The fix is the same discipline that applies to notice period and CTC: write the knockout question against the specific team’s actual policy, not the company’s stated one, and treat “the policy” as something to verify per requisition rather than assume from the last JD. A recruiter hiring for a specific business unit should confirm the real, current attendance requirement for that unit before writing the phase-0 question, not the policy from the company’s careers page, which may be aspirational or already out of date for the team that’s actually hiring.

The same problem shows up geographically when one JD is hiring for multiple offices at once. A GCC opening the same senior data-analytics role across Pune, Bangalore, and Hyderabad might genuinely run three different attendance rules across those cities, shaped by lease size, local team headcount, or how long each office has been open. A single knockout question naming one city fails candidates applying from the other two for no real reason; they’d have been fine under the policy for the office they actually applied to. The workaround isn’t a separate JD per city, which multiplies recruiter setup effort for what’s structurally one search. It’s building the knockout question to first confirm which office the candidate is targeting, then check attendance fit against that specific office’s rule, effectively two short questions chained together rather than one. Skipping either of these steps, team-level or city-level, produces a knockout question that filters against the wrong standard, which is worse than not filtering at all because it creates false confidence in a bad number.

The soft version: measuring willingness, not just current fact

Not every candidate a knockout question would reject in the first 60 seconds is actually a bad fit for the pipeline, which is exactly why not every attendance policy is worth a hard pass/fail gate on day one. Some teams are earlier in figuring out what they’ll actually enforce, and want the interview to surface a candidate’s general comfort with in-office expectations without disqualifying anyone outright before the policy itself is finalized. For that case, the same question can be built as a data-gathering item rather than a knockout: the AI still asks it, still records the answer in the transcript, but doesn’t route to an automatic Reject. That answer becomes a column a recruiter can sort candidates by manually, useful the moment the policy firms up, without having pre-emptively cut anyone based on a rule that wasn’t locked in yet.

Staffing and consulting engagements run this backwards

Banking, insurance, and BPO staffing engagements flip this whole setup: it’s rarely the employer’s own preference driving the attendance answer, it’s a named client sitting five floors up in the same building the consultant will report to on day one. A staffing firm placing someone on a Mumbai banking client’s fraud-analytics desk isn’t asking “what’s our attendance culture,” it’s asking “will this person show up at Nariman Point five days a week for the length of a nine-month engagement,” and that answer genuinely differs contract to contract, sometimes even desk to desk within the same client.

Naming the actual client site inside the knockout question, rather than describing an internal company culture that doesn’t govern this placement at all, changes what the AI screen is really checking. “Can you work five days a week from our client’s office in Nariman Point for the length of this engagement” gets a cleanly checkable yes or no; a generic hybrid-culture question doesn’t, because there’s no internal hybrid culture to ask about here. Consultants weighing a staffing offer also read this kind of specificity as a good sign: it tells them the placement is real and defined, not a vague bench assignment waiting for a project to materialize.

A worked example: two answers, two outcomes

Take a senior finance-ops JD at a GCC with a three-day office policy in Pune, sourced the same way any trigger-based lateral campaign on HireQwik gets set up. The recruiter’s knockout question asks directly whether the candidate can commit to three in-office days a week at that location from the start date. Candidate A, currently based in Mumbai on a fully remote role, answers “no, I’m looking specifically for remote positions.” That’s a clean mismatch, the call ends with a Reject tagged “knockout, location,” and the recruiter loses nothing but two minutes. Candidate B, currently based in Hyderabad, answers “yes, I’m already planning to relocate to Pune for family reasons, can start within three weeks.” That’s not a knockout fail even though the candidate isn’t in Pune today; it passes through with a flag, and the interview continues into the substantive screen.

Same starting fact, a candidate not currently in the required city, two entirely different outcomes, because the question was built to catch policy mismatch, not geography on its own.

Why this is a live problem right now, not a hypothetical

The gap between what employers are asking for and what candidates will accept is wide enough to be measurable. Roughly 40% of job seekers say they’d turn down an offer that lacked flexible working options, even as India’s largest IT services firms move toward stricter in-office mandates. TCS has tied office presence directly to variable pay and promotion decisions, and Wipro requires at least six hours across three office days a week (Pro Edge Hub, 2026; Cynosure, 2026). GCCs, which broadly offer more flexible arrangements than the traditional services firms, have become one of the fastest-growing hiring segments in Indian tech partly on the strength of that difference. Quality mismatch, not policy mismatch, is already the biggest constraint GCC talent leaders report, cited by roughly a quarter of respondents in a 2026 industry survey as their primary hiring challenge (Ceipal, citing the Taggd GCC Talent Lab Survey 2026). A location knockout question doesn’t fix quality mismatch, but it does make sure recruiter time isn’t split between the two problems unknowingly. A candidate rejected for policy fit should never get counted as evidence of a quality gap.

The contrarian part: a strict policy is a real cost, not just a filter

It’s worth saying plainly: a location knockout question is not a neutral piece of screening infrastructure. Every candidate it rejects is a candidate who was otherwise interested in the role and said no specifically because of the attendance policy, and at senior levels, in a market where a meaningful share of job seekers will decline an offer over exactly this, that’s not a small filter. A recruiter who sees a JD generating a steady stream of location knockouts isn’t just running an efficient screen; they’re watching a real signal that the policy is costing the company candidates it would otherwise have hired. The knockout question doesn’t create that cost. It just makes the cost visible early instead of hiding it inside a slow, expensive funnel that quietly underperforms without anyone tracing it back to the policy.

Where this fits with the rest of a lateral screener

Location fit, notice period, and expected CTC are the same category of question: logistics facts that determine whether a hire is even possible before skill fit is worth evaluating, and the setup differences between a campus drive and a lateral search are exactly where that category first shows up. That’s the pattern across lateral hiring generally: campus JDs rarely need any of these three, because the calendar, the stipend band, and the campus location are already fixed for the whole drive. A lateral JD needs a recruiter to actively decide which of these three, if any, are worth gating on for this specific role. Not every senior JD needs a location knockout. A fully remote role has nothing to screen for here. But for any role with a real, enforced attendance policy, it belongs in phase 0 next to notice period and compensation, not buried in round three.

If you’re setting up a lateral screener and want help deciding which logistics questions are worth gating on for your specific roles, book a walkthrough. We’ll look at your actual attendance and compensation policies and build the phase-0 list around them.