The mandate test: five questions that reveal whether a GCC head owns hiring

You have the offer. Head of the India centre, a headcount plan, a mandate that reads as if you run the place. On paper the hiring authority is yours. Whether it is yours in practice depends on decisions the parent made about the operating model before your name came up, and those decisions are almost never in the offer letter.

These are real leadership seats at scale, 150-plus global CXOs already run functions out of India’s GCCs, on ANSR’s count, with Business Standard corroborating the trend. This matters more for a GCC than for a domestic leadership role because a capability centre sits inside another company’s reporting lines. The budget is set at headquarters. The bands are often global. The function you lead may report on a dotted line to a counterpart 8 time zones away who also thinks they own it. A title of “head” is compatible with all of that, and with the opposite of all of that. It doesn’t discriminate.

So you have to make it discriminate. The offer conversation is the one moment you have the upper hand and the parent is still selling. Use it to ask five questions that a nominal mandate cannot answer cleanly. Real authority answers them fast, with a name and a number. Nominal authority answers them with a process, a committee, or a promise to sort it out later.

Richard Feynman liked to say he preferred a question he couldn’t answer to an answer he wasn’t allowed to question, and the offer conversation rewards the same instinct. A confident title is an answer you are being invited not to question. The five questions below turn it back into something you can test, and what you are listening for is whether each answer comes back with a name and a number, or dissolves the moment you push on it.

Start here because signing authority is the cleanest proxy for the rest. If you can put an offer in front of a candidate and it goes out under your name and your budget, most of the other questions resolve in your favour. If the offer has to travel to a comp desk at headquarters for a countersignature, you are running a recommendation engine, and the candidate can feel the difference in how long the process takes and how firm your word is.

A real-authority answer names a ceiling and hands you everything under it. “You approve up to this band; above it, we talk.” That is a mandate you can hire against, because you know exactly where your discretion ends. The candidate you want will read that as speed and seriousness.

Approval itself is normal. Every centre has a threshold above which the parent wants a conversation. The red flag is that no threshold is named, so in practice everything is escalated and nothing is yours. Ask for the number. If there isn’t one, that is the answer.

Signing an offer is worthless if you can’t set the number on it. Global bands exist for good reasons, and inside a large multinational they are usually non-negotiable at the row level. That is fine for the bulk of your hiring. It becomes a problem at exactly the roles you were hired to win, where the local market has re-priced a scarce skill faster than the global grid has caught up.

Demand for that scarce end is not abstract. India’s Net Employment Outlook was +68% for Q2 2026, the strongest reading since 2008, yet 82% of employers reported difficulty finding the skills they need, according to ManpowerGroup’s Employment Outlook Survey. When intent is that high and supply that thin, a fixed band that no one can flex will lose you the candidate to a competitor who can.

So the real question is who owns the exception. A real answer gives you a mechanism: you can request a band flex for a named skill, and there is a person, not a committee, who says yes or no inside a week. A red flag is a band that is fixed, an exception process that is undefined, and a shrug when you ask who signs it off. That is where good offers go to expire.

This is the question that embarrasses people, which is why it works. At some point the parent will put forward a candidate. A relocating employee, a leader’s former colleague, someone HQ wants placed in the centre. The referral is legitimate. The question is whether it is a suggestion you can weigh or an instruction you have to absorb.

A real-authority answer treats the HQ referral as a strong candidate who still has to clear your bar, and is comfortable saying so out loud. “We’ll send them your way. If they’re not right, they’re not right.” That is a leader who has been given a team and expected to build it.

The red flag is softer and harder to catch. “We’d expect you to find room for them.” Or a long pause before someone reassures you that of course you have the final say, while everyone in the room knows how the last 3 of these went. If you cannot decline an HQ candidate without it becoming a political event, you administer hiring more than you own it. Ask the question directly and watch who looks at whom before answering.

Growth headcount gets attention in the offer conversation because it is exciting. Backfill is where authority actually lives, because attrition is constant and unglamorous, and how a centre handles a departure reveals who really controls the seat. In a market this active, you will run this play often; India’s tech and GCC attrition has sat in double digits in recent years, ICRA puts top-tier IT attrition around 13% and Aon overall India attrition at 16.2%, so backfill is the base load.

A real answer is dull in the right way. When someone leaves, their seat is pre-approved inside your plan and you refill it. You may inform finance; you do not audition for the replacement. That is a leader trusted to keep their own team whole.

The red flag is a re-justification loop. Every departure reopens the headcount question, a finance owner who is not you decides whether the seat survives, and a 2-week vacancy becomes a 2-month one while the case is made again. Centres run this way bleed capability quietly, because the org chart says the team is fully staffed while a third of the seats are stuck in approval. If backfill isn’t yours, your team is only ever as stable as someone else’s spreadsheet.

The first four questions test authority in calm conditions. This one tests it under load. You will, eventually, disagree with the parent about a hire. You want the person; they don’t, or they want theirs and you don’t. The design question is simple: when that happens, who decides?

A real-authority answer names the tiebreaker in advance, and for local roles it is often you. “On centre hires below the leadership tier, your call is final.” That is a boundary you can operate inside, because you know which decisions are genuinely yours and which you share. Shared authority is fine, as long as the sharing is defined.

The red flag is the answer that sounds most reasonable. “We work it out as a team.” It sounds collaborative and it means nothing, because it does not say what happens when the team can’t agree. In an operating model where budget, bands, and reporting lines all originate at headquarters, an undefined tie will break upward every time, and you will discover the pattern one hire too late. Make them name the tiebreaker. If they can’t, or if it’s always someone at HQ, you have your answer about who owns hiring, and it isn’t you.