Hiring in Nepal vs India vs US: NPR/INR/USD Pay Parity (2026)

60-Second Summary

There are three coherent comp models for cross-border hiring: 'pay-everyone-the-same' (rare, expensive, philosophically pure), 'cost-of-labor' (pay each location's market rate — most common), 'cost-of-living' (adjust to local purchasing power — controversial). Pick one and document it.
For most VC-backed startups hiring Nepal/India engineers alongside US engineers, cost-of-labor at the 60–75th percentile of the local market is the workable answer. Pay below that loses talent; pay above creates retention dependence and salary-band distortion.
Equity parity (same RSU/option grant size for the same level regardless of location) is the modern norm and the right answer — it signals 'same role, same upside' even when cash differs.
The hardest conversation is internal: explaining to a Bay Area engineer why a Kathmandu engineer at the same level is paid 1/4 the cash but the same equity. Skip this conversation and you build hidden resentment that surfaces in retention data 18 months later.

When a single company hires a senior engineer in San Francisco at $280k base, in Bangalore at INR 50 lakh (~$60k), and in Kathmandu at NPR 25 lakh (~$19k), someone — usually you — has to explain why. The math has to be internally consistent, externally competitive, and culturally defensible across three countries that read the world very differently. This article is the playbook.

The three coherent comp models

Model	Cash comp	Equity comp	Used by	Tradeoff
Pay everyone the same (global)	Single global band; same number regardless of location	Same	37signals (historically), GitLab partial	Philosophically pure; financially expensive; underpays competitive markets like SF, overpays low-cost markets
Cost-of-labor (local market)	Each location's percentile of its market	Same or tiered	Most VC-backed startups, Stripe, Datadog	Market-competitive everywhere; large cash gaps require communication
Cost-of-living adjusted	Indexed to a baseline (often SF) by COL ratio	Same	Google internal, Meta	Most operationally rational; feels punitive when employees move to low-cost locations

Cost-of-labor: how to actually price each market

Cost-of-labor pricing is the dominant model. The implementation question is: at what percentile of which competitive set in each market?

Building a cost-of-labor band for each market

1
1. Define the competitive set per market
Bay Area: VC-backed Series B+ tech companies. Bangalore: India-based and India-arm of MNCs (Flipkart, Razorpay, Stripe India, Atlassian India). Kathmandu: top tier including Leapfrog, Cotiviti Nepal, Cedar Gate, F1Soft, regional remote-first employers paying international rates.
2
2. Choose target percentile per market
Most startups target 60–75th percentile of their competitive set. Don't pay 50th — you lose to competitors. Don't pay 90th — you build retention dependence on comp.
3
3. Pull data sources per market
Bay Area: Levels.fyi, Pave, Radford Tech. India: AON India, Mercer Tech India, Glassdoor India, Levels.fyi (India coverage). Nepal: harder — primary research via recruiter conversations, salary surveys from Verisk/Nepali HR consultancies, public Glassdoor data (sparse). Pad the Nepal number for sparse data by talking to 5+ peer companies.
4
4. Set bands per location, per level
Senior engineer L5 might be: SF $280k–$340k base, Bangalore INR 45–60 lakh base, Kathmandu NPR 22–35 lakh base. Each band 80%–120% of midpoint width.
5
5. Document and update annually
Per-market re-banding annually. Don't do it 'when someone complains' — that's a politics-driven comp system.

The cost-of-living adjustment question

Cost-of-living-adjusted (COLA) comp asks: 'if I'm paid $280k in SF, what does my dollar-equivalent need to be in Bangalore to maintain my standard of living?' Numbeo, Mercer, Expatistan publish ratios. SF ↔ Bangalore is roughly 4–5x. SF ↔ Kathmandu is roughly 5–7x. By that math, $280k SF = ~$56k Bangalore = ~$45k Kathmandu — which roughly matches what cost-of-labor pricing produces anyway.

Where COLA models break: when a Bangalore engineer moves to a smaller Indian city, COLA pure-play would cut their comp. This feels punitive and is politically toxic. The compromise most companies adopt: cost-of-labor as the primary lens, with a 'no comp cut for relocation within the same country' rule.

Equity parity (and why it matters)

The single highest-leverage move in cross-border comp is making equity parity-based: the same grant size for the same level regardless of location. A senior engineer L5 in SF and in Kathmandu both get the same number of RSUs or options, vesting on the same schedule, with the same strike price.

Why this matters: equity signals 'we believe you are equally valuable to this company's outcome.' Cash compensation reflects market rates; equity reflects role. When equity is also discounted by location, the message becomes 'you are a cheaper resource' rather than 'you are part of the same enterprise.' That signal is read clearly by your South Asian engineers, and it shapes retention.

Even when cash differs 4x, equity should match

A Kathmandu engineer earning NPR 30 lakh base + 1,500 RSUs is paid very differently from an SF engineer earning $280k base + 1,500 RSUs. The cash math reflects market. The equity math reflects shared outcome. Both can be true simultaneously, and the equity parity is what makes the cash gap defensible.

The comp philosophy document

Every company hiring across borders needs a 2–3 page Compensation Philosophy document. It does three things: (1) anchors decisions, (2) survives founder turnover, (3) gives HR a defensible answer in every comp negotiation.

Comp philosophy doc — the 5 sections

1
1. Our compensation model
We pay cost-of-labor at the 65th percentile of the local tech-startup market, with equity grants set globally by role/level. Why we chose this.
2
2. Our markets and tiers
Tier 1: SF Bay, NYC. Tier 2: Boston, Seattle, Austin, London. Tier 3: Bangalore, Mumbai, Kathmandu. Tier 4: rest-of-India, rest-of-Nepal, smaller US metros. The number of tiers and what each contains.
3
3. Equity philosophy
Equity granted by role and level, not by location. Refresh policy. Vesting schedule. Acceleration on change-of-control. Tax-equalization (if any).
4
4. Adjustments and exceptions
Off-band offers require Head of People approval. Counter-offers honored only in specific conditions. Relocation does/doesn't trigger comp adjustment.
5
5. Transparency posture
Bands published internally? Externally? Pay-equity audit cadence.

The conversations HR has to lead

With the Bay Area engineer asking why their Bangalore peer earns 'less': market-rate explanation + equity parity emphasis. Avoid moralizing in either direction.
With the Bangalore engineer asking why their SF peer earns 'more': cost-of-labor reality + equity parity + transparent band publication. Acknowledge the gap; don't pretend it isn't real.
With the founder/CEO asking 'why don't we just pay everyone the SF rate': the math (5x cost, no retention benefit at the top of the local market, internal team dynamics that emerge).
With the new manager asking 'can I offer my candidate above-band': process for off-band approval; data on consequences of band drift.
With the candidate negotiating from a higher offer: how to honor real market signals without breaking the band, and when to walk away.

Common mistakes

Mistake	What goes wrong	Fix
No published philosophy	Every comp decision feels arbitrary; high-trust hires lose faith	Write the philosophy doc; publish internally
Equity tiered by location	Sends 'second-class employee' signal	Equity parity by level
Bay Area band copy-pasted to other markets	Either overpays massively or underpays catastrophically — both happen	Per-market band-building
Comp cuts for relocation within same country	Politically toxic; retention damage	Country-level cap on downward adjustment
Annual band updates only when someone complains	Reactive comp = unfair comp	Calendarized annual review
Pretending the gap doesn't exist	Builds resentment that surfaces 18 months later in attrition data	Lead the conversation; transparency wins

FAQ

Frequently asked questions

What if a Nepalese engineer relocates to the US for our SF office?

Most companies adjust to local cost-of-labor on confirmed permanent relocation. Some offer a 12–24 month transition rate to ease the change. Document the policy before it comes up.

How do we handle full-time-equivalent vs contractor hires across borders?

Contractors are easier (no employment tax exposure), riskier (misclassification), and culturally signal lower commitment. For roles you want long-term, prefer FTE via local entity or Employer of Record. See the dedicated articles on Nepal/India/SA compliance.

Should we publish comp bands externally?

Trend is toward yes. EU Pay Transparency Directive (effective June 2026) requires it for EU jurisdictions. Several US states require it for postings. Get ahead of it.

What about US engineers wanting to move to lower-cost locations?

Two-track policy: in-country moves don't adjust comp; international moves trigger local-market re-banding. Document carefully — this is the most common live HR conversation in distributed startups.

From the Insights desk

Longer-form essays that extend the ideas in this playbook with research, data, and 2026 context.

Written by Pawan Joshi.Sources cited inline.

First published 15 Jun 2026See site changelog →

Hiring across NPR / INR / USD: pay parity without the resentment