Site icon HexGn

The First 25 Hires of a New India GCC

TALENT & HIRING The first 25 hires of a new GCC HEXGN INSIGHTS · 05

Organisational research and operator experience agree on an uncomfortable truth: the culture, quality bar and market reputation of an institution are substantially set by its earliest members, and reset only at great cost. For an India capability centre, that means the first twenty-five hires are not early operations — they are the strategy. This playbook sequences those hires, shows the data behind the two decisions companies most often get wrong, and catalogues the failure modes that recur across struggling centres.

The idea in brief. Sequence beats speed: one leader, then four-to-five anchor leads, then a senior-weighted proof team, then the multipliers (talent acquisition, operations, first graduates). Each stage exists to de-risk the next. The recurring failures — hiring teams before leaders, cloning HQ profiles, unstructured interviewing at founding-cohort stakes, slow offers, and silence between offer and joining — are all choices, and all avoidable.

Why sequence is the strategy

Founding cohorts exhibit what organisational scholars call imprinting: early members’ standards propagate through every subsequent interview, review and promotion. In a GCC this operates with special force, because the founding team also constitutes your employer brand in a market that runs on referral and reputation. The practical consequence: who you hire matters enormously, but in what order determines who you are able to hire at all. Strong leaders recruit strong anchors; strong anchors attract strong engineers. The reverse chains do not exist — which is why “we’ll start the team while the head search runs” is the sentence that precedes most founding-cohort regrets.

Hire 1: the centre head — before anything else

Every experienced builder gives the same first instruction: do not hire engineer one before the leader is signed. The reasons are mechanical, not sentimental — and one of them is measurable:

A credible head compresses every search Median days to fill, by role tier — strong vs weak centre-head brand (indicative) 0501001502004590Anchor leadsSenior eng.2850Mid-levelStrong headWeak head Illustrative model — HexGn analysis; parameters described in the text.

The chart’s gap is the leader’s gravitational field at work. In India’s referral-and-reputation market, senior candidates conduct diligence on who they would work for before what they would work on; a respected head measurably compresses every downstream search, while an unknown or weak one lengthens them all — the difference compounds across hundreds of future hires. Add the head’s other jobs — setting the interview bar, negotiating the mandate with HQ, authoring the culture — and the sequencing rule explains itself. Treat the search as the executive hire it is: a full quarter, CEO-level sponsorship, a package that clears the market. (The complete argument, archetypes and interview method occupy the next article in this series.)

Hires 2–6: the anchor leads

Next, the leads for each early function: typically two or three engineering or delivery leads, one people/talent anchor, one operations anchor. These five will interview everyone who follows; their collective judgement is your selection system in human form.

Two disciplines at this stage:

  1. The symmetry test. Would your HQ team enthusiastically hire this person for the same role there? If not, do not hire them here. Every “good enough for the India office” decision compounds into a second-class institution — and India’s talent market reads the signal instantly.
  2. Complementary origins. Blend product-company alumni (craft, ownership instincts) with services-industry alumni (delivery discipline, client empathy). Monocultures of either kind develop predictable pathologies; the blend is where strong centres live. (Our product-vs-services analysis unpacks the stereotypes worth keeping and discarding.)

Hires 7–20: the proof team — senior-weighted, deliberately

Now build the first delivery pods, and here the cost model and the strategy openly disagree. The cost model wants juniors; the strategy wants proof. The founding mandate is to ship something visible to headquarters within a quarter, because early wins purchase the trust that purchases bigger mandates — and senior engineers produce early wins. The pyramid inverts later:

Invert the pyramid later, not first Seniority mix of headcount, % — founding cohort vs mature centre (indicative) 017.53552.57055%20%SeniorMid-level10%35%Early careerFounding 25At scale Illustrative model — HexGn analysis; parameters described in the text.

That right-hand profile — the broad-based pyramid with a large early-career layer — is the correct destination: it is where India’s economics shine and where your campus pipeline (article 21 in this series) pays off annually. Starting there, however, converts your first year into a training program without trainers. Sequence: seniors prove; mids scale; graduates arrive in cohort five with mentors waiting.

