Key takeaways
- A GCC will give you a big title cheaply. Two people can hold the same VP badge and run jobs that share almost nothing: one owns a global charter, the other runs a delivery team on someone else's roadmap.
- Read the mandate, the reporting line and your pull with the parent before you read the number. If the scope can't be stated plainly, the role is still being defined, which cuts both ways.
- Read the package against the level, not the rupee figure. The gap between a real VP mandate and an inflated one shows up in the variable and equity, not the base.
The mandate tells you more than the title.
A GCC will offer you a big title. Head of Engineering. VP, Operations. Site Leader. The title is the easy part for them to give, because it costs nothing and closes candidates fast. What sits under the title is the thing worth reading, and it comes from the live mandates we run every day and the compensation data behind our Compensation Index.
Ask what you actually own. Not the team size, though that matters. The charter. Are you accountable for a product, a function, a P&L line, or the running of a site? A clear mandate reads like a sentence you could say to the global CEO in one breath. A vague one arrives padded with words like "drive," "partner" and "influence."
If the scope can't be stated plainly, that's information. It usually means the role is being defined as you negotiate, which cuts both ways. You can shape it, or you can inherit whatever's left after the org settles.
Build or run changes the whole job.
There are two very different leadership jobs inside a GCC, and they attract different people. A build mandate is greenfield: standing up a function, hiring the first layer, writing the operating model, carrying the risk that it doesn't land. A run mandate takes something that exists and makes it perform on scale, efficiency, retention and predictability.
Neither is superior. But they reward different strengths and they get judged on different clocks. Build roles buy you eighteen months of goodwill and then expect a standing function. Run roles judge you on this quarter's numbers. Know which one you're signing up for, because the offer rarely spells it out.
Read the reporting line, then read it again.
Who you report to tells you where the real seniority sits. A VP who reports to the India Site Leader is running a sub-function. A Director who reports into a global functional head sitting in the US or Europe is often the more senior job, with a direct line to where budgets and headcount get decided.
Ask two questions. Where does my manager sit in the global org? And who sets my objectives, the parent or the site? A local reporting line with a dotted line to global is common. The question is which line carries your review, your rating and your next promotion. The same badge can sit on either side of that line, and the signals below tell you which one you are being offered.
| Signal in the offer | A real charter (wired in) | A delivery run (walled off) |
|---|---|---|
| What you own | A product, function or P&L the business runs on | A team delivering someone else's roadmap |
| Reporting line | Into a global functional head | Into the India site leader |
| Who sets objectives | The parent | The site |
| Global peers | Named counterparts in other regions | Local only |
| Where the comp sits | Weight in variable and long-term against a real mandate | Strong base bolted onto a thin scope |
Your pull with the parent org is the hidden asset.
The most valuable thing a GCC role can give a senior leader is standing with the global parent. That's what turns a capability centre job into a global career. Look for the signals. Do you have global peers or only local ones? Is any part of the global product or function owned out of India, with your name on it? Will you present to the parent's leadership, or will your site head carry your work upward and take the credit?
A role wired into the parent org compounds. One walled off inside the India site can stall, however senior the title reads on paper.
A title costs a centre nothing and closes candidates fast. The mandate, the reporting line and your pull with the parent cost them something real. Read those, in writing, before you read the number.
Sachith Rai · Managing Director and Founder, Recruise
The seniority behind the number.
Comp is a signal too, once you read it against the level rather than the rupee figure. A strong base bolted onto a thin mandate should worry you more than a modest base on a real charter. Benchmark the whole package against what the level actually pays. Our Compensation Index tracks GCC leadership bands, and the difference between a real VP mandate and an inflated one usually shows up in the variable and equity rather than the base.
So before you accept, get the mandate, the reporting line and your pull with the parent org in writing. Read the package against the level rather than the number alone. If the scope is still vague when the offer lands, negotiate the charter before you negotiate the rupees. Our guide on negotiating the package covers where the give really is.
Frequently Asked Questions
What should a Director actually own in a GCC mandate?
The charter, not just the team size. A real mandate reads like a sentence you could say to the global CEO in one breath: accountability for a product, a function, a P&L line, or the running of a site. If the scope can only be described in vague verbs like "drive" or "influence", the role is still being defined.
What's the difference between a build and a run GCC leadership role?
A build mandate is greenfield: standing up a function, hiring the first layer, and carrying the risk it lands. A run mandate takes something that exists and makes it perform on scale, efficiency and retention. They reward different strengths and are judged on different clocks, and the offer rarely spells out which one you are signing up for.
Why does the reporting line matter more than the title?
It tells you where the real seniority sits. A Director reporting into a global functional head can outrank a VP reporting to the local site leader. The line that carries your review, your rating and your next promotion is the one that matters, not the badge on the offer.
How should a senior candidate read the compensation in a GCC offer?
Read it against the level, not the rupee figure. A strong base bolted onto a thin mandate should worry you more than a modest base on a real charter, and the difference between a genuine VP mandate and an inflated one usually shows up in the variable and equity rather than the base.
Read the senior market before you make the move.
One signal from the GCC leadership market, the read behind it, and one thing worth doing — from the desks of Sachith Rai and Christabel Singh. About a five-minute read.
More career guidance for senior leaders.
Career guidance Is a GCC leadership move right for you: how the seat compares to services, product and the startup path
A senior leader’s honest comparison of a GCC seat against a services firm, a product company and a startup — what it buys, what it costs, and who it suits.
Career guidance Director to VP in a GCC: the levers that move you up
The Director-to-VP jump is rarely about tenure or a strong appraisal. It is about changing what you own before anyone hands you the title.
Career guidance Negotiating a GCC leadership package: base, variable, equity and the levers that matter
Senior GCC comp is built differently. How the package is actually assembled — and where the give really is at Director and VP level.
Career guidance From VP to the C-suite in a GCC: what turns a functional leader into a global operator
Three doors open past a VP seat — Country head, global functional owner, and the parent’s C-suite. What to own now to reach the one you want.