Most GCC launch plans have a hiring sequence. Almost none of them survive contact with the Indian talent market.
The reason is arithmetic. Niche AI, cloud and cybersecurity roles in India currently take three to six months to fill and command around a 1.7x salary premium. A country head search typically runs longer. Run those searches one after another in a tidy numbered order and you will be a year into your launch with four people and a board asking questions.
So the useful framing is not a queue. It is three tracks, started at different times because they take different amounts of time, ordered by lead time and dependency rather than by seniority.
Here is what those ten roles are, which track each sits on, and when to start looking.
Why this matters more than it used to
India's GCC market has stopped being a cost decision and the hiring implications are significant.
EY's Future of Pay 2026 report projects GCCs will lead every sector in India on salary growth this year at 10.4%, with skill premiums running 30 to 40% above baseline for AI, machine learning, cybersecurity and cloud capabilities.
Meanwhile, EY's GCC Pulse research found 58% of Indian GCCs already investing in agentic AI with another 29% planning to within a year, 66% prioritizing deep domain expertise, and 63% hiring for niche skills.
You are not competing for engineers. You are competing for a narrow band of specialists against every other GCC in the country, all of whom are also paying premiums. That is what makes the founding team's decision consequential rather than administrative.
One number worth keeping in view: India has roughly 120,000 AI professionals working in GCCs against projected demand crossing a million AI-related roles. The gap is not closing this year.
Track one: start immediately, because they take longest
Hire 1: GCC Head or Country Leader
Start this search before anything else exists, including the entity.
The profile that works is not "has managed a large team." It is someone who has built a center from nothing, can hold budget accountability, knows the local talent market genuinely rather than from a deck, and can influence senior stakeholders at headquarters who have never worked with an India operation.
That last capability is the one companies undervalue and then regret. The country head's hardest job in year one is not managing in India. It is defending the center's mandate at headquarters when someone proposes moving work back.
EY's research names leadership localization as a continuing challenge across Indian GCCs, and this is the role where it bites. The pool of people who have actually done this is small, everyone is chasing them, and the search takes months.
Start it first. Expect it to run four to six months. Use a search partner.
Hire 2: The scarce specialist your mandate depends on
Counterintuitive placement, and deliberate.
Whatever your center's defining capability is, the person who anchors it is a three-to-six-month search at a 1.7x premium. AI or ML architect. Principal engineer. Data engineering lead. Cybersecurity specialist. Regulatory expert.
If you wait until the org chart is populated to start this search, you will start it in month seven and land the person in month twelve, and your engineering team will have spent five months making architecture decisions without them. Start the search now. Land them later. The two things are not the same.
Start immediately, in parallel with hiring one. Do not wait for the country head to arrive to begin the search.
Track two: start once the country head is identified
Hire 3: Talent Acquisition Leader
The first hire your country head makes, and often the one they bring with them.
External agencies give you candidate volume. They do not own your workforce strategy, your compensation positioning, your interview standards or your employer proposition in a market where candidates have five offers. Somebody internal has to.
This person's real job in the first six months is deciding what "good" means for every subsequent role, and defending it when hiring pressure builds. Volume recruiters will fill your requisitions. They will not tell you that the shortlist is wrong.
Hire 4: Head of Technology or Engineering
For a technology-led center, this is where technical direction gets set.
Architecture principles, engineering standards, cloud direction, security requirements, delivery methodology, technical hiring profiles, career paths for engineers.
The reason this cannot wait: every engineer you hire before this person arrives will make defensible local decisions that collectively produce an incoherent system. That rework is expensive and it lands eighteen months later, when it is hardest to fix.
For non-technology mandates, substitute the equivalent functional leader. A finance shared services center needs its process owner here, not a CTO.
Hire 5: Delivery, Product or Program Leader
This role answers the question that most new centers cannot: what exactly does India deliver to the global business, and how would anyone know if it stopped?
Service lines, business stakeholders, delivery milestones, success metrics, process ownership, escalation paths.
Without it, the center becomes a staffing pool. Teams receive work, execute it, and own no outcome. That is the structural difference between a delivery arm and a capability center, and it is decided by whether this role exists early.
Track three: start as headcount approaches thirty
These roles are essential and they are not urgent on day one. Hiring them too early creates overhead against an employee base that does not yet exist.
Hire 6: HR Business Partner or People Leader
One strong person, not a department.
Organization structure, job levels, compensation philosophy, performance management, career progression, retention. The early employees become the cultural reference point for everyone who follows, which means this framework is being set whether or not anyone is deliberately setting it.
Retention is worth designing rather than reacting to. EY's Pulse research put GCC attrition at 9% in 2025, down from 13% in 2023, with upskilling, flexibility and leadership access named as the retention levers. Worth noting the sources disagree: EY's Future of Pay 2026 puts GCC attrition at 14.1% against an all-sector 16.4%, on a different sample. Either way, GCCs retain better than the market, and the reasons are structural rather than financial.
Hire 7: Finance and Operations Lead
Budget, vendors, procurement, controls, cost tracking, operational reporting, coordination with the parent finance function.
The value shows up when leadership starts comparing headcount to output. A center measuring only employee numbers can look like it is succeeding while cost per capability quietly deteriorates. This person builds the reporting that prevents that.
Track cost per productive FTE, time to productivity, utilization, attrition and capability output. Not headcount.
Hire 8: Security, Risk or Compliance Leader
Earlier for regulated sectors, and non-negotiable for financial services and healthcare.
Information security, access controls, data protection, third-party risk, business continuity, incident response, IP protection.
The reason not to defer it: EY's research found only 7% of GCCs have a fully embedded cybersecurity center of excellence, and retrofitting security into systems and processes already in production is materially more expensive than designing it in. The rest of that 93% are paying for it now.
Hire 9: Senior Domain Expert
This is where the founding team becomes specific to your industry rather than generic.
A bank needs a lending or risk specialist. A healthcare company needs regulatory or clinical operations depth. An industrial company needs supply chain or engineering expertise. A SaaS company needs a platform or product expert.
Generic technology talent builds what it is asked to build. Domain expertise changes what gets asked, and it gives the India center credibility with global stakeholders that no amount of delivery performance will substitute for.
Hire 10: Your second scarce specialist
Not an administrator.
The original version of this list ends with a workplace and employee experience lead. That is a real need and it is not a top-ten strategic hire. Facilities, office operations and vendor coordination can be handled by a partner, an EOR, or a BOT arrangement during the launch phase, and most successful centers do exactly that.
Spend the tenth slot on capability instead. A second architect, a second principal engineer, a second domain specialist. Capability density beats headcount at this stage, and three exceptional engineers aligned to a coherent architecture will outproduce ten average ones every time.
What not to hire yet
- A large HR team: One leader sets the framework. Specialists come with scale.
- Middle managers: Early centers need builders, not layers. Layers arrive later and are hard to remove.
- A big internal recruitment team: A strong TA leader plus selective external partners. Build the team as volume justifies it.
- Facilities and admin staff: Outsource during launch.
- Volume engineers before the technical leader lands: This is the most expensive version of the mistake and the most common.
What comes after the first ten
Divide the next hundred into four groups and staff them in this proportion.
- Core capability: People directly delivering the mandate. The largest group.
- Capability multipliers. Architects, technical leads, program managers, trainers. The people who make larger teams effective rather than merely bigger.
- Business enablement. HR, finance, legal, procurement, security, workplace. Scale with organizational complexity, not with headcount.
- Future leadership: Identify your next-generation leaders from the first fifty hires, not when you reach five hundred. Leadership localization is the problem the market has not solved, and the centers that solve it grow their own.
Measure something better than time to hire
Speed is a real constraint and a poor optimization target.
Track five things: time to hire, time to productivity, quality of hire against the capability you specified, capability coverage against your roadmap, and retention of the people you cannot replace.
A fast process that fills roles with the wrong people is not efficient. It is expensive, and the cost surfaces in month nine when you discover the architecture is wrong and the person who would have prevented it is still six weeks from starting.
Conclusion
The first ten people are not early employees. They are the architecture of the organization.
They determine who gets hired next, what standards hold under pressure, how headquarters perceives the center, and whether India ends up owning work or receiving it.
A hundred-person center with weak leadership and fragmented skills is an expensive delivery arm. A ten-person founding team with the right leaders, the right domain depth and a functioning hiring engine builds something you will still want in five years.
Start the long searches first. Run them in parallel. Hire for capability density, then scale.
Planning a founding team and want to know which of these searches will actually be hard in your sector? Talk to us. We will map the availability for your specific roles before you commit to a timeline.
