How to Negotiate Remote Salary as a Non-US Worker

A designer in São Paulo. An engineer in Bangalore. A product manager in Berlin. They're all doing the same work as their US counterparts, often in the same time zones, on the same Slack channels. Yet the offer letter says 40% less.

This is geographic arbitrage—and it's negotiable.

The problem isn't that non-US remote workers can't earn top-market rates. The problem is that most don't try. They see a number, assume it's fixed, and click accept. But companies hiring globally for remote roles aren't setting salary bands by geography out of malice—they're doing it because no one pushes back.

Here's how to change that when you negotiate remote salary as a non-US worker.

Why Geography Shouldn't Be Your Ceiling

Remote work flipped the script on location-based pay. When you're working asynchronously from Lisbon for a San Francisco startup, your ZIP code stops mattering. Your output does.

Yet many companies still anchor salaries to local market rates. A senior engineer in Istanbul gets offered $90k. The same engineer applying from California gets $150k. The work is identical. The time zone might even be better.

The reason this gap exists:

Legacy thinking. Companies inherited location-based pay from the office era and haven't updated it for remote-first hiring.
Passive acceptance. Most candidates from lower-cost countries don't negotiate. Companies learn they don't have to pay more.
Misplaced equity concerns. Some hiring managers worry it's "unfair" to pay everyone the same. (Spoiler: it's not unfair—it's fair.)
Assuming currency differences cushion the blow. They don't. A $90k salary in Brazil is not equivalent to $90k in the US when you account for USD strength and local purchasing power.

Here's the truth: if a company is willing to hire you remotely, they've decided they don't need you in an office. That decision means your location is irrelevant to your value. Use that in your negotiation.

Research Your Actual Market Rate

Before you negotiate remote salary, you need a number that's defensible.

Don't use local salary data. That's playing into their game. Use US market rates for the same role, because you're doing the same work.

Where to find this:

Blind salary database. Search by role, company, and level. Real salaries posted anonymously by engineers at FAANG and growth startups.
Levels.fyi. Cross-reference salary by title, company, and years of experience. Broken down by base, stock, and bonus.
PayScale, Glassdoor, LinkedIn Salary. Higher variance, but broad coverage. Filter by seniority and company size.
Angel list, RemoteOK. Actual job postings from remote-first companies—good for seeing what similar remote roles actually pay.

For a mid-level full-stack engineer at a Series B startup: expect $140k–$180k base in the US market. Not $90k.

For a senior product designer at a established SaaS company: expect $130k–$170k base. Not $80k.

Once you have that range, anchor your negotiation 10–15% above the midpoint. So if the market range is $140k–$180k, you're asking for $165k–$170k.

The Psychology of Anchoring

The first number matters. A lot.

When you propose a salary in your negotiation of remote salary as a non-US worker, you're setting the frame. Companies will negotiate down from your anchor—not up from theirs.

If they offer $90k and you counter with $95k, they hear "she's okay with ~$90k." If you counter with $165k, they hear "oh, this candidate thinks they're worth premium rates."

They might land at $140k instead of $165k. You've still won.

Never counter with a number pulled from thin air. Say: "Based on market data from Levels.fyi and Blind for this role and level, the US market range is $140k–$180k. Given my experience with [specific accomplishment], I'm targeting $165k."

That's not aggressive. That's informed. And it works.

Scripts for the Conversation

When they ask "What are your salary expectations?"

Script 1: Deflect and Redirect

"I'm open to discussing comp once we've confirmed mutual fit. What range does your role typically target for this seniority level?"

Get them to anchor first. If they name a number that's too low, you have room to push back. If it's in your range, you've learned something valuable.

Script 2: Name Your Number with Justification

"Based on market data for remote senior engineers at [Series B/growth-stage companies], the range I'm seeing is $155k–$185k base. Given my background in [microservices/team leadership/scaling], I'm targeting $170k. What works for your budget?"

Specific. Sourced. Confident.

Script 3: Handle the Geography Push-Back

They say: "We'd love to offer $120k, but that's significantly above market for [your country]."

You respond: "I appreciate that. I'm not anchoring to [country] market rates because I'm working remotely for a US-based company on a distributed team. My comp should reflect the US market for this role and level, not the cost of living here. Especially since time zones actually work in your favor—I can overlap with your west-coast team asynchronously."

Or, if they're being rigid: "I understand your concern about internal equity. Let's talk about how we structure this—is there room in the budget, or would a signing bonus / additional equity help bridge the gap?"

Script 4: The Strong Close

"I'm excited about [specific project/mission/company]. I know remote hiring has given you flexibility on location. I'd like to bring the same flexibility to our compensation discussion. Can we meet at $165k base plus [equity, bonus structure]?"

You're not begging. You're proposing a clean, fair number.

Negotiation Tactics That Work

Get competing offers. Or at least set them in motion. If you have another offer pending, mention it: "I have another offer on the table at $155k. I'd prefer to work with you—can we close the gap?"

Don't lie. But do show urgency.

Negotiate the full package. Salary is one lever. So is:

Signing bonus. $10k–$30k upfront offsets any currency or relocation stuff.
Stock options. Especially valuable at growth-stage / pre-IPO companies. Ask for vesting details.
Flexible hours. If they won't move on base, ask for comp time or asynchronous requirements.
PTO. US companies often have less generous leave. Negotiate for 25–30 days.
Professional development budget. $1k–$3k per year adds up.

Compress the timeline. "I need to make a decision by Friday." Urgency closes gaps.

Know when to walk. If they won't budge above $110k and you know the market is $150k+, there's a deeper issue. They either don't value you or don't have the budget. Either way, your time is worth more elsewhere. We track salary transparency on our job board—you can see what other companies are actually offering for your role.

The Currency and Tax Layer

One more thing: currency matters.

If you're in Brazil and they offer $100k USD annually, that's approximately 500k BRL at today's rates. That sounds huge—but $100k USD is also about 25% below market for your role.

Instead, negotiate for the fair USD rate upfront. Once you have $160k USD locked in, you can deal with how it gets paid (wire transfer, crypto, local currency at spot rate, etc.).

Some companies will offer to pay in your local currency. That's fine—but lock the USD amount first, then calculate local currency. Don't let them anchor to local market rates.

Also: if you're an independent contractor (1099, not W2), you're covering your own taxes and benefits. That's typically 25–35% on top of salary. Negotiate accordingly. A $100k contract role isn't equivalent to a $100k salary.

After You Negotiate Remote Salary

Once you've landed the offer, get it in writing. Every detail:

Base salary in USD (or specify currency with exchange rate)
Signing bonus (if applicable)
Stock or options (if applicable)
Vesting schedule
Equity cliff
Bonus structure and conditions
Start date

A conversation is not an agreement. An email is better. A contract is best.

If you're signing on with a startup, especially, make sure the founder or hiring manager confirms in writing. Verbal promises evaporate.

You Have More Leverage Than You Think

The fact that a company is hiring remotely globally tells you something: they believe geography doesn't matter. They've already decided they don't need you in an office. They've already made the bet that distributed teams work.

They've done 80% of the mental work for you.

Your job is to finish it: to make clear that if geography doesn't matter for the work, it shouldn't matter for the salary either.

You're not asking for a handout. You're asking to be paid fairly for the labor you're trading. That's not negotiation—that's just math.

If you're hunting for remote roles that pay in USD and value distributed teams, set up salary alerts on WeHireAnywhere to track what companies are actually offering. You'll get a clearer picture of market rates, and you'll see which companies list salary upfront (good sign) versus hide it (red flag). When it's time to negotiate, you'll walk in knowing your worth.