Setting Fair Salaries When You Hire In Latin America And The Philippines
Figuring out how to set salary for remote roles is one of the most frustrating parts of building a distributed team. You know the role, you know the budget, but the moment you open a salary survey, you find data for Bogota, Manila, and Mexico City that are wildly different from each other, and you are left guessing which number actually applies to your situation.
When you get this right, you stop losing top candidates to competitors who simply communicated their pay logic better. You also reduce the risk of paying two people in the same role very differently for no defensible reason, which tends to surface during performance reviews and cause real trust problems.
This guide walks you through every step, from building a pay philosophy to keeping your bands current as markets shift. At Walter, we spend every day connecting U.S. businesses with talent in Latin America and the Philippines, and this is what we've learned about structuring compensation in a way that is fair and sustainable.
Decide What Your Company Believes About Pay First
Your pay philosophy is the single decision that makes every other compensation choice easier or harder, and most teams skip it entirely. Getting it in writing before you run any benchmarks saves you from having to relitigate the same internal debates every time you open a new role.
Should Pay Follow The Person Or The Position
These two approaches represent genuinely different bets on what your company values, and each one carries real trade-offs for your hiring funnel.
Location-based pay ties a person's salary to the cost of labor in their home country or city. A developer in Bogota earns a different amount than one in Mexico City for the same role. This approach is common and keeps your compensation data cleaner because you are always benchmarking against a defined local market.
Role-based pay sets a single rate for a position across the region you hire in, regardless of exactly where the person lives. Some companies anchor this to the most competitive market in the region, others to a regional median. The benefit is simplicity and a strong message to candidates that output matters more than geography. The risk is that you may overpay relative to local norms in lower-cost areas, which stretches your budget without needing to.
The right choice depends on where your candidates come from and how dispersed your team is. If most of your hires are concentrated in two or three countries, location-based pay is manageable. If you hire across the whole region, a simpler band may serve you better.
Look At Your Own Team Before You Look At The Market
Before you pull any external salary data, map what your current team earns across similar roles. External benchmarking tells you what the market pays; internal equity tells you whether your own team is in a fair relationship with each other.
A new hire offer should not leapfrog a two-year employee doing the same job. That gap creates resentment the moment it becomes visible, and in remote teams, salary information travels fast. Identify your current pay distribution by role and level first, then use market data to validate or adjust your bands, not to build them from scratch while ignoring what already exists.
Pick The Right Benchmark
Picking the wrong labor market to benchmark against is one of the most common and costly mistakes in international compensation. Your choice here shapes whether your offers land competitively or consistently miss the mark.
Three Ways To Anchor Your Pay Scale
Three markets compete for your attention when you set pay for a distributed team: where your candidates live, where your company has a physical presence, and the revenue market your company competes in.
Candidate location pricing means you match the local labor market for each hire. It keeps costs predictable but adds administrative complexity as your team spreads across more countries.
Team hub pricing anchors everyone to the country where most of your workforce is located, even if the new hire lives elsewhere. This is simple to administer but can make you uncompetitive in higher-cost markets and over-budget in lower-cost ones at the same time.
Revenue market pricing ties pay to the economic tier your company operates in, not where employees sit. A startup generating revenue from enterprise clients in the U.S. often uses U.S. market rates even when the team is fully distributed across LATAM or the Philippines. This approach attracts candidates who know their work drives high-value outcomes and expect to be paid accordingly.
Most companies use a blend: revenue market anchors the ceiling, candidate location guides adjustments within a defined range.
Why A Range Beats A Fixed Number
A salary band gives you a minimum, midpoint, and maximum for a role. Single rates, where everyone in a job title earns the same amount, are easier to explain but harder to defend as your team grows.
Use bands when you have more than a few people in the same role, when you hire across multiple experience levels within that role, or when you operate across multiple countries. Bands let you place a new hire at the lower end while giving a tenured employee room to grow toward the top without requiring a promotion.
A practical starting point is a bandwidth of 40% to 50% between the minimum and maximum. That gives you meaningful room to differentiate without creating a situation where two people doing the same work earn dramatically different amounts.
Turn Your Philosophy Into A Number
A compensation formula turns your pay philosophy into a number you can explain to a candidate, a founder, or a skeptical team member without flinching. The key is grounding it in role-specific inputs, not just market percentiles.
What Actually Drives The Base Rate
Three inputs drive the base rate before you factor in any location adjustments: scope, level, and how hard the role is to fill.
Scope means the actual complexity and accountability of the job. A senior developer who owns a critical part of the product earns more than one who handles maintenance tickets, even when they share the same title and years of experience. Write scope definitions for each level before you attach a number.
Level maps to a career ladder, and your career ladder needs to exist on paper before you set pay. If you pay people at the same level differently with no documented rationale, you create a compliance risk and an equity problem at the same time.
Scarcity is the market signal that tells you when the standard band is not enough. If you are hiring a bilingual customer support lead in mid-2026 and qualified candidates have multiple offers, your band ceiling may need to move.
Track time-to-fill and offer decline rates as early signals that your bands are falling behind the market.
Balancing Base Pay With Bonus
Total compensation is what actually competes for talent, and base salary is only one part of it.
A lower base paired with a meaningful performance bonus may match or exceed a higher base with no variable pay. Be explicit about this trade-off in your offer communications, because candidates who receive competing offers will compare total compensation, not just base.
When you adjust base to reflect a different mix, document that decision so future pay reviews do not treat the person as simply underpaid or overpaid.
Know Your Full Cost, Not Just The Sticker Price
The salary you post in a job listing is not the full cost of that hire, and in international hiring the gap between listed pay and total employer cost can be substantial. Knowing this number before you make an offer prevents budget surprises later.
What Local Laws Add To The Base Salary
Payroll contributions, mandatory benefits, and statutory costs vary significantly from country to country. Each country brings its own layer of rules: some require a thirteenth-month payment, others have specific severance or probation period requirements. When you hire in a new country, verify statutory obligations before finalizing your offer, or work with a partner who already understands those rules.
Health coverage, paid time off, and other benefits are not optional considerations for competitive roles. A candidate evaluating two similar offers will weigh the benefits package heavily, which means a somewhat lower base paired with strong health coverage can outperform a higher base with thin benefits.
Why Freelance Rates Look Higher Than They Are
Independent contractors typically quote a higher hourly or project rate than employees earn on a comparable annual salary. That premium exists because contractors cover their own social security contributions, fund their own benefits, and absorb their own equipment costs.
If a contractor quotes you a rate lower than your employee equivalent, investigate potential misclassification risks. Misclassifying an employee as a contractor is one of the costlier compliance mistakes a company can make when hiring internationally, and the rules vary depending on both the country where your business operates and the country where the worker lives.
Say It Out Loud: Talking About Pay With Your Team
Even a well-designed pay structure fails if your team cannot explain it clearly and consistently. The biggest source of distrust in compensation among distributed teams is not the numbers themselves but the silence around them.
Answering “Why Do They Earn More Than Me”
If you use location-based pay, candidates and employees will ask why someone in one country earns less than someone in another doing the same job. You need a prepared, honest answer grounded in your pay philosophy, not an improvised one.
The clearest explanation ties pay to local labor market rates. Something like: "We benchmark compensation against the competitive pay for your market, which means your salary reflects what it takes to attract and retain talent where you live." That answer is defensible as long as your benchmarking data is up to date and applied consistently.
What damages trust is inconsistency. If you apply location adjustments to some roles but not others without a documented reason, employees will notice. Write your geographic pay rules into your compensation policy and make that policy accessible to your whole team, not just managers.
Giving Managers The Words To Use
Managers who cannot articulate why someone is paid what they are paid become a liability in retention conversations. Give them a script, not just a policy document.
A practical talking-point framework:
- What the role is benchmarked against: "This role is priced against regional data for [job family] at the [level] tier."
- Where this person sits in the band and why: "You are at the midpoint because you joined with two years of relevant experience, which is our standard placement for that profile."
- What movement within the band looks like: "As you demonstrate [specific outcomes], we review band placement during the annual cycle in [month]."
Train managers to deliver these points without reading from a script, and practice with them before performance review season. A manager who stumbles through a salary conversation sends a signal that the company does not have a real system, even if it does.
Don't Let Your Bands Go Stale
A salary band you built in 2023 is likely out of position in 2026, especially in technical and bilingual roles where compensation has moved sharply. A static system becomes a retention risk faster than most teams realize.
When To Revisit Your Numbers
Set a scheduled review at least once per year, and tie it to a specific date so it does not slip. Many companies align compensation reviews with their fiscal year-end or the start of hiring season.ghyttttt656667777777777777744544444444444444444444444444444444444444444444444444444444444444444444444444444444444444
Beyond the calendar, define trigger events that force an off-cycle review. These include: a significant shift in hiring difficulty for a role, a wave of counteroffers above your band ceiling, or the entry of a well-funded competitor into your talent market. Waiting for the annual cycle after a trigger event means you lose people you could have retained.
A Simple Yearly Checkup For Your Bands
Run this exercise once per year, or whenever a trigger event occurs:
- Pull the current salary for every person in each role and level.
- Calculate where each person sits as a percentage of the band midpoint. This is their compa-ratio. A ratio below 80% signals potential underpay; above 120% signals compression risk.
- Compare your band midpoints with at least two current data sources, such as a compensation survey and aggregated job-posting data for similar roles in the region.
- Flag any band where the midpoint is more than 10% below the median of your benchmark sources.
- Prioritize adjustments starting with the roles where you are currently hiring or where your turnover rate is highest.
- Document all changes, the data you used, and the date of the review.
This exercise takes two to three hours for a team under 50 people and gives you a defensible record if a compensation decision is ever questioned.
Frequently Asked Questions
Should remote employees be paid based on where they live or where the company is located?
Both approaches are used by real companies, and neither is universally right. Location-based pay keeps your costs tied to local labor markets, while paying based on company location applies one consistent standard to everyone. Your choice should be documented in a written compensation policy so candidates and employees can understand the logic behind their offer.
What factors do companies use to determine pay when hiring in Latin America or the Philippines?
Most companies weigh role scope, experience level, and market benchmarks for the relevant country or region. Scarcity of qualified candidates, internal equity for existing team members, and the total compensation mix, including benefits, also factor in. The goal is a number that is defensible internally and competitive externally.
How can I benchmark competitive pay ranges for a role in Latin America or the Philippines?
Use at least two data sources: a compensation survey and aggregated salary data from job postings for equivalent roles in that country. Cross-reference both to find the median and 75th percentile for your role and level. Update your benchmarks at least once per year, since these labor markets can shift faster than more established ones.
How do country-specific rules affect international pay decisions?
Each country has its own combination of mandatory benefits, payroll contributions, and worker classification rules. These rules change over time, so whenever you hire in a new country it's worth reviewing current labor law before finalizing the offer, or leaning on a partner with local experience.
What's the best way to handle cost-of-living differences when setting international compensation?
Decide upfront whether you are adjusting for cost of living or cost of labor. These are not the same thing. The cost of labor reflects what it takes to hire qualified people in that market; the cost of living reflects what people spend day-to-day. Most compensation professionals recommend anchoring to labor market data rather than cost-of-living indices, since your talent competition operates in the labor market.
How can candidates negotiate salary and benefits for an international remote job offer?
Research the market rate for your role and level using data specific to your target employers and country. Frame your ask around total compensation, including base, bonus, and benefits, rather than base salary alone. Identify the component with the most room to move, since some companies have rigid base bands but more flexible benefits or bonuses.
Where To Go From Here
Building a compensation system for a distributed team is not a one-time project. It is a process that starts with a clear philosophy, runs through defensible benchmarking and formula-building, and stays accurate through regular audits and honest manager conversations.
The companies that retain international talent longest are the ones whose employees feel like the pay system is fair and explainable, not secretive or arbitrary. That feeling comes from consistency: consistent benchmarks, consistent band placements, and consistent conversations when the numbers change.
