Most India capability centres do not fail at entity setup. They fail at hire number seven. The legal work is bounded and solvable incorporation, PF and ESI registration, a Shops and Establishments licence, a rented floor in Whitefield or Hitec City. The hiring is not bounded, and that is where the timeline quietly slips by two quarters.
The pattern repeats across new centres: the parent company approves a 20-person headcount plan, hires a country head in month four instead of month one, then discovers that nobody has a recruiting function, an employer brand, or a compensation benchmark in India. By the time the first engineer signs, the board has already asked twice why the centre is behind plan.
Planning the gcc first 20 hires is a sequencing problem before it is a sourcing problem. Roles are easy to list. The order is what determines whether month six ends with 20 productive people or 11 offers, four reneges, and a country head who spends their first quarter doing recruitment coordination instead of building a mandate.
India hosts over 1,700 global capability centres employing more than 1.9 million professionals, with the sector projected to reach 2,400+ centres and roughly $100 billion by 2030. Every new centre is competing for leadership talent inside that same pool.
That number cuts both ways. Depth of talent is real; so is the competition for the few hundred people who have actually built a centre from zero.
TL;DR
This guide lays out the gcc first 20 hires in the order they should actually be made, with a six-month timeline and an indicative salary budget per wave. It is written for founders, COOs and global engineering leaders who have board approval for an India centre and now need a defensible gcc initial hiring plan.
The single number to hold onto: a 20-person engineering-led centre in Bengaluru or Hyderabad runs roughly ₹6.5–9 crore in annualised fixed compensation, and the country head search alone typically consumes 10–14 weeks before anyone else can be hired.
By the end you will know which four hiring waves to run, what each wave costs, which roles to deliberately delay, and whether your ramp needs an internal recruiter, a search firm, or an outsourced recruiting engine.
What The GCC First 20 Hires Actually Are
The global capability centre’s first 20 hires are the founding cohort of a new capability centre, typically one country or site leader, a talent acquisition lead, two to four engineering or functional leads, a compliance and people-operations spine, and ten to twelve individual contributors. They are hired in waves, not in parallel, because each wave creates the authority and capacity needed to hire the next.
That definition matters because it separates headcount from sequence. A spreadsheet with 20 rows is not a plan. A plan says which rows unlock the others.
The Real Problem: Authority, Not Availability
New centres consistently underestimate the leadership hiring window by 3–4x. A country head search runs 10–14 weeks from kickoff to signed offer in a normal market, plus a 60-to-90-day notice period that Indian senior candidates almost always serve in full. That is five to seven months from approval to a leader who is actually at their desk before a single engineer is interviewed.
Meanwhile the compensation ground is moving underneath the plan. GCCs are projected to lead every sector in India in 2026 salary increments at 10.4%, with skill premiums of 30–40% for AI, machine learning, cybersecurity and cloud capabilities, according to EY’s Future of Pay 2026 report. A budget benchmarked eight months ago is already 8–10% light.
The third constraint is invisible until it bites: employer brand cold start. A new centre has zero name recognition in the Indian market. Candidates weighing your offer against a known product company are pricing in risk you cannot see on the comp sheet. Expect offer-to-join ratios well below your home-market norms in the first two quarters, and budget for it rather than being surprised by it.
The Gcc Ramp Up Sequence That Actually Works
The gcc ramp up sequence below is organised into four waves across six months. Each wave has a gating condition that triggers the next wave. Skipping a gate is the single most common cause of a stalled ramp.
Wave 1 (Months 0–3): The Country Head, And Nothing Else
Who should be the first hire in a GCC in India is not a debate worth having: it is the country or site leader. This person needs 15+ years of experience, prior zero-to-one or P&L exposure, and enough standing to push back on parent-company leadership when the mandate drifts.
Run this as a retained search, not a contingency one. Contingency firms optimise for volume; there are perhaps a few hundred credible GCC builders in India and they are all employed. Start the search three to four months before your office is ready, because the notice period is the constraint, not the shortlist.
The gating condition: the country head must have signing authority and interview veto before Wave 2 opens. A first hires capability center plan that lets HQ hire the leadership spine without the country head produces a team that reports upward to three different time zones and owns nothing.
Wave 2 (Months 2–4): The Hiring Engine And The Compliance Spine
This is where most plans go wrong by deferring. A senior talent acquisition lead is not an overhead hire; they are the multiplier for the remaining 17 roles. Hire them second, not tenth.
Alongside TA, stand up a small people-operations and finance layer: one HR operations generalist and one finance/compliance manager covering payroll, PF/ESI, TDS and statutory filings. Many centres outsource the statutory piece to a firm for the first year and keep only an internal owner, which is usually the right call at this scale.
The gcc founding team at the end of Wave 2 is four people. None of them write code. That feels wrong to engineering leaders and it is correct anyway.
Wave 3 (Months 3–5): Engineering And Functional Leads
Now hire two to four leads: an engineering manager, a principal engineer or architect, and depending on mandate, a product or data lead. These people do three jobs at once: they define the technical bar, they interview, and they give ICs a reason to join a brand nobody in India has heard of.
Strong senior candidates take offers from unknown centres for exactly one reason: a credible leader they can learn from. If your leads are mediocre, your ICs will be too, and no compensation band will fix it. This is also the wave where infrastructure specialisation shows up if the mandate includes platform ownership, this is when you hire DevOps engineers and hire cloud engineers rather than back-filling them after the application teams are staffed.
Wave 4 (Months 4–6): Individual Contributors
Ten to twelve ICs, hired in two batches rather than one. Batching matters: the first batch of five to six exposes every gap in your onboarding, your access provisioning, and your HQ collaboration model. Fix those before the second batch lands, or you will replicate the friction across twelve people instead of six.
Keep a deliberate seniority mix roughly one senior to two mid-level engineers. All-senior teams are expensive and get bored; all-mid teams need leads who have no time to lead.
The Six-Month Sequence At A Glance
| Wave | Months | Roles | Cumulative headcount | Gating condition to proceed |
| 1 | 0–3 | Country/site head | 1 | Leader onboarded with signing authority |
| 2 | 2–4 | TA lead, HR ops, finance/compliance manager | 4 | Recruiting function live, comp bands signed off |
| 3 | 3–5 | 2–4 engineering/functional leads | 7–8 | Interview loop defined, technical bar set |
| 4 | 4–6 | 10–12 ICs (two batches) + IT/workplace | 20 | Batch 1 onboarding retro complete |
What The First 20 Hires Cost
Indicative annual fixed-compensation bands for Bengaluru and Hyderabad in 2026. Pune, Chennai and NCR typically run 10–20% below Bengaluru for equivalent seniority; treat these as planning ranges and re-benchmark at offer stage.
| Wave | Role | Indicative annual CTC (₹) |
| 1 | Country/site head | 60 lakh – 1.2 crore |
| 2 | Talent acquisition lead | 35–55 lakh |
| 2 | HR operations + finance/compliance | 45–65 lakh combined |
| 3 | Engineering manager / architect (each) | 45–80 lakh |
| 4 | Senior IC (each) | 28–45 lakh |
| 4 | Mid-level IC (each) | 16–28 lakh |
| 4 | IT / workplace support | 10–18 lakh |
A 20-person engineering-led centre lands at roughly ₹6.5 — 9 crore in annualised fixed compensation, before variable pay (averaging 16.1% of fixed across Indian employers), real estate, equipment and statutory overhead. Add 25–35% on top of fixed comp for a realistic fully-loaded cost per seat.
One budgeting detail that only shows up in practice: build in a 10–15% offer-premium reserve for the first two quarters. You will need it to close at least three of your first ten candidates, and discovering that mid-negotiation costs you the candidate and two weeks.
Case Studies: How The Sequence Plays Out
A European fintech building an India engineering centre. The parent ran its own leadership search for four months, hired a country head, then handed the same team a 15-person engineering mandate with no recruiting capacity in India. Shortlists arrived through three contingency vendors with overlapping candidates. Once a dedicated sourcing pod was put in place with a single owner and a fixed interview loop, the remaining roles closed inside two hiring cycles rather than trickling in over two more quarters.
A healthtech scaling from a 6-person outpost to a full centre. The existing team had no TA function; the engineering lead was running first-round screens. Moving screening and coordination to a dedicated pod returned roughly 12–15 hours a week to the engineering lead and compressed time-to-shortlist to under two weeks per role. The unlock was not sourcing volume, it was removing interview coordination from the person whose job was to set the technical bar.
Who Should Actually Do The Hiring
The decision that determines whether the ramp holds is not what to hire but who runs the hiring. Four options, honestly compared:
| Model | Best for | Typical constraint |
| Internal recruiter (1 FTE) | Steady-state hiring after month 9 | One recruiter realistically closes 2–4 roles/month; 20 roles in 5 months does not fit |
| Contingency agencies | One-off niche roles | Overlapping candidate pools, no ownership of the funnel |
| Retained executive search | Country head and leads only | Cost and cycle time make it wrong for IC volume |
| Recruitment process outsourcing | Ramp phases of 15–100 hires in under two quarters | Requires a defined comp band and interview loop before kickoff |
Arithmetic is the whole argument. Twenty hires in five months, minus notice periods, minus a 60–70% offer-to-join ratio in the first quarter, means roughly 35–40 offers and several hundred screened candidates. That is a full-time recruiting operation and you are trying to run it with a recruiter you have not yet hired.
What Most Teams Get Wrong
Three failures recur, and none of them are about sourcing.
First, hiring the country head too junior to defend the mandate. A leader who cannot hold a room with parent-company CXOs will watch the centre get reduced to maintenance work within 18 months.
Second, deferring the talent acquisition lead to position ten or later this single decision roughly doubles the time-to-fill on every subsequent role.
Third, treating the compliance layer as something to sort out later; payroll, statutory filings and IP assignment cannot be retrofitted under pressure once 20 people are on the books.
A fourth, subtler one: writing job descriptions that are direct translations of HQ roles. Indian titles carry different seniority weight, and a mismatched title costs you candidates before compensation is ever discussed. Fix the ladder mapping before the first role goes live, not after three rejections.
Before You Sign The Headcount Plan
If you have board approval for an India centre and a 20-row headcount spreadsheet, the useful next step is not sourcing; it is stress-testing the sequence and the comp bands against what the market is actually paying this quarter.
Supersourcing has run global capability center setup and ramp hiring across 527+ delivered engagements, including centres for fintech, healthtech and enterprise SaaS clients, with a 98% candidate joining rate and a 7–10 day replacement guarantee if a hire is not a fit.
Send your headcount plan and target start date to mayank@engineerbabu.com, or book a working session at supersourcing.com/contact-us. If your ramp is under two quarters, ask specifically about the recruitment process outsourcing model rather than role-by-role IT staffing services; the economics diverge sharply above 15 hires.
FAQ
Who do you hire first when setting up a GCC?
The country or site head, without exception. This role holds the mandate, sets the compensation philosophy and gives every subsequent candidate a reason to join an unknown brand. Hiring ICs before leadership creates a team reporting into HQ across time zones with no local ownership, a structure that is very hard to unwind later.
How long does it take to hire a GCC country head?
Budget 10–14 weeks from search kickoff to signed offer, plus a 60–90 day notice period that senior Indian candidates typically serve in full. That is five to seven months before the leader is operational. Start this search three to four months before your office lease begins, not after.
What is the salary budget for the first 20 GCC hires?
Roughly ₹6.5–9 crore in annualised fixed compensation for an engineering-led centre in Bengaluru or Hyderabad, plus 25–35% for variable pay, real estate, equipment and statutory costs. Tier-2 and non-Bengaluru metros run 10–20% lower for equivalent seniority.
How many recruiters do you need for 20 hires in 6 months?
One recruiter closes two to four roles a month in a competitive market. Twenty roles across five active months, accounting for drop-offs and reneges, needs two to three dedicated sourcing and coordination people which is why most centres outsource the ramp and internalise recruiting afterwards.
Should a new GCC use an internal recruiter or an outsourced model?
Use retained search for the country head and leads, an outsourced ramp team for IC volume, and an internal recruiter from month nine onward for steady-state hiring. The mistake is picking one model for all three phases. If you are mid-decision, it is worth pressure-testing your sequence against someone who has run the ramp before committing a budget.
Does the sequence change for a non-engineering GCC?
The waves hold. Only Wave 3 changes; a finance or analytics centre hires a functional lead instead of an engineering manager, but the country head, TA lead and compliance spine come first regardless of mandate.
