A Director in the US and a Director in your India GCC aren't the same hire

When a US parent opens a senior role in its India centre, the level usually arrives pre-decided. Somebody maps the role against the headquarters org chart, finds the nearest equivalent, and the requisition goes out as a Director, because that's what the reporting line implies. It's an efficient way to start a search and a reliable way to mis-set one.

A title is the most portable thing in a job description and the least informative. It moves intact through the requisition, the approval chain and the offer letter, carrying an implied seniority that was calibrated in an entirely different labour market. What doesn't move with it is everything that gave the level meaning at headquarters: the size of the function, the decisions the seat actually owns, the peer group the person will sit among, the alternatives that peer group has.

So the brief goes to market describing a level, and the market answers with people. The two don't line up, and the reasons take weeks to surface, because everyone in the room is using the same word to mean different things. The disagreement feels like a disagreement about candidate quality. It's really a disagreement about what the word means.

The clearest divergence is span. A GCC that's taken on the delivery weight of a function whose strategy still sits at headquarters will often run large teams under modest titles. The India Director in that structure can carry an organisation several times the size of their nominal US counterpart, because the centre absorbed the headcount while the roadmap stayed elsewhere. Read against the headquarters meaning of the title, that person looks over-titled. Read against the work, they're running a bigger operation than the person they report to.

It runs the other way just as often. A US Director who owns a product line, a budget and a roadmap has decision rights that an India Director executing against someone else's roadmap simply doesn't have, however many people report to them. Bigger team, narrower mandate. When a committee at headquarters interviews that candidate against their own idea of what a Director decides, the candidate reads as junior, though the seat never held the authority the question was about.

Neither structure is wrong. Both are rational answers to how the centre was chartered. But a hiring committee reading candidates against the headquarters meaning of a level will misjudge in a consistent direction, and the misjudgement compounds. The shortlist narrows around people whose last title matched, rather than people whose last set of decisions matched.

The second thing that fails to cross is the set of instincts a committee has built up about what a CV should look like. Movement every 3 years reads as restlessness in a market where 7-year tenures are normal, and reads as ordinary in a segment that repriced fast enough to make staying put expensive. The same pattern, the same CV, 2 opposite conclusions depending on which market's norms the reader is carrying.

Company prestige translates badly too. A committee scanning for familiar logos will over-weight the multinationals it already knows and skip the India-headquartered firms and the centres that did the most interesting work, because the names carry no signal at headquarters. The effect is to filter for visibility rather than capability, which is the failure mode of every proxy: it selects for who's easy to read.

None of this asks the committee to lower a standard. It asks them to notice which of their standards are actually standards and which are habits formed in one labour market and applied, without examination, in another. The useful question in the room is simple. Is this a judgement about the work, or about the shape of a career in a market I happen to know well?

Once the level is set from the org chart, the loop is built to match it, and the loop is where the mismatch gets expensive. A panel assembled for a headquarters Director will probe strategy formation, executive influence, and the framing of a roadmap. Reasonable things to ask a person who'll own those. If the India seat executes against a roadmap headquarters owns, the strongest candidates will answer those questions thinly, because they've spent their careers doing something adjacent and harder to talk about.

Meanwhile the questions that would actually discriminate go unasked. How do you hold delivery quality across an organisation you scaled faster than you could hire? How do you carry a decision you disagreed with to a team that can tell you disagreed with it? How do you run a function whose customer is 11 and a half hours away and only overlaps with you for 2 of them? Those are the parts of the job the seat really turns on, and they rarely appear on a loop designed elsewhere.

The result is a loop that's rigorous about the wrong thing. It rejects capable people confidently, which is the most dangerous kind of rejection, because it leaves everyone more certain the market is thin. The pipeline wasn't thin. The questions were pointed at a job that exists on a different continent.

The repair is unglamorous and takes about an hour. Instead of opening with the level, write down the decisions the seat will own, the decisions it will influence, and the decisions that'll be made without it. Three lists, plainly worded, no titles anywhere. Nearly every cross-border misalignment we see surfaces in that exercise, because two people who agreed instantly on “Director” will disagree immediately about whether this person sets the hiring plan or executes it.

Those lists do work the title can't. They tell you which candidates have genuinely held the seat, which are stepping up and by how far, and what the role is worth to somebody currently sitting one rung away. They also give the interview loop something real to assess, because a decision is a thing a candidate can be asked to walk you through in detail, and detail is where capability stops being a claim.

And they travel. A US stakeholder and an India stakeholder can look at the same 3 lists and find the same disagreement in the same place, which isn't true of a level. That's the whole point. You want the argument on day 1, in a room, over a document, while it's still an argument about a document and not about a candidate who was never the problem.

Once the decisions are agreed, the title becomes a much smaller question, and it should be answered by the market the person will be recruited from, not the chart they'll appear on. If the seat competes against roles the India market calls Senior Director, calling it Director to keep the org chart tidy will cost you candidates who never opened the message. The reverse is equally true: inflating a title to attract interest buys you a stronger response rate and a harder second year, when the person discovers the authority didn't come with the label.

Internal consistency is a real constraint, and pretending otherwise doesn't help. But it's a constraint to trade against deliberately, with somebody naming the cost, rather than settle silently by whoever drew the reporting line. In practice the trade is usually available. The level stays where governance needs it, and the scope, the band or the mandate moves to make the seat genuinely competitive.

What doesn't work is holding the headquarters title, the headquarters scope assumptions and the headquarters interview loop, then concluding senior talent in India is scarce. The talent is there. It's being assessed against a job description that describes a role in another country, and rejected for failing to be something it was never asked to be.