Hiring a GCC Site Leader: The First Hire That Matters Most

The first three hires matter more than the first 300

Most teams obsess over headcount. They model a 20-person pod, draw an org chart, and start filling boxes. That is backwards. The trajectory of a GCC is set by its first three hires — above all by the GCC site leader — long before the org chart fills out.

The reason is leverage. A strong site leader recruits other strong people, sets the engineering bar, and earns the trust that lets headquarters hand over work that matters. A weak one becomes a bottleneck you route around, and every hire after them inherits the ceiling they set. That is the discipline behind "the first three hires matter more than the first 300": you are not staffing a team, you are choosing the person who will build it.

Zinnov's framing is that GCC maturity — once a decade-long journey from cost center to strategic hub — is now compressed into the setup decision. As we lay out in the 90-day build playbook, the first quarter is mostly about one thing: landing the right leader.

Functional leader vs operational caretaker

The single most consequential choice is what kind of leader you hire. There are two archetypes, and they are not interchangeable.

• The operational caretaker. Keeps the lights on — payroll questions, facilities, HR escalations, status reports back to HQ. Necessary work, but it produces a back office. Engineers under a caretaker get a ticket queue, not a mission.
• The functional leader. A real engineering leader who has shipped product and run teams. They own technical decisions, set the hiring bar, push back when the spec from HQ is wrong, and are accountable for outcomes — not activity. Engineers under a functional leader get ownership.

The caretaker model is how dispersed extension teams quietly fail. The functional model is how a site becomes a second home for engineering. Put bluntly: a GCC succeeds when it owns something real and is led by someone senior. Hire the caretaker and you have built a cost center with extra steps.

The dual mandate: run the site and own a global function

The best GCC site leaders today carry a dual mandate. They run the India site — the people, the culture, the local execution — and they own a global function that spans the whole company, not just the India location.

That second half matters more than it sounds. A leader who only manages the location is, structurally, a regional manager. A leader who owns global platform, or global support, or a product pillar end-to-end has a mandate the strongest candidates actually want, and the authority to deliver it.

It is also a retention mechanism. Indian engineers, in rough order, optimize for competitive money, an impressive title, and growth. A global mandate delivers all three: real scope, a senior title that means something, and room to learn. A ticket queue delivers none of them, which is why caretaker-led sites churn. Aim to keep attrition below roughly 12% — well under the IT-services benchmark — and a credible mandate is how you get there. The same talent depth that makes this possible is why India leads in AI engineering talent.

How to assess a GCC site leader

You are hiring for judgment under ambiguity, not a checklist of technologies. Probe a few things hard:

• Builder track record. Have they actually built a team from a handful of people to scale — hiring, firing, setting the bar — or just inherited one? Ask for the specific numbers and timelines.
• Technical credibility. Engineers will not follow someone they do not respect technically. The leader has to be someone your best HQ engineers would take a code review from.
• HQ relationship. Can they manage up across time zones, disagree with a VP, and still keep trust? A site leader who only says yes is a caretaker in disguise.
• Recruiting magnetism. Their first real job is hiring. Can they close senior candidates who hold three or four competing offers? In India, that is the live market reality.
• Ownership instinct. Do they ask "what do we own?" before "how many people do I get?" The right answer is the question itself.

What a real site leader costs

Expect a total compensation band of roughly ₹1.5–2.5 crore per year — about $160K–$265K at ₹94 to the dollar — for a genuine functional leader with a dual mandate. That is the price of someone who has built and scaled before.

Two things to understand about that number. First, it is the one place in your GCC where the cost arbitrage is thinnest: India engineering talent runs roughly 3× cheaper than the US at the IC level, but the multiple compresses toward 2.7× at leadership, because senior leaders are scarce and globally mobile. Second, it is the highest-ROI line item in the entire build. Underpay here and you do not save money — you cap the value of every dollar you spend downstream. For how the full pod economics work, see what a GCC in India costs.

This is executive search, not IC recruiting

Here is where most first-time builders go wrong. They run the site leader hire through the same funnel as an engineer — job post, screen, panel, offer. That funnel finds available people. It does not find the best people, who are employed, not looking, and being courted by everyone.

Hiring a site leader is executive search: mapping the market, approaching passive candidates, selling the mandate, and closing against counteroffers. The Indian market makes this sharper — interview-to-offer ratios run around 7:1, and strong candidates routinely hold three to four simultaneous offers. You do not win that by posting a job. You win it with a real mandate, a credible story, and someone running a deliberate search. That is also why an experienced partner matters; see how we run the build.

The proof: how Cognite turned it around

Cognite's India story is the clearest case study we have. It began as a dispersed extension team — one or two people embedded in each global team. It did not work. There was no clear ROI, no clean performance ratings, no real engagement. The classic caretaker-era outcome.

The turnaround was a leadership decision, not a headcount decision. Cognite brought in senior, globally-mandated India leaders — an engineering VP, a support VP, a value-delivery VP — and then built whole teams under them. Crucially, those teams owned something real: full product pillars end-to-end, value delivery, and insourced global support, rather than scattered tickets.

The result: the site went from 55 to 120 people in about nine months, including 81 hires in a single 2.5-month sprint, and is now described internally as one of the company's futuristic hubs. Same country, same talent pool, same company — the only variable that changed was leadership and mandate.

A GCC succeeds when it owns something real and is led by someone senior. Everything else is downstream of that one hire.

If you are weighing whether to build it yourself or have a partner stand up the leader and pod, the build-operate-transfer model is worth understanding — it lets someone else carry the early hiring risk while you keep the option to own the entity outright.