Interviewing at this stage deserves founding-cohort rigour: structured scorecards, work samples, calibrated debriefs. Twenty-five hires means several hundred interviews; unstructured, that volume produces a team selected by accumulated mood. The selection-science literature is unambiguous — structured methods roughly double predictive validity over unstructured conversation (Schmidt & Hunter, 1998) — and the founding cohort is the worst conceivable place to ignore it.

Hires 21–25: the multipliers

The interview architecture, specified

“Structured interviewing” is invoked more often than implemented; for the founding cohort, the architecture deserves specification. The loop that serves a 25-hire founding phase, per role family:

  1. Stage 1 — measured screen (60–90 minutes, online): a cognitive/reasoning instrument plus a hands-on skills task appropriate to the family (coding exercise, case, work sample). This stage exists to make the funnel merit-ordered before any human hour is spent — the selection-science backbone (see the validity evidence in article 22).
  2. Stage 2 — craft deep-dive (90 minutes, one senior interviewer): the candidate’s real work, interrogated — a system they built, a close they ran, a model they shipped — with a scorecard anchored on depth, trade-off reasoning and honesty about failures. One interviewer, deliberately: calibration beats committee at this stage.
  3. Stage 3 — ownership and collaboration panel (60 minutes, two interviewers): behaviourally anchored questions on initiative, cross-border collaboration and conflict — the “will they own outcomes at 9,000 kilometres’ distance” stage.
  4. Stage 4 — bar-raiser conversation (45 minutes, head or anchor from another team): a deliberately independent vote whose only mandate is the symmetry test — would HQ hire this person? Founding cohorts drift without an institutional sceptic; this seat is the drift-brake.
  5. Debrief, same week: written scores before discussion (anchoring discipline), decision by rubric not consensus-fatigue, and offer-or-decline within days — the speed the market demands, achieved by calendar design rather than corner-cutting.

Total candidate time: four to five hours — substantial, and correct for hires whose standards propagate through hundreds of successors. The architecture also produces a side asset: by hire 25 you possess calibrated scorecard data on every early employee, the seed of the promotion and development machinery the scale phase will need (articles 22 and 25 pick up that thread).

The offer is not the finish line

One India-specific hazard deserves its own chart, because it ambushes every first-time builder between signature and start date:

Engagement decides who actually joins Offer-to-joining dropout by pre-joining engagement level (industry-reported ranges, mid-points) 012.52537.55035%No engagementBasic check-ins8%Designed program Indicative; compiled from public investor disclosures of listed Indian IT-services firms and industry reporting.

India’s 30–90-day notice periods create a long window in which your signed candidates keep receiving counter-offers and rival pitches; industry-reported dropout between offer and joining runs 20–40% where employers go silent. The founding cohort cannot absorb that arithmetic. The countermeasure is systematic pre-joining engagement — named buddy, manager check-ins, early equipment, team-channel access — which compresses dropout toward single digits. (The full mechanics of the notice-period dance are in article 28.)

Exhibit: a 90-day founding rhythm

Window Milestones
Days 0–30 Centre head signed; anchor searches launched; compensation bands calibrated against live market data; interview architecture and assessment stack designed
Days 31–60 Anchors onboarding; structured loops running; employer-brand basics live (careers page, leader visibility, first tech-community appearance)
Days 61–90 Proof-team offers out with engagement cadence running; first pod delivering; graduate program announced

The recurring failure modes

  1. Team before leader. Produces a cohort with no gravitational centre and a leader who inherits — rather than sets — standards. The most common sequencing error, and the least recoverable.
  2. The HQ clone spec. Requiring Silicon-Valley-shaped résumés ignores what the Indian market is uniquely good at, and screens out its best value — high-ability services alumni whose potential the market systematically mis-prices.
  3. The discount reflex. Saving 15% on anchors to lose 40% on everything downstream: slower hiring, weaker referrals, earlier attrition. The cost-per-retained-employee lens (article 4) prices this correctly.
  4. Slow yes. In hub markets, strong candidates hold multiple offers; decision loops beyond a week function as rejections you did not intend to send.
  5. Selling the job instead of the mission. “Offshore team for a foreign company” loses to “founding team of a centre with a real mandate” every time — and both descriptions can be true of the same role. Tell the true, better story.
  6. Post-offer silence. See the chart above; the market will do your un-recruiting for you, free of charge.

