When One Background Check Is Not Enough for Remote Hires in Latin America

You did everything right.

You verified their ID. Checked their portfolio. They passed.

Six weeks later, the code they’re shipping looks nothing like what they showed you in the interview. Or worse they’ve gone quiet entirely.

This isn’t rare. US and UK employers hiring in Latin America report that somewhere between 20–30% of hires where something felt off, it didn’t show up until month one, two, or three.

Not at the application stage. After.

Why Pre-Hire Verification Only Solves Part of the Problem

A solid hiring process catches the basics. Identity, address, phone, work history, skills quiz.

But Latin America doesn’t have centralized criminal or employment databases the way the US does. Records are fragmented across countries, provinces, sometimes cities.

Privacy laws in Brazil, Colombia, and Mexico limit what you can even pull — and what that means in practice is that pre-hire checks can verify identity without being able to verify experience.

A quiz can confirm someone knows React syntax. It can’t confirm they’ve ever shipped a production app.

A portfolio looks impressive until your lead developer notices the GitHub repos are all forked, last committed to three years ago, or the live links 404.

Deepfakes in video interviews are no longer a rare edge case. Proctored skill tests have been gamed.

The reality is that the first 90 days is when you find out who you actually hired.

What Actually Goes Wrong in the First 90 Days

There are a few patterns that come up again and again.

The skills gap. Someone claims senior-level React or Node.js experience, passes a proctored quiz, and then the first real sprint reveals junior output. Sometimes it’s AI-assisted interview performance. Sometimes it’s inflated self-assessment.

The fake work history. LinkedIn profiles with jobs at companies that don’t verify employment, or that the person left after two weeks. References that turn out to be friends. Blogs and portfolio pieces that were copied.

Moonlighting. Someone takes your role while keeping two or three others. For US-based teams this is annoying. For AU or UK teams already working with limited timezone overlap, it’s a real productivity problem.

Location mismatch. Someone lists Mexico City, turns out they’re operating from a different country entirely. This creates timezone issues, sometimes tax issues, and occasionally a genuine trust problem.

What to Do in the First Four Weeks That Most Employers Skip

The onboarding window is your best chance to verify what the pre-hire process couldn’t.

Live pair programming. Not another quiz — actual collaborative work. Two hours on a real or near-real problem. Screen shared, camera on, working through it together. You’re not just evaluating output; you’re watching how they think, communicate, and handle something they haven’t prepared for.

IP verification against the address on file. If someone told you they’re in Bogotá and they’re logging in from somewhere else consistently, that’s worth understanding.

Reference calls, not reference checks. An email to a listed reference gets you a polished response. A 15-minute call with a previous client — asking how the person handled feedback, what the work actually looked like, whether they’d hire again. Ask for a previous client’s contact, not just a listed reference.

Portfolio link audit. Run through every link in their portfolio. If something 404s, ask about it. If GitHub repos look inactive or forked, ask about that too. Most of the time there’s an explanation. Occasionally there isn’t.

How to Structure Months One Through Three

Once someone is past onboarding, the verification work shifts from “is this person who they said they are” to “is this working relationship what we thought it would be.”

Monthly output reviews tied to Git commits or deliverable logs. Not performance reviews in the HR sense just a check that the work is being produced by the person you hired, at the level you hired them for. Authorship trails in Git, timestamped file submissions, async Slack activity patterns — these tell a story over time.

Quarterly reference calls. Yes, again. Once at hire isn’t enough. A call with a current or recent client at month three, framed as a check-in rather than an investigation, keeps you grounded in who this person is outside your engagement.

“No moonlighting” in the contract, with clarity around what that means. Not every employer wants exclusivity and not every contractor can offer it. But if you do need someone’s full attention, that needs to be in writing — and it needs to be defined.

A Few Things Worth Knowing by Country

Mexico — RFC (tax ID) verification post-hire is worth doing if you’re running a longer engagement. It’s a basic compliance step that a lot of employers skip.

Colombia — Criminal record checks are legally limited. Focus energy on reference calls rather than trying to pull records. Medellín and Bogotá have strong talent communities where professional reputations travel — a real reference call in this market goes a long way.

Brazil — LGPD means you need explicit consent before running additional background checks post-hire. Build that into your contract upfront. Don’t try to add it later.

Argentina — CUIT verification matters, especially if you’re paying in USD. Get it documented early. The currency situation makes payment records important for both sides.

One Practical Framing for Smaller Teams

If you’re running a smaller operation and don’t have the bandwidth for a full quarterly compliance process, here’s a simpler way to think about it.

Hire two junior candidates for a real three-month project instead of one senior candidate for an ongoing role. Pay both. See what they produce.

By the end of month three you’ll know more about both of them than any pre-hire process could have told you.

It costs more upfront. It costs less than the alternative.

The Thing That Doesn’t Change

The best hires in Latin America aren’t going to be bothered by a structured verification process. They’ve often dealt with employers who didn’t have one and paid the price for it.

A clear process, communicated openly, signals that you’re a serious employer. That you’re building something real. That the working relationship matters.

The people who push back on reasonable verification during onboarding are usually the ones you find out about in month two anyway.

Build the habit now. It’s a lot easier than fixing things after.