Ruzora
Hiring

How to Check a Developer's References (Incl. LATAM)

Reference checks feel like a formality and are one of the last honest signals you get. Ask specific questions about real behavior, talk to the right people, and listen hard to what goes unsaid.

RE

CEO, Ruzora

Updated 6 min read

To check a developer's references, talk to two or three people who worked closely with them (ideally a former manager), confirm each reference is who they say they are, and ask about specific situations instead of asking whether the candidate was good. For LATAM software engineers the standard is the same, plus two checks: verify the reference independently, and ask how the engineer worked with US or remote teams.

Reference checks are the step founders most often skip or phone in, and that is a mistake, because a real reference check is one of the last honest signals you get before committing to a hire. Done as a formality, generic questions, a nod, done in five minutes, it tells you nothing, which is exactly why people conclude references are useless. Done well, it can confirm what you saw in the interview or surface the thing that changes your mind. The difference is entirely in how you do it: asking specific questions about real behavior, talking to the right people, and listening as hard to what goes unsaid as to what is stated.

Key Takeaways

  • A real reference check is a genuine signal, not a formality to rush through.
  • Ask specific questions about actual behavior, not generic ones with easy answers.
  • Talk to the right people, ideally those who worked closely with the candidate.
  • Listen to what goes unsaid; hesitation and vagueness are signals too.

What Questions Should You Ask a Developer's References?

Generic reference questions, was the candidate good, would you hire them again, invite generic, positive, meaningless answers, because almost no one badmouths a former colleague to a vague prompt. The way to get real signal is to ask specific questions about actual behavior and situations. How did they handle a project that went wrong? What would you have wanted them to do better? Can you describe a time they were stuck and how they got unstuck? Specific questions about concrete situations are much harder to answer with empty praise, and they surface the texture of how the person actually worked, which is what you are trying to learn (interview questions for a senior software engineer applies the same specific-over-generic principle).

A short set that works for engineers:

  • What did they own on your team, and what did you have to check behind them?
  • Tell me about a release or incident that went badly. What did they do in the first hour?
  • How did they take code review feedback they disagreed with?
  • If they rejoined tomorrow, what kind of work would you give them, and what would you keep away from them?
  • Would you hire them again for the same role? (Then wait. The pause is the answer.)

Who Should You Talk To, and How Do You Read the Silence?

Two things beyond the questions matter. First, who you talk to: a reference who worked closely with the candidate, a manager or a teammate who saw their day-to-day, tells you far more than a distant or hand-picked contact. Push, politely, for people who actually worked with them rather than only the curated best friends. Second, and most important, listen to what is not said. References rarely lie outright, but they signal through omission and tone: a hesitation before answering whether they would rehire, a pointed lack of comment on a specific area, enthusiasm that goes quiet on one topic. Those silences and hesitations are often the real message, and a good reference check is as much about reading them as about the literal answers.

Weak reference checkStrong reference check
Generic questionsSpecific behavior and situations
Hand-picked distant contactsPeople who worked closely with them
Only hears the wordsReads hesitation and omission
Rushed formalityGenuine, careful conversation

What Are Reference Check Standards for LATAM Software Engineers?

The questions do not change. A few practical things do:

  • Verify the reference first. Find the person on LinkedIn, check that their history overlaps with the candidate's, and reach them through a company email or the company's main line, not only a number the candidate supplied. Remote hiring has a real fake-candidate problem, and a friend posing as a former manager is the cheapest part of that scheme to pull off.
  • Ask for at least one reference from a remote or US-facing team if the candidate has worked with one. That is the closest evidence of how they will work with you: written updates, async handoffs, speaking up in calls.
  • Offer to do the call in Spanish or Portuguese. A local manager may be far more candid in their first language. If you do not speak it, a short written questionnaire they can answer in their own language works better than a stiff English call.
  • Expect some employers to confirm only dates and title. Larger companies in the region, like many in the US, route reference requests to HR. Treat that as neutral, and lean on direct teammates instead.

If a vetting partner already ran references, ask what they checked and who they spoke to. "References checked" with no detail is not a standard.

A Concrete Version

You are about to hire a developer and do the reference check. The formality version: you ask a former colleague if they were good, hear yes they were great, and move on having learned nothing. The real version: you talk to someone who managed them directly and ask specific questions, describe a time a project went sideways, what would you have coached them on. The reference answers warmly about their technical skill but goes noticeably quiet and vague when you ask about how they handled feedback or worked under pressure. That silence is the signal. It does not automatically disqualify the candidate, but it tells you exactly what to probe further, information the formality version would never have surfaced.

The Honest Counterpoint

Reference checks are valuable and imperfect, and you should weight them appropriately rather than treating them as definitive. References are usually chosen by the candidate and skew positive, people have off days and personality clashes that unfairly color a reference, and a single lukewarm comment is not proof of a problem. The signal from references is real but noisy, so use it to confirm, probe, or raise questions rather than as a sole verdict, and combine it with the direct evidence of your own evaluation. For roles hired through a vetting partner, much of this diligence is already built into the process (the five-stage vetting process). Take references seriously, read them carefully, and weigh them alongside everything else.

Frequently Asked Questions

How many references should you check for a software engineer?

Two or three, with at least one from a direct manager. More than that rarely adds signal; one reference who worked closely with them beats three distant ones.

How do you verify a reference is real?

Find the person independently on LinkedIn, confirm their dates overlap with the candidate's, and contact them through a company email or main line. Be suspicious if every reference is reachable only by a personal mobile number.

Are reference checks different for LATAM developers?

The questions are the same. Add independent verification, ask for a reference from a remote or US-facing team if one exists, and offer the call in the reference's first language.

What are red flags in a developer reference check?

Long pauses on whether they would rehire, vague answers about a specific skill, references who cannot describe a concrete project, and references you cannot verify outside what the candidate gave you.

The Bottom Line

Checking a developer's references well means treating it as a genuine signal rather than a formality to rush. Ask specific questions about real behavior and situations, which are hard to answer with empty praise, talk to people who actually worked closely with the candidate rather than distant curated contacts, and listen as carefully to hesitation and omission as to the literal words, because references signal through silence. Weigh the result alongside your own evaluation rather than as a sole verdict, and a proper reference check becomes one of the last, most honest signals you get before you commit.

If you would rather start from engineers who have already been through technical vetting, see vetted engineers or request a shortlist.

Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours.

RE

CEO, Ruzora

Roberto is the founder and CEO of Ruzora. He works directly with US startup founders and CTOs on staff-augmentation and software-factory engagements, and personally reviews senior engineer placements.

Senior LATAM engineers

Get a vetted shortlist within 72 hours.

Tell us the role and the stack. Within 72 hours you're reviewing a vetted shortlist of senior LATAM engineers who match it.