Attrition is the least glamorous metric in nearshore staffing, and arguably the most important one. Industry averages for tech talent turnover in Latin America run 20-30% annually meaning a company with a 10-person nearshore team, engaged through a typical provider, replaces two to three engineers every single year. Each replacement resets institutional knowledge, disrupts sprint velocity, and costs real money in recruiting and ramp-up time that rarely appears on the invoice.
At Cafeto, our attrition rate has held at approximately 7% for years a figure that isn’t a marketing claim so much as the output of a specific, deliberate set of retention practices. This article explains why attrition matters more than most companies realize, what actually drives high turnover in this industry, and the practical mechanics behind keeping it low.
Why attrition is an under-discussed financial metric?
When a nearshore engineer leaves, the visible cost is recruiting a replacement. The much larger, less visible cost is everything the departing engineer knew that the replacement doesn’t: why a particular architectural decision was made, which parts of the codebase are fragile, which client stakeholder prefers which communication style, what the last three production incidents taught the team.
For a senior engineer on a codebase for two or more years, this institutional knowledge takes months to rebuild with a new hire during which sprint velocity measurably degrades, code review takes longer because the new engineer lacks context, and the risk of reintroducing previously-fixed bugs increases.
At a 25% annual attrition rate, a 10-person team effectively never reaches full institutional maturity there’s always a meaningful fraction of the team still ramping up. At 7%, the team spends the overwhelming majority of its time at full institutional capacity. This compounding difference, not the direct recruiting cost, is where the real financial impact of attrition lives.
What actually drives high attrition in this industry
Compensation that doesn’t keep pace: In a genuinely competitive talent market like Bogotá or Medellín, engineers who feel underpaid relative to market rate leave the moment a better offer appears and with local tech ecosystems maturing rapidly, better offers appear often.
Treatment as a resource, not a professional: Engineers placed with clients who exclude them from planning conversations, provide minimal context, and evaluate them purely on ticket throughput disengage faster, and disengaged engineers leave faster.
Absence of career development: Engineers with genuine options and Colombia’s best engineers increasingly have them will choose employers who invest in their growth (certifications, training, career pathing) over ones who treat the role as static.
Reactive rather than proactive HR: Providers who only engage with placed engineers when a problem surfaces miss the early signals of disengagement that, addressed proactively, often prevent departure altogether.
The specific practices behind Cafeto’s 7% rate
Competitive, regularly benchmarked compensation: Salaries are reviewed against current local market data on a defined cadence, not left static until an engineer raises the issue themselves by which point they’ve often already started looking elsewhere.
Structured career development: Certification support (AWS, Azure, Fortinet NSE, ISTQB, and others relevant to an engineer’s specialization) and defined career pathing give engineers a visible growth trajectory within the organization, rather than a ceiling they’d need to leave to get past.
Proactive HR touchpoints: Regular, scheduled check-ins between HR and every placed engineer not just performance reviews, but genuine engagement conversations surface disengagement signals early enough to address them, rather than learning about a problem via a resignation letter.
Cultural integration with client teams: Engineers who are genuinely included in client planning, treated as professionals whose judgment is valued, and given real context beyond their immediate tickets report meaningfully higher engagement and engagement is one of the strongest predictors of retention across any industry, not just software.
Transparent escalation paths: When friction arises between an engineer and a client team, a clear, non-punitive escalation path rather than an engineer feeling they have to simply endure a bad situation or quit resolves a meaningful fraction of situations that would otherwise end in departure.
Consistent workload and expectations: Engineers who experience wildly inconsistent workload (crunch followed by idle periods) or shifting expectations without clear communication disengage faster than those on stable, well-managed projects.
Why retention is a decision as much a provider decision
Retention is not solely the provider’s responsibility. How a client treats a nearshore engineer measurably affects whether that engineer stays. Clients who include nearshore engineers in planning, communicate clearly and consistently, and treat placed talent as team members rather than resources contribute directly to lower attrition on their own engagements a dynamic best understood as a shared responsibility between client and provider, not something either party fully controls alone.
This is one reason mature nearshore partners actively coach client-side engineering managers on practices that improve engagement not out of altruism, but because retention outcomes genuinely depend on both sides of the relationship.
How to evaluate a provider’s attrition claims
– Ask for the actual number, not a vague “low turnover” claim and ask how it’s calculated (voluntary vs. total, trailing 12 months vs. lifetime average)
– What specific retention practices produce that number compensation benchmarking cadence, career development programs, HR touchpoint frequency
– Ask for a reference client whose engineers have stayed 3+ years on the same engagement
– Ask what happens when an engineer does want to leave is there a structured transition process, or does the client simply lose institutional knowledge overnight
Conclusion
Attrition is the quiet variable that determines whether a nearshore engagement compounds in value over time or resets every twelve to eighteen months. The difference between 25% and 7% annual turnover isn’t luck or market conditions it’s a specific set of deliberate practices around compensation, career development, proactive engagement, and cultural integration, sustained consistently over years. For any company evaluating a nearshore partner, the attrition number deserves the same scrutiny as the rate card. It’s arguably the more important figure of the two.
Bibliography
- Deloitte. (2025). Human capital trends report 2025: The worker-employer relationship disrupted. Deloitte Insights.
- LinkedIn Economic Graph. (2025). LinkedIn talent insights: Software engineering hiring trends 2025.
- HireWithNear. (2026). US companies hiring in Latin America: 5 strategic trends for 2026. https://www.hirewithnear.com
- SHRM. (2025). SHRM HR benchmarking reports 2025.
Book a Consultation to learn about engineering operations to Colombia:
https://outlook.office.com/book/[email protected]/?ismsaljsauthenabled
Learn about: The Changing Economics of the H-1B Visa here
