Hiring is slower right now. That's real.
Six months to fill a senior engineering role in San Francisco. $250k+ TC. A bench you can't scale without bleeding cash. The leaders we work with stopped framing this as a temporary problem about a year ago.
Now they're framing it as a question: what model would we choose if we were starting today?
The math that stopped making sense
Three things shifted between 2023 and 2026, and they compounded:
- Senior compensation kept rising while velocity didn't. A staff engineer in a US tier-1 metro now costs $300k+ all-in. Their output didn't grow proportionally. That's not a critique of US engineers. It's a critique of the salary curve.
- The 2020-2022 hiring binge created a retention tax. Companies that paid above-market in 2021 inherited that comp band. New hires expect parity. Cuts to backfills don't fix this.
- The "remote is temporary" wager lost. Every senior engineer who wants remote work has remote work. Companies that pulled back to "office or quit" sacrificed their top quartile. Companies that kept remote opened the geography question.
Once geography is open, the next question is obvious: if we're hiring remote anyway, why are we paying a Bay Area premium for someone in Austin?
And the question after that: if it's Austin, why not Costa Rica?
What "nearshore" actually means (and what it doesn't)
The word has been abused. Most people hear "nearshore" and think Mexico call center. Or they hear it and think offshore with marketing makeup. Both are wrong, and the wrong framings are why CTOs default to "we tried that once."
Here's the version that works:
- Time-zone aligned. Costa Rica is on Central Standard Time year-round. Colombia is on Eastern Standard Time year-round. Your 10am standup is their 10am standup. No relay race. No "I'll see this in the morning."
- Bilingual by default. Not "passable English." Working English. Slack-tone English. The kind that doesn't slow your sprint planning.
- Engineering culture, not BPO culture. The talent pool comes from CS programs at universities that have been producing senior engineers for US tech companies for twenty years. Intel has been in Costa Rica since 1997. The infrastructure exists.
If your "tried it once" experience was a 12-hour offset, broken English, and an account manager who couldn't tell you what your engineer was working on, that wasn't nearshore. That was offshore wearing a name tag.
“SMASH has been a strong partner and has allowed us to build software and solutions that we couldn't have done on our own because we didn't have the ability to find that kind of talent locally and scale up that quickly.
”
The shift isn't cost. It's continuity.
Here's the part most "nearshore" content gets wrong: the leaders who actually make the switch don't do it for the cost arbitrage.
The cost is real (call it 40-60% lower fully-loaded vs. a US senior), but if cost were the only lever, you'd see those leaders moving to the cheapest geography possible. They don't. They specifically choose nearshore because of continuity.
The continuity argument:
- Senior engineers hired in LATAM have lower attrition than equivalent US hires. The local market doesn't churn the same way.
- Once integrated, they stay on the same product for years. That institutional memory is invisible until someone leaves and you realize how much they carried.
- A team that's been together for 18 months ships more in a quarter than a team that's been together for 6.
The math that finally clicks for CTOs isn't "this is cheaper." It's "this is the team I can actually keep."
What to ask if you're considering the switch
If you're at the "what would we do if we were starting today" stage, the questions worth asking aren't about the model. They're about the partner:
- How do you vet senior? ("AI-vetted" is theater. Ask who runs the technical interview and how senior they are.)
- How do you handle integration? (Embedded means embedded. If your engineers won't be in your Slack, on your standups, in your sprint planning, that's outsourcing.)
- What's the path from one hire to a team? (Most clients we serve start with one role and grow to 8+ in 12 months. The model has to flex.)
- What happens if it doesn't work out? (Real partners have a clean exit. No 18-month contracts that hostage you.)
- Who pays them, who manages them, who replaces them if they leave? (If those three questions have three different answers, or worse, no answers, walk away.)
If you're at the point in your scaling story where you're asking "how do we build the team we'd actually want to keep," we should probably talk. Send us a note or book a call and we'll show you what an embedded team would look like for your operation.