GCC, Site & Engineering Leadership
Site, Country & GCC Leadership
Read this before you spend six months applying. The data says something specific about how these roles are filled, and it is not through job boards.
This atlas contains 2,082 leadership postings. Of those, 44 are Vice President, 31 are Chief-something, 18 General Manager, 6 Country Manager and 4 Site Lead. Against 595 Director and 517 Principal Engineer postings. That ratio is the most useful thing on this page.
What the ratio actually means
It does not mean the roles are rare. India's GCC sector employs well over a million people and every one of those centres has a site leader. It means they are not filled through public postings. Executive search firms, internal promotion, and transfer of a trusted leader from headquarters account for nearly all of them, and by the time a role reaches a job board the shortlist frequently already exists.
So a strategy of watching job boards for GCC Head roles will mostly return nothing, and the small number that surface will be the ones where internal succession failed — which is not always the job you want.
What actually works instead, in order of yield
Be visible to search firms. Korn Ferry, Egon Zehnder, Heidrick, Spencer Stuart and the India specialists run this market. Being known to two or three partners who cover technology GCCs is worth more than any number of applications. That relationship takes a year to build and cannot be started when you need it.
Take the Director role at a company whose India centre is growing. Site leadership is very often an internal step, so the reliable route is to be inside the organisation one level below when the centre expands. Look for employers announcing India expansion — those are the seats that open.
Own a global charter from India, not an India charter. The single biggest differentiator between a site leader and a large-team manager is whether they owned outcomes globally or executed work defined elsewhere. That distinction is decided years before the interview.
What the job is, when you get it
| Time | What you are actually doing |
|---|---|
| Morning | Local. Attrition, hiring pipeline, compensation review, a facilities issue, a skip-level. The site's health is your line responsibility whatever your functional title says. |
| Midday | Functional. You have a reporting line into a global function — engineering, product, operations — and a matrix relationship with the site. Most of the difficulty in this role lives in that seam. |
| Afternoon | Global overlap. Calls with headquarters. The window is short, so the agenda you set for it determines what your site gets credit for. |
| Ongoing | Statutory and regulatory. Entity governance, labour compliance, data-residency questions, sometimes a board. This is real work that engineering leaders arrive underprepared for. |
The interview
The question that decides it: “What would you change about how work reaches this centre?”
Interviewer: “Our India centre delivers well but headquarters still treats it as an execution arm. What would you do?”
A weak answer. “I'd focus on building trust with the global leadership team, invest in upskilling, and look for opportunities to take on more strategic work over time.” Every GCC leader says this. It contains no mechanism, no timeline and nothing falsifiable, and the interviewer has heard it from every candidate this month.
A strong answer. “The pattern is almost always structural rather than cultural, so I'd look at where decisions are actually made rather than at attitudes. Three things I'd check in the first month.
First, does anyone here own a product outcome end to end, or do we own components of outcomes owned elsewhere? If it's the second, no amount of trust-building changes the perception, because the org chart says we execute.
Second, where does the roadmap get set, and is anyone from this site in that room at the point the decision is made rather than at the readout? Being consulted is not the same as deciding.
Third, what is the attrition of our strongest people, and where do they go? If they leave for product companies at the same level, we are not offering scope, and that is measurable.
Then I'd pick one charter — a whole product surface, small enough that headquarters can afford to let it go — and get it moved here with the decision rights attached, not just the headcount. One genuine transfer of ownership does more in a year than five years of relationship-building, because it changes what people here can put on a CV.
I'd expect to be measured on that, and I'd want the charter agreed before I take the role rather than promised after.”
The strong answer treats it as an operating-model problem with observable evidence, and negotiates the mandate before accepting. Candidates who accept the role on a promise of ‘more strategic work later’ are the ones who leave in eighteen months.
What to have ready
- A charter you moved. Work that was owned elsewhere and is now owned by your team, with the decision rights, and what it took to get it.
- Attrition numbers you can defend — regretted attrition specifically, with the trend and what you changed.
- A hiring story at scale. Growing a team by a hundred in a year without the quality bar collapsing is a specific skill and it gets probed hard.
- A governance answer. What you did about a statutory, labour or data-residency requirement. Engineering leaders routinely have nothing here and it is disqualifying at site level.
- A cost conversation. GCCs are funded on a cost-arbitrage case and defended on a capability case. Be able to make the second argument with numbers.
Compensation
| Level | India band (total) | Notes |
|---|---|---|
| Engineering Director | ₹80L – ₹1.6Cr | The band with the most public postings |
| Senior Director / VP | ₹1.5Cr – ₹3Cr | Long-term incentive becomes the majority of the package |
| Site / Country Head | ₹2.5Cr – ₹6Cr+ | Wide, entity-dependent, almost never advertised |
Estimated. No Indian posting in this corpus published a band — zero of 337 — so these come from market reference rather than measurement, and should be treated as directional. The practical consequence is the same as elsewhere in India: decline to disclose current compensation and anchor on a target.
Red flags
A site role with a dotted line to everything and a solid line to nothing. Ask who writes your objectives and who signs your appraisal. If the answer is unclear at interview it will be worse in the job.
“Strategic work will follow.” Get the charter in writing before you accept. Promised scope that depends on future goodwill is the most common reason these roles disappoint.
No P&L, no headcount authority, no hiring bar ownership. That is a large-team management job with a leadership title.
The centre exists purely for cost. Nothing wrong with it, but the ceiling is fixed and you should know that going in rather than discovering it in year two.
What this role tests
Themes, and where to learn them
These chapters are shared across every role that tests them, so preparation here compounds rather than being spent once.
Practice questions across all themes → · Back to GCC, Site & Engineering Leadership →