The compounding pay-off

Founding cohorts built this way develop a measurable signature by month twelve: referral-driven pipelines (the cheapest, best-converting source in India), interview standards that survive scale, early mandate wins from HQ, and attrition well below market. The alternative signature is equally measurable and considerably more expensive. Twenty-five decisions, made in the right order with the right rigour, are the difference — which is why the first twenty-five hires are not a staffing exercise but the founding act of the institution.

Case pattern: two founding cohorts, two years later

A composite contrast — details blended from real engagements — that operators will recognise instantly. Two companies of similar size entered India the same quarter, same city, similar mandates.

Company A ran the sequence in this playbook: a full-quarter head search closed first; anchors passed the symmetry test; the proof team skewed senior against the cost model’s protests; an in-house recruiter arrived as hire 21; offer-holders got a designed pre-joining program. Two years later: 140 people, referrals producing over a third of hires, regretted attrition in single digits, and — the metric that matters — two product mandates HQ had originally planned to keep at home.

Company B optimised for speed and cost: team hiring started before the head search (“we’ll backfill leadership”), anchors were hired at a discount, the cohort skewed junior, agencies ran everything, offers went silent until joining day. Two years later: 90 people against a 150 plan, three anchor departures re-litigated in exit interviews as “no one to learn from,” an offer-dropout rate that had become a standing agenda item, and a mandate unchanged from month one — maintenance. The company’s own post-mortem, delivered to us verbatim: “We saved four months and fifteen percent on the first ten salaries, and paid for it every month since.”

Nothing in Company B’s market was different. Every divergence traces to decisions made — or defaulted — in the first ninety days. That is the founding cohort’s leverage, stated as biography rather than framework.

Questions founders of centres ask

“Can we compress the sequence if we’re in a hurry?” You can parallelise within stages (anchor searches can overlap once the head is signed) but not across them without paying Company B’s tax. The honest acceleration levers are EOR for legal speed (article 8), a strong search partner for the head, and decision discipline — offers in days, not weeks.

“What if we already started wrong — team first, no head?” Recoverable, at a price: hire the head now, give them explicit authority to re-set standards (including undoing early mistakes), and expect a bumpy quarter. The longer the leaderless interval, the more culture there is to renegotiate.

“Senior-weighted founding teams are expensive. What’s the actual ratio?” The pattern that works: roughly half the founding 25 at senior level, inverting toward the broad-based pyramid (20/45/35) by year two as mandates stabilise and graduates arrive under mentors. The chart above carries the shape; your role mix tunes the numbers.

“Should founders relocate from HQ?” One or two HQ transplants embedded early — as bridges, not bosses — measurably accelerate trust and knowledge transfer. A centre run long-distance by HQ transplants who never localise leadership tends to cap its own ceiling; the internal-transfer archetype works best paired with a strong local deputy (see the centre-head analysis).

“How do we know the founding phase is ‘done’?” Three tests: referrals have become a top hiring source; interview standards survive without the head in the room; and HQ has voluntarily expanded the mandate. Hit all three and the institution has formed — everything after is scaling.

Cohort five: designing the first graduate intake

Hires 21–25 include your first graduates, and how that micro-cohort is designed previews the campus engine the scale phase will run (the full playbook is article 21). The founding-phase version, in miniature:

Done this way, cohort five is less a hiring event than the commissioning of a machine: the campus-to-centre pipeline that, by year three, should be supplying the broad base of the pyramid at the best economics available anywhere in the plan.

Methodology & data notes

The time-to-fill and seniority-mix charts are indicative models built from HexGn market observation and practitioner interviews; the offer-dropout ranges reflect widely reported industry experience in competitive Indian hiring segments. Selection-validity claims cite the peer-reviewed meta-analytic literature. Where a chart says “indicative,” the relationship — not the point value — is the claim.

References & further reading

HexGn runs exactly this sequence with clients — leadership search first, anchors and proof team under structured assessment, offer-to-joining engagement managed as a designed process — because the founding cohort is the strategy.

Exit mobile version