How do I research salary ranges for remote tech roles?

Check sites like Glassdoor, Levels.fyi, RemoteOK, and Stack Overflow for current salary data. Focus on remote roles hiring from your region, and ask peers about their real offers.

What if I don't want to answer the salary question right away?

You can politely say you’d like to learn more about the role or total compensation before giving a range, but be prepared to share a researched number if the recruiter insists.

How do I handle salary questions if my local pay is much lower?

Be clear that your past local salary reflected that market, but global remote roles pay differently. Present your new research-based range confidently as your expectation.

What’s the risk of giving too low or too high a salary number?

Going too low leaves money on the table or makes you look inexperienced. Going too high could price you out. A realistic range based on market data keeps negotiations fair.

How to Answer the 'What Are Your Salary Expectations?' Question

Facing the Salary Expectation Question? Here’s How to Nail It

Few interview moments trip up candidates—especially LATAM tech professionals targeting remote, dollar-based jobs—like being asked, "What are your salary expectations?" You don’t want to price yourself out, but you also don’t want to leave money on the table or seem underprepared. Let’s break down how to handle this minefield with confidence and precision.

Why This Question Matters So Much

For remote, international tech roles, salary can vary wildly. Companies want to know:

Can they afford you?
Are you informed about your own market value?
Will money be an issue later?

Your response is an early negotiation anchor—answering poorly can cost you thousands, or even the job.

Prepare With Real Market Data—Not Just Guesses

Don’t wing it or base your range on local LATAM salaries alone. To quote competitive numbers:

Use sites like Levels.fyi, Glassdoor, and RemoteOK to track remote USD rates for your tech stack and experience level.
Tap into tech salary reports like Stack Overflow’s annual survey or GitHub’s developer reports.
Ask peers in your network what ranges clients or companies are offering for similar roles.

Tip: Focus on ranges published by companies *hiring in your region* for remote roles, not just US-based in-office salaries.

How to Define (and Justify) Your Range

Set a realistic range, not a single number. For example, if market data shows remote React engineers with 3+ years earn $40k-$60k USD, your range might be $45k-$55k.

When the question comes up:

Give a range, not an exact number.
Briefly mention it’s based on your research, skills, and market rates.
Signal flexibility if the role excites you.

Phrase it like this:

> "Based on my research and experience level, I’m targeting between $45,000 and $55,000 USD for a role like this. I’m open to discussing total compensation and benefits as well."

What to Say if You’re Pushed for a Number Early

Many recruiters open with salary questions. If you’re too early in the process to know what the job really entails, try to delay:

"I’d appreciate learning more about the role’s responsibilities and your overall compensation package before sharing a range. Could you tell me more about budget for this position?"
If pressed again, share your researched range (never "I’m flexible" alone—that sounds unprepared).

If the Recruiter Insists on Your Old (Local) Salary

Some US or EU companies ask about your past compensation. In LATAM, this can be *much* lower than what the global market pays. Don’t let this anchor your offer.

Politely explain that your past salary was based on local market conditions, but your research shows higher rates for remote, international roles.
Reiterate your range with confidence.

Example response:

> "My previous role compensated me according to local market standards, but for remote positions with global companies, I’ve found that $X–$Y is competitive with what other professionals in similar roles are earning."

A Real Example from a LATAM Dev (What Actually Works)

Ana, a React developer from Argentina, faced this question interviewing with a US-based SaaS company. She researched market rates on Levels.fyi, saw that LATAM devs were landing $42k-$50k USD for similar roles, and prepared her answer. When the recruiter asked, Ana replied:

> "Based on current remote market rates for React developers—with my years of experience—I’m looking for something in the $45,000 to $50,000 USD range. I’m flexible depending on the full package and professional growth opportunities."

She was later told her number fit the company's budget and was brought into final interviews. Prep, clarity, and grounding in real data works.

Quick Tips for Salary Negotiation Success

Never be the first to name a number if you can help it, but don’t refuse to answer outright.
Avoid "whatever you think is fair"—that signals lack of confidence or preparation.
Practice out loud. Nervous? Try scripting your answer in English and Spanish.
Consider the whole package: USD payments, benefits, bonuses, time-off policies.
Double check tax/contractor implications—know what amount ends up in your pocket.

Watch Out for Lowballing and How to Respond

If their offer is below your range, don’t panic or shut down the process. Instead:

Thank them and restate your researched range.
Ask if there’s flexibility, or if an improved offer is possible with added responsibilities or a later review.
Gauge if other benefits (stock, remote stipend, learning budget) could close the gap.

Stay polite but firm—many companies leave a cushion for negotiations.