Backend
- Node and TypeScript services
- Python — Django, FastAPI
- Go, Java and Kotlin
- Ruby on Rails, including legacy upgrades
- .NET, deepest pool in Colombia
- Elixir and Phoenix — thin, but we can map it
Home / Roles we fill
CoverageEngineering, customer-facing support, and finance. Those are the functions where we have real bench, real market maps, and recruiters who can hold a technical conversation without reading from a sheet. If your role sits outside them, we will say so on the intake call rather than take your retainer and learn on your time.
Individual contributors and first-line managers, mid-level through staff. We recruit against your rubric and your interview loop; we do not run a parallel "Interlatin-certified" process and ask you to trust it.
Level definitions we use, so we are talking about the same thing: mid is three to six years and ships features independently; senior is seven-plus, owns a service and reviews others' design; staff influences multiple teams and has genuinely operated something at scale. Titles inflate wildly in this region, so we grade on the interview, not on the CV header.
A support team three hours off your customers is a support team with a backlog every morning. This is the clearest case for hiring in this hemisphere rather than across an ocean, and it is where we build the largest teams — usually five to thirty people at once.
Volume teams work best in Barranquilla, Cali, Mérida and Recife, where the bands are lower and there is far less competition from other US buyers than in the capital tech markets. For a small, senior support pod attached to an engineering team, Mexico City or Medellín is usually the better call.
Bilingual accountants are scarcer than bilingual engineers, and every search here is genuinely a search rather than a filter of an existing pipeline. We take fewer of these and we close a higher share of them.
Four filters. Each candidate who reaches your inbox has passed all four, and you get the written notes for every one of them — including the parts that argue against hiring.
Why they are looking, what they turned down recently, their real notice period, their band expectation stated as a number, and whether the working hours in your role are compatible with their life. Roughly half of a raw pipeline dies here, which is exactly where it should die.
Twenty unscripted minutes about something they actually did — the last incident they handled, the last close they ran. We grade against the CEFR scale and, more usefully, against a plain question: could this person run your standup on a bad Wednesday? The grade and a short justification go in the notes.
We use your scorecard, not a generic one. For engineering that is normally a 45-minute conversation about a system they built, with follow-ups written by your team. If you don't have a rubric, we will draft one in the intake call and you approve it before we screen anybody.
Country, contract vehicle, tax status, banking, equipment, and whether anything in their current arrangement — a non-compete, an unfinished monotributo re-categorisation, a visa process — will delay the start date. Catching this before the offer is the difference between a five-week and a nine-week hire.
Saying no to a requisition we cannot close is cheaper for both of us than a search that runs eight weeks and dies.