We hear the same opening line on almost every GCC call.
"Let's start with ten engineers and see how it goes."
It sounds sensible. India has the talent, the cost works, and the company already has product managers and engineering leaders back home. So why not hire a group of developers and get shipping?
Because ten engineers without a local leader are still just ten engineers.
Somebody has to understand the Bengaluru or Hyderabad talent market well enough to hire the next twenty. Somebody has to sit between the India team and headquarters. Somebody has to build the recruiter, university and vendor relationships. Somebody has to set the operating culture and deal with the team problems before they turn into resignations.
That somebody is the India site leader, and in our experience it's the single hire that decides whether the India operation becomes an organisation or stays a cost line with ten names on it.
What we mean by "site leader"
The title moves around. India Site Leader, Country Head, GCC Leader, GCC Head, Site Director, India Engineering Head, Managing Director, India Technology Leader. Don't get hung up on it. The mandate is what matters.
The person owns the operation locally. Depending on how you structure it, that covers hiring, workforce planning, culture, office and vendor operations, leadership development, stakeholder management, budgets, talent strategy, local compliance coordination, and, often, engineering delivery. For a new GCC, they're the connective tissue between the global company and the team on the ground.
What actually happens when you hire ten engineers first
We've watched this film enough times to describe the ending.
You hire ten strong engineers in Bengaluru. They're good. But nobody in India owns hiring strategy, retention, career paths, culture, conflict, office operations, recruiter relationships or workforce planning. All of that lands on an overseas manager who now has ten direct reports across a nine-and-a-half to twelve-and-a-half hour time gap, plus their existing job.
Six months later the team has two interpretations of every process, no local career framework, total dependence on US managers for decisions, slow hiring, patchy onboarding, and no succession plan. Then the company hires a site leader to fix it.
That's backwards. The leader should have designed the organisation before the first engineer signed. If you're planning the wider sequence, our post on the first 10 hires for a new India GCC puts this role at number one for exactly this reason.
The leader changes the maths on every hire after them
A good site leader doesn't manage the team you've got. They build the next layer.
Say they join with zero employees in India. Their first job isn't code. It's defining the org structure, identifying the critical early hires, building a hiring roadmap, picking recruitment channels, setting local processes, starting candidate relationships, coordinating the office and establishing a working rhythm with HQ.
Then the engineering hiring starts, and it's coordinated rather than a series of one-off requisitions raised from another continent. That difference compounds. A leader who hires five managers, twenty senior engineers, eighty developers, ten support staff and a handful of AI and data specialists over three years has produced a multiple of their own salary in organisational value. That's the whole argument for leadership-first hiring, and it holds even when the leader's package looks expensive on day one.
Strong leaders attract strong engineers
Senior engineers in India's tech hubs ask the same questions before they say yes. Who will I report to? What's the technical culture? Who makes the engineering decisions here? Does this office have real ownership or is it a ticket queue? Is the India centre strategically important, or is it a cost experiment?
A recognisable local leader answers every one of those. Without that person, candidates read the India office as low-cost execution and price themselves accordingly, or decline. With the right leader, the message becomes "we're building a serious engineering organisation here," and the quality of who applies changes overnight. This is doubly true if you're hiring AI/ML engineers in India, where the good ones pick their boss as carefully as their problem.
The first hire is not always a CTO
Another reflex worth resisting: assuming the first India hire has to be a technical executive.
If headquarters already has a strong CTO and VP Engineering, cloning that structure in India creates a second head with unclear authority. What you probably need instead is someone who can build the local organisation, represent India internally, run local leaders, partner with global engineering, own workforce planning and shape the culture. That's a Site Leader or GCC Head, and it complements HQ rather than competing with it.
If the role really does need to carry technology strategy, then it's a different search. Our guide to hiring a CTO or VP Engineering in India covers that one. Decide which you need before you write the brief, because the candidate pools barely overlap.
What the site leader should own
Scope depends on your model, but for an engineering-heavy GCC the ownership usually splits five ways.
- Talent: hiring strategy, leadership recruitment, employer brand, retention, workforce planning.
- Operations: office, vendors, local policies, budgets.
- People: culture, career development, leadership development, engagement.
- Business alignment: global stakeholder communication, India strategy, capacity planning, reporting.
- Engineering, where applicable: delivery, technical leadership, engineering managers, quality, productivity.
Write down which of those belong to the leader and which stay with HQ. Ambiguity here is where India-HQ friction starts, and it's easier to settle in the offer letter than in month eight.
What a site leader costs in 2026
No single number, because the role spans a leader of 40 people and a leader of 4,000.
Current market data in India puts GCC site director compensation broadly around ₹80 lakh to ₹1.2 crore for mid-scope leadership and ₹1.2 to 2 crore for senior, larger-centre roles, with executive-search data showing packages climbing well beyond that as the operation grows. Treat those as bands. The real question isn't "what does a site leader cost" but "how much responsibility are we handing this person." Someone running 50 employees and someone running a 1,000-person GCC are not the same hire and shouldn't be benchmarked as one.
Where to hire them
Bengaluru for technology-heavy GCCs and product engineering. Hyderabad for enterprise technology and large-scale centres. Pune for a mature enterprise engineering market. Delhi NCR if you're spanning tech, fintech, SaaS, consulting and business operations. Chennai for engineering depth with enterprise and industrial technology.
The leader doesn't have to live in the launch city forever, but they need to know its talent market cold and be comfortable being the face of the company there. If you haven't picked the city yet, Bengaluru vs Hyderabad vs Pune vs NCR will shorten the debate.
What their CV should actually show
Titles are a weak signal. Building is a strong one.
Look for someone who has launched a GCC or engineering centre, managed 100-plus people, hired engineering leaders rather than just engineers, worked with an international HQ, owned a budget, run cross-functional teams, built a local culture, scaled an org and lived through a reorg. They also need to understand how a global company operates. An India centre isn't an independent startup. It has to fit the parent's structure while owning enough locally to move fast, and that balance is a learned skill.
Manager versus site leader
- A manager asks: how do I get more out of my ten engineers?
- A site leader asks: what organisation do we need to support the next three years?
If your India operation is meant to become a real business capability, you need someone asking the second question. A very good manager will run ten people well and still leave you without an organisation.
The first 90 days
Days 1 to 30: understand. Meet the CEO, CTO, VP Engineering, HR, finance, product, existing managers and the global stakeholders who'll depend on India. Absorb the business strategy, the India objectives, the hiring plan, the budget, the roadmap and the cultural expectations. Map the local talent market.
Days 31 to 60: design. Build the operating plan: org structure, hiring roadmap, leadership needs, location strategy, compensation strategy, recruitment channels, office plan, operating cadence including the US-India time-zone overlap model. The organisation gets designed before large-scale recruitment starts. That order is the whole point.
Days 61 to 90: build. Hiring accelerates. Engineering managers, staff engineers, recruiters, HR, operations, the first engineering teams. Because there's a design underneath it, the hiring is coordinated rather than reactive.
Culture doesn't ship from headquarters on its own
HQ might prize blunt disagreement in meetings. Some of your India hires will hesitate to challenge a senior stakeholder on a call, not because they lack opinions but because nobody's shown them it's safe. A strong local leader builds a culture where pushback is expected, and carries local realities back to HQ in the other direction. That two-way translation doesn't happen by itself, and it certainly doesn't happen through a manager eleven time zones away.
Retention is the other half
Hiring is half the problem. Keeping people in a market where competitors are calling them monthly is the other half. A site leader shapes career paths, promotions, recognition, leadership development, team mobility and learning. Without that, employees feel disconnected from the wider company, and disconnected employees answer recruiter messages.
The right sequence
For a real GCC or serious India operation, the order that works: site leader first, then founding leadership across engineering, HR, finance and operations, then staff and principal engineers and engineering managers, then the core engineering teams, then specialist capability in AI, cloud, security, data, DevOps and QA.
Not a rigid formula. A small team with strong HQ engineering leadership might sensibly start with a senior engineer. But if you're building something you'd describe as a "centre," leadership goes in early. For how the later phases play out in weeks, see how fast you can ramp a pod in India.
How to interview one
Skip the tour of their previous titles. Ask about decisions.
"Tell me about an organisation you built from nothing. What was your first hire, and why that one?" "How did you sequence the next ten?" "Talk me through a hiring miss and what you changed." "How did you keep your strongest leaders when they were being poached?" "How did you get HQ to invest more in India?" "HQ wants 100 hires this year and the market can support 50 good ones. What do you do?" "How would you build trust between India and US engineering?"
Builders answer those with specifics and trade-offs. Managers answer with frameworks.
Does the site leader need to be technical?
For an engineering-heavy centre, technically credible, yes. The strongest engineer in the building, no.
They should understand software development, engineering org design, product development, cloud, architecture and technical hiring well enough to hire and judge technical leaders. They don't need to review pull requests. Their job is to build the environment where the people who do can do their best work.
If you need engineers now
You don't have to pick between "wait six months for a leader" and "hire ten engineers with no leader."
The hybrid works: start the site leader search today, bring in a dedicated teams pod or augmented engineers for immediate capacity, hire the permanent leadership, then fold the interim capability into the long-term org where it fits. Product work doesn't stall, and the leader inherits a working team instead of an empty floor. If the plan is to own the entity eventually, the Build-Own-Transfer model is built for exactly this handover, and when staff augmentation makes sense covers the interim phase.
When to start the search
Earlier than you think. If you want 100 people in India in twelve months, the site leader should be in the planning conversation well before the first hiring wave, because the leadership search itself runs six to ten weeks, senior notice periods run 60 to 90 days, and once they land they need time to build relationships before they can hire at pace. A leader who starts three months before your target launch is arriving late.
The short version
If your India strategy is "get ten developers because India is cost-effective," you're thinking about the market the way people did in 2012. Companies are building product teams, R&D centres, AI organisations and strategic capability here now, and that needs leadership.
Ten engineers can write code. A great site leader builds a system that lets hundreds of engineers succeed. That's why the leader comes first.
We run the search as part of GCC building or as a standalone specialist hiring mandate for GCC Leaders, Site Heads, CTOs and VPs Engineering. Tell us the scope you have in mind and we'll send you five profiles, free. No retainer, no obligation, just leaders who've built this before.
