Why Your Nearshore Hires Leave in Six Months (And What Actually Retains Them)

Nearshore hires do not usually leave because of money. They leave because the first 90 days never gave them a way to prove value, and by month six both sides have quietly concluded it is not working.

The numbers on the failure are well established. 74% of employers admit they have made a wrong hire (SHRM / CareerBuilder). A bad hire costs up to 30% of that employee’s first-year salary (US Department of Labor). At a senior nearshore salary of $83,200, that is roughly $25,000 in direct cost, before you count the manager hours, the team drag and the six months you spend hiring the replacement.

The cycle is predictable. You ask for talent. You get fifty names nobody truly vetted. The filtering work lands back on your engineering managers. You hire out of urgency. Six months later you start over.

Here are the four points where it actually breaks.

Failure point 1: You optimized for the offer, not for the first 90 days

Getting the offer accepted is roughly 10% of the journey. The other 90% is the first 90 days, cultural translation and the path to real autonomy. Most hiring processes invest all of their energy in the 10%.

What breaks. In a large company, a new engineer lands into structure: KPIs, SOPs, a documented onboarding path. In a startup of 10 to 100 people, which is what most companies hiring in Brazil actually are, none of that exists. The new hire is expected to help build the strategy, not execute a plan handed to them.

Nobody tells them that. They arrive expecting a plan, find a void, and spend six weeks being quietly unproductive while assuming that is normal.

What fixes it. Say the quiet part in the offer conversation. “We do not have structured onboarding. In your first 30 days we expect you to identify what is missing and propose it.” That single sentence converts a confusing environment into a stated expectation, and it filters for the people who find ambiguity energizing rather than paralyzing.

Failure point 2: You hired for hard skills and staffed for soft ones

The strongest predictor of whether a remote hire works out is not their stack. It is whether they can articulate impact, own a blocker, and communicate across a cultural gap.

“I always thought that teaching hard skills is much easier than teaching people soft skills. I would prefer to teach someone a new stack rather than teaching them how to communicate, or how to behave in high stakes situations.” — Beatriz França, People and Culture leader, 10+ years, speaking at Beyond Hire

What breaks. A candidate passes the technical loop, lands on the team, and then goes quiet for a month. Not because they cannot code. Because they are waiting for someone to tell them what to do, and on a distributed team nobody is coming.

What to screen for instead. Three observable behaviors, all testable in a normal interview:

1. Impact articulation. Ask what they built. Weak answer: “I have 10 years in X.” Strong answer: “I used X in this context, and it reduced risk and unlocked budget.” The formula is experience plus the context of the challenge plus the business outcome.
2. Ownership under blockage. Ask what they did the last time something blocked them for a week. Weak answer: “I was waiting on access.” Strong answer: “I messaged IT, set a deadline, escalated on Wednesday, and shipped.”
3. Reciprocal evaluation. Candidates who interview you back, asking about scope, culture and expectations, are the ones who stay. Someone treating the interview as an audition rather than a negotiation has not assessed whether the fit is real, which means you will both find out at month five.

Failure point 3: Feedback lands as rejection instead of investment

This is the most avoidable one, and it is almost entirely a translation problem.

In Brazilian professional culture, work relationships are relational first. The first week involves rapport, personal connection, and a fair amount of context around any criticism. In much of North American and Northern European work culture, direct criticism of the work is standard and is not a comment on the person.

A new hire from Brazil receiving blunt feedback in week three, with no relational buffer, frequently reads it as “they are about to let me go.” They tighten up. They over-explain. They stop volunteering.

What fixes it. Name the norm explicitly during onboarding. One paragraph is enough:

“On this team we critique work directly and early. If we point out flaws, it is because we expect you to be here a long time. If we thought it was not working, we would be having a different conversation.”

That framing is accurate, and it converts a perceived threat into what it actually is. In many global cultures, pointing out flaws is not an insult. It is an investment.

Failure point 4: You built a two-tier team

The fastest way to lose a nearshore hire at month eight is to treat them as a resource rather than a team member. No equity. No access to the strategy conversation. No path to seniority. A separate Slack channel for “the contractors.”

Senior Brazilian engineers reading that structure correctly conclude the ceiling is visible from the door.

What fixes it. Treat nearshore hires as first-class team members. Equity where the model allows. Real career conversations. Presence in the meetings where decisions get made. This is the difference between the teams reporting 93% to 97% retention in remote-for-global roles and the teams that restart every six months.

The retention checklist

Lever	Action	Owner
Expectation setting	Say explicitly that onboarding is unstructured and initiative is expected	Hiring manager
First-week clarity	Name three deliverables for the first 30 days	Hiring manager
Feedback framing	Explain the team’s directness norm during week one	Hiring manager
Blocker protocol	Tell them who to escalate to and after how many days	Team lead
Priority alignment	Recurring conversation on what is critical vs. what can slip	Team lead
Career path	State what the next level looks like and what earns it	Hiring manager
Team parity	Same tools, same meetings, same visibility as domestic staff	Leadership

What this costs if you skip it

Item	Cost
Bad hire, direct cost	Up to 30% of first-year salary (US Dept. of Labor)
At $83,200 senior nearshore salary	~$25,000
Recruitment and onboarding, per hire	$4,700 – $5,475 (Vena)
Frequency across employers	74% have made a wrong hire (SHRM / CareerBuilder)
Time lost	Roughly two quarters of team velocity

These are industry benchmarks, not Tookn results.

Frequently asked questions

Why do remote developers quit within six months? Most often because the first 90 days gave them no clear path to demonstrate value. In startups without structured onboarding, a new hire who expected a plan finds a void, stays unproductive without knowing it is fixable, and disengages. Compensation is rarely the primary driver, particularly in nearshore roles that already pay a large premium over local rates.

How much does a bad hire cost? Up to 30% of the employee’s first-year salary according to the US Department of Labor. On a senior nearshore salary of about $83,200, that is roughly $25,000 in direct cost, plus $4,700 to $5,475 in re-recruitment and roughly two quarters of lost team velocity. 74% of employers report having made a wrong hire (SHRM / CareerBuilder).

How do you onboard a remote engineer in a startup with no process? State up front that structured onboarding does not exist and that identifying gaps is part of the role. Name three concrete deliverables for the first 30 days. Define who to escalate to and after how many days. Explain the team’s feedback norms in week one. Ambiguity is workable when it is declared. It is corrosive when it is a surprise.

What retains nearshore engineering hires? Team parity above all: same tools, same meetings, same visibility and the same career path as domestic staff. Then explicit expectation setting in the first 90 days, feedback framed as investment rather than warning, and a stated route to seniority. Teams doing this report 93% to 97% retention in remote-for-global roles.

Should I screen for soft skills when hiring remote engineers? Yes, and weight them heavily. Hard skills are more teachable than communication, ownership under ambiguity and cross-cultural adaptation. Screen for impact articulation, behavior when blocked, and whether the candidate evaluates you as seriously as you evaluate them.

Keep reading

• The First 90 Days at a Global Company  [→ https://tookn.io/blog/first-90-days-global-company]
• Cultural Translation: What Nobody Warns You About  [→ https://tookn.io/blog/cultural-translation-global-teams]
• How to Hire Developers in Brazil: Four Legal Models Compared  [→ https://tookn.io/blog/how-to-hire-developers-in-brazil]
• Why Brazil Is the Top Nearshore Destination in 2026  [→ https://tookn.io/blog/why-brazil-nearshore-engineering-2026]

The hire is just the beginning. Companies do not need a random list. They need the right match, real curation, and someone who stays involved after the hire.