Managing Global HR From India: Lessons From the Frontline

Summary:

• India’s regulatory complexity is real, but India-based HR teams need to make the market feel navigable to global stakeholders rather than reinforce the perception of difficulty.
• India’s talent pool spans creative, technical and service disciplines; companies that come only for a one-year cost saving optimise for the wrong thing.
• Stakeholder management and structured cultural assimilation matter more than technical HR skill for global teams run from India.
• An internal HR chatbot cut repeat questions by 60% and resolved 85% of issues before they reached a ticket.

TopSource’s own history straddles two worlds. It’s a UK founded business that built its real operational depth in India from around 2010 onward. That dual identity raises a question worth asking any HR leader running global teams from an Indian base: what does it actually take to make that work well?

The following draws on a recent conversation between Aparna Singh, Head of Global HR at TopSource, and Kaushiki Srivastava, HR Director at Ubisoft.

Asked what international colleagues most often get wrong about employing and managing teams in India, the answer wasn’t really about mistakes. It was about intimidation. India’s regulatory environment is dense, and that complexity is often the first barrier global counterparts run into when they start thinking seriously about setting up here.

There’s a harder truth worth sitting with too. Indian HR teams sometimes contribute to that perception simply through how they communicate the rules internally. HR functions based in India need to work at making the market feel navigable to global stakeholders, rather than reinforcing the idea that doing business here requires a translator on every call.

There’s a financial dimension to this as well. New gratuity provisioning requirements under the labour code create a sudden, visible jump in the numbers global finance teams see. That conversation, weighing the cost of compliance against the cost of non-compliance, needs to be had honestly, not treated as some quirk of doing business in India specifically.

Perhaps the sharpest point raised was about how India’s talent pool tends to get perceived internationally. It’s often reduced to technical talent, shared services, or a cheap delivery hub. The counter to that is straightforward. India is enormously diverse, with all five working generations active in the labour market at once, and talent spanning creative, technical and service disciplines. Gaming is a good example. There are roughly 300 competitors in the Indian gaming market, and only four of them are international.

The framing here was pragmatic rather than defensive. Cost efficiency is a genuine advantage, but it shouldn’t define the value proposition on its own. Companies that come to India purely chasing a one year cost saving are optimising for the wrong thing. The real value shows up over a longer horizon, once volume and quality start to compound. Spotify and Netflix are both useful illustrations here. Neither found real traction in India until they properly studied the market, rather than assuming a global playbook would simply transfer.

One practical piece of advice for any global organisation scaling its India presence: commission a proper market study covering talent insights and total rewards benchmarking, specific to India, rather than relying on standard global compensation surveys. Those tend to bucket India specific roles into a generic miscellaneous category that misses how the market actually works.

Managing HR for teams outside India, while sitting in India, means constantly resetting your default assumptions. Maternity benefits, reasonable accommodation laws and elder care norms all vary sharply by country and culture. A policy that acts as a real employer differentiator in India might simply be standard practice, and therefore no differentiator at all, somewhere like Singapore.

Two capabilities came up repeatedly as essential for any global HR team based in India.

The first is stakeholder management, treated here as more foundational than technical HR skill. Teams working across borders need a shared language around what a deadline actually means, what an escalation looks like, and what quality means in practice. Without that shared understanding, ordinary friction gets misread as a personality clash or a capability gap, when it’s really just a communication gap.

The second is structured cultural assimilation, built into how new teams and projects kick off and revisited periodically rather than treated as a one off onboarding exercise. External cross cultural training tools can help here, but the underlying point is that most of these tensions have very little to do with actual workload. They’re about mismatched expectations on tone, pace and tolerance for friction.

On AI’s role in global HR operations, the conversation stayed away from the flashier use cases and focused instead on practical relief. One example shared was an internally built chatbot, deployed through Teams, aimed at deflecting repetitive employee queries. Over eighteen months it produced a 60% reduction in repeat questions and resolved 85% of issues before they ever reached a formal ticketing system.

The point isn’t that AI replaces HR judgment. Recruitment screening and even interviewing are becoming contested ground, with candidates using AI just as readily as recruiters do, and face to face interviews holding their value precisely because they’re harder to game. The more durable use case is freeing HR teams from repetitive transactional work so they can spend time on things that actually need judgment, such as auditing whether policies are still current, rather than only ever answering leave balance queries. The caveat attached was clear. AI is useful as a support for synthesis and communication, but data handling matters. Using unauthorised or unvetted tools risks real data exposure, and content that obviously reads as AI generated undermines the exact communication problem it was meant to solve.

Strip away the specifics and what’s actually being asked of HR leaders here is fluency in two directions at once: fluent enough in India’s complexity to manage it without exporting that complexity outward, and fluent enough in a dozen other markets’ norms to stop assuming India’s defaults apply everywhere else. That’s a harder job than either “run India” or “run global” on its own, and it’s a fair description of what the role has quietly become.