All articles
NearshoreJun 20, 2026 · 9 min read

What Years of Building Tech Teams in LatAm Taught Us, and Why It Led to NearCore

What Years of Building Tech Teams in LatAm Taught Us, and Why It Led to NearCore

NearCore exists because years spent building tech teams across Latin America surfaced the same two problems on repeat: US companies were paying a real markup to an intermediary reselling the exact same LatAm talent a direct provider could offer, and the label Senior had stopped meaning anything consistent across the market. Neither problem was a one-off bad deal. Once the pattern was clear enough to name, the fix was obvious enough to build a company around: sell direct, and hold a real, narrow definition of Senior. That is the short version of how NearCore came to exist, and the model has not changed since.

A recurring pattern, not a single bad deal

Years spent placing and building technical teams across the region meant sitting in the same conversation, with different companies and different roles, but the same underlying shape. A US company would come in through an intermediary (often a US-based staffing brand with a familiar name and a standard contract), and that intermediary would, in turn, source the actual candidate from the same LatAm talent pool a direct provider was already working in. The client was paying for the introduction and the paperwork comfort. The work itself, and the person doing it, were the same either way. That direct exposure to the markup is why NearCore now invoices clients in USD under one US contract, with no resale layer of its own.

That is not a criticism of the model in the abstract; the trust friction it solves is real. A single US vendor, standardized invoicing, one point of contact: those things have value, especially for a buyer new to the region. But watching the same markup get paid, deal after deal, for talent that was never actually different, is what made the pattern impossible to ignore.

The other constant across those years was watching how differently Senior got used depending on who was doing the hiring and how urgently. Sometimes it was accurate. Sometimes it was a title stretched to close a deal faster. Sitting on both sides of those conversations, building teams for companies and watching how the market described the people it placed on them, made it clear the inconsistency was not incidental; most of the market's own incentives baked it in, because nobody had a reason to tighten the definition.

The markup that stopped making sense

The intermediary layer makes sense when a buyer does not yet understand the nearshore market and needs the reassurance of a known, US-based brand standing between them and the risk. It stops making sense the moment that buyer has been through the cycle once and understands what they are actually buying. At that point, the extra layer is not adding sourcing capability, technical vetting, or ongoing management; it is adding a markup on top of work someone else is already doing. Watching that realization land, deal after deal, for companies that had simply outgrown the need for the training wheels, is what made sell direct feel less like a differentiator and more like an obligation. That is why NearCore sells directly, in USD, under one US contract, with no resale layer on top.

Senior stopped meaning anything

The second pattern was quieter but just as corrosive. Across enough searches, Senior turned out to mean wildly different things depending on who was using it: sometimes three years of experience with a generous title, sometimes a generalist stretched across a role touched only briefly, sometimes genuinely senior talent buried in a grid of Junior/Mid/Senior tiers that made it hard to know, from the outside, what you were actually being offered. That left clients doing the vetting work themselves, after the fact, that the label was supposed to have already done.

That observation is what led me to set NearCore's bar at exactly one flat, unambiguous 7-year minimum, with no tiers to obscure it, applied across exactly ten roles in two connected chains, the Data chain and the Cloud chain, plus the Data Architect role that connects them. I did not set it there because narrower was safer to promise, but because it was the only version of Senior that meant the same thing every time someone used it.

Building NearCore around two fixes

Put together, those two observations point at the same conclusion: the value being sold in this market was rarely the sourcing itself. It was trust and clarity, and both could be delivered directly instead of resold. NearCore was built around exactly that, deliberately and from day one:

  • Sell direct: USD invoicing, a US contract, one point of contact, with the intermediary layer's markup removed.
  • Define Senior narrowly and consistently: 7 years minimum, ten roles, two connected chains, and a Data Architect role that ties data design to infrastructure design.
  • Keep the fit process itself, actually understanding a client's business before searching for a candidate, as central as it was in every prior team-building engagement, rather than letting scale dilute it.

It came from watching the same two frictions repeat across enough real engagements that starting a company felt like the obvious next step. The scope stayed narrow: ten roles across two chains is a small enough surface to actually hold the bar on, and holding the bar was the point of starting over.

Built for the US market, without inheriting its vices

There is a version of this story where the fix is just cut out the middleman, and that is true as far as it goes, but it undersells what was possible by building NearCore from scratch rather than retrofitting an existing US staffing model. The layered markup, the hidden Junior/Mid/Senior tiers, and the generalist recruiter juggling categories they do not understand deeply enough to vet are not accidents of a few bad actors. They are structural features of a model that grew up domestically, where adding a resale layer or blurring a title was rarely visible enough to cost a provider the deal.

NearCore did not have to unwind any of that, because I never built it on top of any of it. There was no legacy reseller layer to justify keeping, no existing tier structure to defend, no generalist recruiting org to retrain. The USD-invoicing, direct-sourcing model and the 7-year, ten-role bar were not fixes bolted onto something else, or a premium tier carved out of a broader generalist model. They were the starting point, and the only model NearCore ever ran.

That distinction matters for a buyer evaluating providers, not just as a founding story. A company purpose-built for the US market, without the vices that make domestic staffing expensive and opaque, has no structural reason to reintroduce them later: no legacy revenue line tied to the markup, no sales motion built around a looser Senior definition a stricter one would cannibalize.

Talk to NearCore about the team you're trying to build

If any part of that pattern, the markup, or the vague Senior label, sounds familiar from your own hiring process, that is exactly the conversation worth having with NearCore. Tell us what you are building, and we will tell you plainly why NearCore was built to solve exactly this kind of problem.

Questions this article answers

Because the intermediary layer adds cost without adding sourcing capability, vetting, or management once a buyer understands the market. NearCore kept the parts that matter, USD invoicing, a US contract, one point of contact, and removed the resale markup on top.

Explore the roles behind this article

Hiring senior Data & Cloud talent?

Talk to nearcore