.png)
How Should US Firms Prepare for Pay Transparency When Hiring in India?
Eighteen US states plus Washington, D.C. now require salary range disclosure in job postings, and more states are joining the list every quarter. India added its own version of this pressure when the Code on Wages folded the old Equal Remuneration Act into a single statute with a clear gender pay parity clause.
Put those two facts together and you get the real question HR teams are asking us: how should US firms prepare for pay transparency when hiring in India, when neither country's law fully covers the other side of the hire? We've watched this gap catch out clients who assumed their India hires sat outside every disclosure rule, only to get asked during their own pay equity audit why the India band looked nothing like the US band for the same role.
Why This Is Suddenly an HR Problem, Not Just a Legal Footnote
Hiring has shifted fast in the last stretch. AI powered screening tools are now standard in most US recruiting stacks, which means job descriptions and salary data move faster between markets than they used to, and a mismatched India band gets noticed sooner rather than later.
Global Capability Centers (GCC) are opening at a pace we haven't seen before, with cloud, data, and platform engineering roles leading the demand curve out of India. At the same time, remote and hybrid work has blurred the line between "a US role" and "an India role" inside the same org chart, so a manager based in Austin can now sit directly above an engineer in Pune and see both salary structures side by side.
This is exactly why pay transparency has stopped being a US only conversation. Most state disclosure laws are written around where a job could be performed, so a posting for an India based role usually falls outside California, Colorado, or New York's direct requirement. That is the legally correct read, and it is also the trap. Teams read "not covered" as "no documentation needed," and that is where the exposure actually starts once US and India teams sit under one comp philosophy.
Where US Firms Find Compliant Talent in India
Bengaluru and Pune carry the deepest bench of India based People Ops and Total Rewards professionals who have already worked inside a global capability center or an MNC captive. They know how to build a band against a US style leveling framework because they have done it before. Hyderabad runs close behind for HR tech and fintech adjacent comp talent, and Delhi NCR and Chennai are strong for generalist HR leadership who can own the compliance paperwork end to end.
What Indian recruiting talent typically brings: fluency with statutory pay components like basic, HRA, PF, and gratuity, and a working knowledge of the old equal remuneration framework most professionals trained under. What they often lack walking into a US led mandate is direct exposure to state level pay transparency mechanics, since publishing a good faith salary range is still a newer discipline in India than it is in the US. We test for this directly in screening by asking candidates to walk through how they would document a range that a US regulator might eventually review, not just how they would set the number.
This is also where the choice between contract hiring and full time hiring starts to matter. Contract hiring through a staffing partner gets you speed and flexibility, and it works well for time boxed projects or roles you are still validating. Full time hiring, usually through an entity or an EOR, gives you a stable long term team and simpler equity treatment, but it puts the pay documentation responsibility more directly on you.
How US Firms Prepare for Pay Transparency When Hiring in India
The law to know by name is the Code on Wages, which consolidates the Payment of Wages Act, the Minimum Wages Act, the Payment of Bonus Act, and the Equal Remuneration Act into one framework. It came into force nationally, though individual states are still finishing their own rules on different timelines, and its gender pay parity clause applies to every establishment regardless of size or sector. It does not require salary range disclosure in job postings the way Colorado or California do. It requires equal pay for the same or similar work, which is a related but separate obligation.
For a US firm, what this means depends on how the role is structured. Contract hiring through an Indian staffing partner puts the direct compliance obligation on the partner, but the US company still carries reputational and contractual risk if a wage complaint surfaces. Hiring through an Employer of Record (EOR) shifts the legal employer role to the EOR, though the pay bands themselves are almost always set by the US company, so the real exposure still traces back to you. Full time hiring through your own India entity puts complete exposure on your books, including direct exposure to a labour inspection.
The mistake we see most often is treating this as a payroll structuring issue only, worrying about wage definitions and statutory contributions while missing the gender pay parity question sitting in the same law. Those are two separate compliance checks, and both belong in the same review before a role goes live.
If you want a second set of eyes on how your current India bands would hold up, our team at AnjuSmriti Global can walk through it with you directly.
Pay Transparency Readiness Checklist for Hiring in India
Before you open a requisition for an India based role, whether contract or full time, you should be able to check off every line here.
Checklist item | Why it matters |
One documented band methodology for both US and India roles | Defends against a pay equity audit that compares global bands |
Written reason for any gap between comparable US and India bands | Regulators and internal stakeholders will ask for this eventually |
Gender pay parity self check against the Code on Wages standard | A direct statutory requirement inside India |
Clear record of how the India range was benchmarked, and when | Needed if a labour inspection or internal review asks for the basis |
Clarity on which entity is the legal employer of record | Determines who carries compliance liability |
A plan for how blended US India teams see and understand pay data | Prevents the "why is my range undocumented" complaint |
A refresh cadence for India bands, ideally twice a year | India tech pay moves faster than most annual review cycles assume |
None of this shows up automatically in an applicant tracking system. It has to be built into how a mandate starts, not patched in after a hire goes live.
Our Process, and Where This Nearly Went Wrong
For every new client scaling India hiring, we run compensation benchmarking before sourcing starts, not after. That means roughly two weeks upfront pulling India market data for the specific role and city, mapped against the client's existing US leveling framework, before a single candidate is contacted. Sourcing for a mid to senior technical or operations role then runs three to four weeks, and HR or People Ops leadership searches usually take closer to six given the smaller qualified pool.
Here is a scenario worth sharing. A US based fintech company, roughly 300 employees, was already fully compliant on every US posting with documented, board reviewed ranges. They opened a small capability center in Hyderabad through an EOR and set India bands off a single competitor's public job posting, with no written methodology behind the numbers. Several months in, a US based director relocated to manage the Hyderabad team directly, compared both sets of bands during a routine leveling exercise, and escalated to HR because the gap had no documentation behind it at all. That escalation landed weeks before the company's annual pay equity audit.
We ran an emergency benchmarking pass across every India role, rebuilt the bands against the same framework the US team used, and produced a written methodology tying each range back to a dated source. The audit closed clean, and the client now refreshes India bands twice a year as a standing part of the engagement.
What Hiring in India Actually Costs
Figures below are approximate monthly CTC in INR for a mid size India tech hub, contract basis.
Level | Monthly CTC (INR) | Roughly vs. Comparable US Salary |
Mid, 3 to 5 years | Rs 1,40,000 to Rs 1,90,000 | About one third |
Senior, 6 to 9 years | Rs 2,20,000 to Rs 3,10,000 | About 35 to 40 percent |
Lead or Principal, 10+ years | Rs 3,40,000 to Rs 4,80,000 | About 40 to 45 percent |
On top of the base figure, plan for statutory employer contributions of roughly 12 to 15 percent, an EOR management fee if you are not running your own entity, and a placement fee structured per mandate. Clients who put real rigor into their India bands, matching what state law already forces on their US postings, tend to reinvest the savings into a second hiring wave rather than a single flagship role, because the documentation groundwork is already built.
Conclusion
More US states will keep adding disclosure requirements, and remote hiring ambiguity will keep pushing companies toward one global documentation standard instead of two separate rulebooks. On the India side, state level rules under the Code on Wages are still finishing their rollout, and gender pay parity enforcement will get sharper as that happens. In live mandates right now, US clients are asking for documented India bands as a default request, not an add on, which is a real shift from where this conversation was even a year ago.
If your India hiring plan needs compensation documentation built to survive a US audit from day one, start that conversation with our team.
Interesting Reads:
FAQs
1.Does India's gender pay parity law apply to contractors hired through an EOR?
Yes, in substance. The EOR is the legal employer, but the pay bands are almost always set by the US company. If the bands you set create a gender based gap for the same role, the EOR cannot fix a number it did not originate. The compliance responsibility for the actual pay decision still sits with you.
2.Do California or Colorado pay transparency laws apply to job postings for India based roles?
Generally no, since these laws apply to jobs performable within that state. A posting for an India based role usually falls outside the direct requirement. The real risk is internal inconsistency once US and India bands for similar roles get compared during an audit or an internal transfer.
3.If we already publish US salary ranges, are we required to publish India ranges too?
No, this isn't a legal requirement in either country today. But once a documented methodology exists for US roles, an auditor or internal stakeholder will often expect the same rigor for India roles, especially once teams work together directly across both markets.
4.How should we handle pay equity on a blended US India team?
Build both sets of bands on the same leveling framework so any gap has a clear, documented explanation such as cost of living or market source. Teams generally accept a documented gap. What creates complaints is an undocumented one, especially once a manager can see both sides directly.
5.Should we choose contract hiring or full time hiring for our first India roles?
Contract hiring gives you speed and flexibility for validating a role or a market, while full time hiring gives you stability and simpler long term equity treatment. Most companies start with contract roles for the first few hires, then convert strong performers once the team's shape is proven.
6.What happens if we post an India role without a salary range?
Direct legal exposure is low today since neither country mandates range disclosure for India postings specifically. The bigger risk is reputational, since candidates increasingly expect ranges, and skipping one on an India posting while including one on a US posting reads as inconsistent.
7.How often should India salary bands be refreshed?
We recommend twice a year. India tech compensation moves faster than most annual US benchmarking cycles account for, and a stale band is one of the fastest ways to lose a strong candidate mid process or create an unexplained internal gap later.
8.What documentation should HR keep to defend India bands during a US audit?
Keep the benchmarking source and date for each band, the leveling framework mapping India levels to US equivalents, a written reason for any gap between comparable ranges, and a log showing bands are reviewed on a set schedule rather than set once and left alone.
Comments