What should the first 100 hires for a GCC in India look like?
The first 100 hires for a GCC in India should start with one senior leader, add two senior engineers chosen by that leader, and then grow in pods of five to eight with their own engineering manager. People operations, finance and recruiting join before headcount passes about twenty. A global capability centre that hires in that order spends its first year building a team. One that hires engineers first spends it looking for a leader to manage people it did not choose. This guide sets out the order stage by stage. For the structure behind it, see our India team build approach.
"Our board has approved a hundred roles in India over two years. I have a budget and a charter, but I do not know what order to hire in or what to leave until later."Typical question from a COO opening a first GCC
The order in brief.
Four stages carry most of the weight. Headcount in each is approximate, because the right number depends on the mandate.
| Stage | Who to hire | What it unlocks | Watch for |
|---|---|---|---|
| Hires 1 to 5 | India leader, two senior engineers, a strong generalist, an early specialist | A technical bar, a hiring loop run locally and the first credible shortlist for everyone after | Hiring engineers before the leader, so the bar is set by whoever interviews first |
| Hires 6 to 20 | Engineering managers, first pods, a recruiter, an HR lead, a finance and administration lead | Pods that can ship, and an operation that can onboard and pay people | Letting engineers run hiring and onboarding in their spare time |
| Hires 21 to 50 | More pods, platform and data roles, a second layer of leaders, an employer brand lead | Capacity to take on larger scope from the parent company | A recruiting plan that depends on one or two people |
| Hires 51 to 100 | Directors, specialist teams, internal mobility and learning roles | An operation that hires and develops without the parent company in the loop | Hiring ahead of the work the parent will actually hand over |
Hires 1 to 5: the leader and the bar.
The first hire is a senior engineering leader, before any individual contributor. That person sets the technical bar, gives every later candidate someone credible to report to, and can assess local talent in a market the parent company may not know. Our guide to the first hire for an India engineering centre explains why. The leader then picks two senior engineers, adds a strong generalist for the gaps the plan did not predict, and only then a first real specialist.
Leadership searches are slower than engineer searches. Plan eight to fourteen weeks from brief to signed offer, then a notice period of 60 to 90 days on top; see notice period management in India. Our executive search practice runs these searches, and the NBA India technology team, built leadership-first, closed with 100% offer acceptance and zero attrition at 12 months. The details are in the NBA case study.
Hires 6 to 20: pods and the first operations.
Once the leader is in seat, hiring moves to pods: a small group of five to eight engineers with an engineering manager or tech lead. This is also the point to hire the first non-engineers. A recruiter, an HR lead and a finance and administration lead should arrive before headcount passes about twenty, because every engineer hired without them costs a day of someone else's time.
An in-house recruiter or an embedded hiring partner keeps hiring moving while engineering leaders run the product. Waiting until hire 30 usually means a year of slower hiring.
Your own entity, an employer of record or a mix decides who runs payroll and benefits. Our comparison of GCC vs EOR vs recruitment agency covers each route, and our guide to employee benefits in India covers what the offer must include.
Tell us how many hires you plan in the first year and we will tell you what the hiring plan should look like.
Discuss a mandate →Hires 21 to 50: the second layer and the engine.
Between 21 and 50 hires, the GCC either builds a repeatable engine or becomes dependent on a few people. Add a second layer of leaders so the India head is not the only senior contact. Bring in platform, data and quality roles that individual pods do not justify on their own. Build a hiring process that works without the founding team: a shared brief template, a consistent interview loop and a pipeline report that shows where candidates are stuck.
Compensation matters more at this scale, because every offer sets a precedent. Our India GCC compensation benchmarks give directional bands by level and city. City choice also starts to matter: Bengaluru, Hyderabad and Pune compete for the same people on different terms, and our comparison of the three cities shows how.
Hires 51 to 100: building an operation that hires itself.
After about fifty people, the work changes from building a team to building an organisation. Directors take over pods, specialist teams form, and learning and internal mobility become real parts of retention. The hiring plan should now follow the work the parent company is actually handing over, not the original forecast. A GCC that hires ahead of its mandate runs into attrition and idle capacity at the same time.
Where teams lose months.
It feels faster. It usually means the leader is later recruited into a team they did not choose, which is a harder search and a weaker offer.
A hiring plan built for a mature head office rarely fits a new India centre. Roles, levels and offers need to match the Indian market.
Hiring 100 people in two years means about one hire a week. That is a full-time function, not a task for engineering managers.
How we help at Talhive.
We run the hiring that decides how fast a GCC gets going. Our executive search practice finds the India leader, our engineering and AI recruitment builds the first pods, and India team build sequences the whole plan. Every search starts with an assessment brief, 93% of the people we place are still in role at 12 months, and our case studies include NBA India, Loopio and ketteQ. If the leader is the hardest hire, see how to hire an India leadership team without a local network. For a specific city, we run dedicated hiring in Bengaluru, Hyderabad and Pune.
Send us your GCC charter and hiring plan and we will tell you where the first hundred hires are most likely to slow down.
See how an India team build works →