If your job description says “5 days on-site in Mexico City,” you have not posted a LATAM role. You have posted a Mexico City role, and a weak one, because the senior engineers you want have been working remotely for a decade and read office attendance as a pay cut. Here is the supply math behind that, and what to do instead.
TL;DR
- LATAM’s senior engineers went remote-first years before 2020, by selling their work to US and European companies. Remote is not a perk there, it is the default employment model.
- A 5-day mandate in one metro removes 90-97% of a region-wide pool. You are not filtering for commitment, you are filtering by postcode.
- Door-to-door commutes in São Paulo, Mexico City, Bogotá and Lima run 1.5-3 hours round trip. Five days of that is 400-600 hours a year, an unpaid second job.
- Expect a double-digit salary premium for on-site and a longer fill, because you now compete with local banks and telcos for physical bodies instead of with US companies for remote ones.
- Retrofitting RTO onto an existing remote LATAM team is a resignation event. Your top quartile has offers within weeks.
- Quarterly onsites, hub-and-spoke, and core overlap hours capture most of the collaboration value at a fraction of the supply cost.
LATAM engineers were remote-first before it was a US debate
The remote norm in Latin America was not created by the pandemic, it was created by currency. Around 2014-2016, the best engineers in Buenos Aires, Medellín, Guadalajara, Recife and Montevideo discovered they could bill in dollars for foreign clients while living on local costs. By 2019, “trabajo remoto para el exterior” was the aspirational career track, and it was structurally remote: the client was 4,000 miles away, so there was no office to go to.
That produced a selection effect that still governs the market. The strongest senior profiles, the ones with real distributed-systems depth and C1 English, largely exited the local on-site job market years ago. What remains reliably available for 5-day on-site work skews toward engineers who have not yet won remote dollar-denominated work, plus those tied to local corporates: banks, telcos, retail, consulting firms.
So requiring an office does not only narrow geography. It moves your search into a different tier of the market, where you compete on local-currency comp against employers with thirty years of head start and far better brand recognition in that city.
The commute nobody puts in the job description
US leaders model the commute as an inconvenience. In LATAM metros it is a material cost the candidate quantifies before replying to your recruiter.
| Metro | Round trip | Why |
|---|---|---|
| Mexico City | 2-3 h | Ecatepec / Neza to Polanco or Santa Fe; Santa Fe has no metro access |
| São Paulo | 2-3 h | Zona Leste and ABC to Faria Lima / Itaim; brutal peak congestion |
| Bogotá | 1.5-2.5 h | TransMilenio dependency, limited rail, north-south asymmetry |
| Lima | 1.5-3 h | One operating metro line, Javier Prado bottlenecks |
| Buenos Aires | 1-2 h | Best transit of the five; conurbano to Microcentro |
Two hours a day, five days a week, is roughly 480 hours a year, or twelve full working weeks. Add transport cost, a non-trivial slice of net pay in these cities, plus the safety calculus of leaving the office after a late deploy. A senior engineer prices that, correctly, as a large real-terms cut.
This is also why “hybrid, 3 days” is not the compromise US teams think it is. Three days on-site preserves the full requirement to live within commuting distance: the candidate still cannot relocate to a cheaper city or restructure their week. You lose most of the supply advantage while keeping most of the pain.
The arithmetic: from a region to a radius
Run the funnel on a concrete role: senior backend engineer, 7+ years, strong English, US overlap. Index the region-wide remote pool at 100.
| Constraint applied | Remaining pool (indexed) |
|---|---|
| Region-wide, fully remote | 100 |
| One country only | ~25-35 |
| One metro area only | ~10-18 |
| Inside a realistic commute radius | ~5-9 |
| Actually willing to be on-site 5 days | ~2-4 |
Two to four out of a hundred. The last step is the one people underestimate: willingness correlates inversely with seniority. The engineer with 12 years of experience is more likely to have kids, a home in a suburb chosen for space rather than transit, and three recruiters offering remote roles. The people most willing to commute daily have the least leverage, which is the opposite of who you want.
A shrunken pool also means fewer candidates per stage, less negotiating room and slower closes. Search duration does not scale linearly with pool size, it scales badly.
What the mandate costs you in money and time
You will pay a premium. Full-time on-site roles in LATAM hubs need a meaningfully higher offer than the equivalent remote role to compensate for commute time, transport spend and lost optionality. Budget a double-digit percentage uplift, and expect it to grow with seniority.
You will also pay in structure: office space, a local entity or a heavier employer-of-record setup, and compliance with location-specific rules. Several countries codified remote work explicitly (Mexico’s NOM-037, Colombia’s Ley 2121, Brazil’s CLT teletrabalho provisions), so remote is a well-trodden legal path, not a gray area you are inventing.
And you pay in time-to-hire. A remote LATAM search for a solid senior profile moves in weeks. The same search restricted to one metro with mandatory attendance takes two to three times longer, with a higher offer-decline rate at the end.
Imposing RTO on an existing LATAM team is a resignation event
Announcing RTO to an existing distributed LATAM team is re-negotiating every contract at once, because that is what your engineers will hear. The terms they accepted included location freedom, and for many that freedom was the reason they left a local corporate job.
The order of departure is predictable: your strongest engineers leave first, because they can. A senior with two years at a US company, English and a clean commit history generates multiple live processes in a month. Your weakest performers comply. You get the inverse of the retention curve you wanted, plus 8-12 weeks of search per backfill and months of ramp on top.
If you must change location terms mid-flight, negotiate rather than announce: individual conversations, a comp adjustment that genuinely covers commute cost and time, and a long runway. Forecast the loss rate before you send the email.
Middle grounds that actually work
The collaboration benefits leaders want from an office are real. They are not worth 97% of the talent pool. Buy them directly instead.
- Quarterly onsites. Three to five days, planning plus social, everyone in one city, fully funded. This delivers the relationship-building that RTO is usually a proxy for.
- Hub-and-spoke. Where you already have three or more engineers in one metro, fund a coworking allowance and keep attendance optional. Clusters form naturally in Guadalajara, Medellín, São Paulo and Buenos Aires.
- Core overlap hours, not office hours. LATAM’s structural advantage is the time zone, not the geography. Mandate a 4-5 hour overlap window with your US team and hold it firmly. That solves the real problem, which is asynchronous latency, not empty desks.
- On-site onboarding only. First one or two weeks in person, then remote. Highest-leverage in-person time, lowest supply cost.
- Measure what you claim to want. PR cycle time, review latency, incident MTTR, design-doc throughput. If those are healthy remote, the office argument is aesthetic.
A 5-day mandate is defensible under a hard constraint: on-prem hardware, regulated data that cannot leave a facility, or a physical product. If that is you, scope it deliberately, pick one metro, pay the premium and staff a local entity. If your reason is “culture” or “juniors need mentoring,” buy the outcome, not the seat.
Frequently Asked Questions
Is remote really the norm for senior engineers across LATAM?
For the segment US companies want, yes. Engineers with strong English and 6+ years of experience have served foreign clients remotely since well before 2020, and most have never had a daily office routine in that mode of work. Local on-site jobs still exist in volume, but in a different comp tier with a different candidate profile.
How much does the pool grow if I drop the on-site requirement?
Roughly an order of magnitude. Moving from "5 days on-site in one metro" to "remote, anywhere in LATAM with 4 hours of US overlap" takes you from a few percent of the addressable pool to essentially all of it, and it opens secondary cities like Córdoba, Cali, Curitiba and Mérida where competition is lower and retention is better.
Is 2-3 days hybrid a reasonable compromise?
Not from a supply perspective. Any requirement that forces the candidate to live within commuting distance keeps the geographic filter fully in place, you only reduce how often they suffer it. A compromise that actually preserves supply makes attendance optional and clusters hiring in one or two cities.
What premium should I budget for on-site work in LATAM?
Plan for a clear double-digit percentage uplift over the equivalent remote offer, plus facility costs and a heavier legal setup. The premium compensates commute time and transport spend, and rises with seniority because senior candidates have more remote alternatives. An on-site role priced at remote market rates will not close.
We already have a remote LATAM team. Can we introduce onsites without losing people?
Yes, if they are periodic and funded. Quarterly or semiannual gatherings with travel, lodging and time fully covered land well, because they read as investment rather than surveillance. What triggers attrition is recurring mandatory attendance imposed on people hired under remote terms.
Doesn't remote hurt junior engineers?
It hurts juniors who are left unsupported, which is a management problem, not a location problem. Pairing schedules, a named mentor, recorded architecture walkthroughs and a firm overlap window handle most of it. If you want in-person time for early-career hires, concentrate it in onboarding and quarterly onsites instead of making the whole team commute year-round.
