What English Level Do You Actually Need? A Role-by-Role Guide for Latin America Hires

Mexico illustrates the trap well. National English proficiency in Mexico sits in the “low” band on the EF English Proficiency Index, yet Mexico is also one of the most established outsourcing and nearshoring destinations for US companies, with entire sectors of English-fluent professionals in tech, finance, and customer operations.

Both facts are true at once, because national averages describe the whole population, not the sector you are hiring from. A hiring manager who reads the national score and either writes off Mexico or demands unnecessary fluency for a backend engineering role is making the same mistake from two different directions: treating a population statistic as a job requirement.

The fix is not a better proficiency score. It is asking a more specific question: what does this particular role actually require, and how would you know if a candidate meets it?

{{recruiting-embed}}

English Requirements Are a Role Question, Not a Country Question

Every Latin America hiring conversation eventually turns to English level, and it is usually framed as if the answer lives at the country level: Argentina is strong, Honduras is weak, and so on. That framing produces bad job posts. A backend engineer who reads code comments and writes async Slack updates needs a different bar than a customer support agent taking live calls from US customers, and the two roles should not share a job description requirement just because they are hired in the same country.

The more useful frame sorts roles by what English actually has to do in the job, not by title or seniority.

A Four-Tier Framework for English Requirements

Sort the role first, then set the bar. These four tiers cover the large majority of roles US companies hire for in Latin America.

Tier 1, Internal-only

Example roles: backend engineer, data analyst, andanalyst, QA engineer working with a Spanish-speaking or bilingual team.

What English has to do: read documentation and understand occasional English code comments or tickets.

Realistic bar: reading comprehension; conversational fluency not required.

Tier 2, Written, Not Spoken

Example roles: DevOps engineer, technical writer, async-first contributor on a distributed team.

What English has to do: write clear Slack messages, PR descriptions, and async updates.

Realistic bar: strong written English; verbal fluency secondary.

Tier 3, Customer-facing, Written

Example roles: support ticket agent (email or chat), technical account manager handling written correspondence.

What English has to do: write clear, professional, error-free English in real time.

Realistic bar: high written fluency; near-native clarity expected.

Tier 4, Customer-facing, Spoken

Example roles: sales development rep, phone-based customer support, and account executive.

What English has to do: real-time spoken conversation with US customers or prospects.

Realistic bar: high spoken fluency, including idioms and tone; often the highest bar in the org.

How to Test English Level Without Trusting Self-Report

Self-reported English level on a resume or in a screening call is close to useless as a signal. Almost every candidate rates themselves “fluent” or “advanced,” and the gap between self-rating and actual on-the-job performance is where most English-related hiring mistakes originate.

A composite example makes the pattern concrete. A candidate for a customer-facing, spoken role (tier four) rates themselves “fluent” on their resume. A structured phone screen conducted entirely in English, with no advance notice of the topic, reveals hesitation, translation lag, and difficulty with idiomatic phrasing under real-time pressure.

The same candidate would likely test well on a written assessment, because written English allows time to compose and revise. The mismatch is not dishonesty. It is that “fluent” means something different to the candidate, who is comparing themselves to their own community, than it does to a hiring manager comparing them to a native US speaker on a live sales call. 

For a more structured approach to evaluating workplace English, employers can use Cambridge English’s Workplace English Tool to identify the language skills and level required for a specific role.

Three practical ways to test for the actual tier you need, rather than a self-reported label. An English fluency test for hiring that matches the role instead of a generic screening call:

1. Match the test format to the tier. For written tiers, use a written exercise, a sample email response, or a short async Slack-style update, not a live call. For spoken tiers, run a live, unscripted phone or video screen where the candidate cannot prepare answers in advance.
2. Test under realistic pressure. A candidate who sounds fluent in a scheduled, prepared interview may behave differently on an unplanned customer call. Where possible, simulate the actual working condition: a live objection-handling scenario for sales, a mock support ticket with an irritated customer for support roles.
3. Separate English assessment from role assessment. A strong candidate can fail an English bar that was set too high for the role, and a weak candidate can pass a bar that was set too low. Score English proficiency as its own dimension against the tier the role actually requires, not as a proxy for overall candidate quality.

English Proficiency by Country: 2026 Data

Country-level English proficiency Latin America data is a useful sanity check once you know the tier you are hiring for, not a substitute for role-specific testing. The EF English Proficiency Index (EF EPI) 2025 report, which scores adult English proficiency across more than 100 countries and territories, gives a current baseline for the Latin America countries US companies hire from most.

Argentina: EF EPI 2025 score 575, high proficiency band and regional leader. Hiring implication: strong candidate pool across all four tiers, including spoken customer-facing roles.

Costa Rica: 516, moderate proficiency. Established outsourcing hub; solid pool for tiers two through four.

Colombia: 480, low proficiency. Strong for tiers one and two broadly; tier three and four candidates concentrated in Bogota, Medellin, and outsourcing-sector talent.

Chile: 517, moderate proficiency. Similar profile to Colombia; sector-specific rather than population-wide strength.

Peru: 519, moderate proficiency. Growing outsourcing sector; screen carefully for tiers three and four.

Brazil: 482, low proficiency, but not a reliable read on hiring pools. Brazil’s deep, sector-specific talent ecosystem, especially in tech and finance, means the national score understates available tier one through three talent; Brazil should be evaluated on its own terms, not benchmarked against Spanish-speaking countries.

Mexico: 440, very low proficiency nationally. The national score reflects the broad population; established nearshoring and technical sectors provide strong tier one through three candidates; tier four requires more deliberate sourcing and testing.

Honduras: 553, high proficiency, and second in the region after Argentina. Strong for customer-facing English roles, though the overall talent market is smaller than the larger economies.

Source: EF English Proficiency Index 2025, EF Education First.

Confidence: primary published index, updated annually; scores are national averages and should be read as a directional baseline, not a substitute for role-specific candidate testing.

Setting the Requirement in Your Job Post

Once you know the tier, write the job post to match it rather than defaulting to “fluent English required” out of habit.

1. Name the tier explicitly in plain language: “This role requires strong written English for async Slack and documentation; verbal English is not required,” rather than a generic fluency line.
2. State what the English is actually used for, not just the level. “You will write customer-facing email responses” tells a candidate more than “advanced English” does, and it self-selects candidates who can accurately judge their own fit.
3. Build the testing step into your process before the offer stage, using the format-matched approach above, so the requirement in the job post is actually verified rather than assumed from the resume.

{{consultation-embed}}

Frequently Asked Questions

What English Level Do I Need for a Latin America Hire?

It depends entirely on the role, not the country. Internal-only roles like backend engineering often need only reading comprehension. Written, non-customer-facing roles need strong written English. Customer-facing written roles need near-native written clarity. Customer-facing spoken roles, like sales or phone support, need real-time spoken fluency, which is the highest bar and should only be required where the role actually demands it.

Which Latin American Countries Have the Strongest English Proficiency?

According to the EF English Proficiency Index 2025, Argentina leads the region, with Honduras, Peru, Chile, and Costa Rica in a moderate band. Colombia, Brazil, and Mexico score lower nationally, but all have deep, sector-specific English-fluent talent pools in technology, finance, and outsourcing that a national average does not capture.

Can I Trust a Candidate’s Self-Reported English Level?

Not reliably on its own. Almost all candidates describe themselves as fluent or advanced, and the gap between self-rating and actual performance, especially under real-time spoken pressure, is a common source of hiring mistakes. Test with a format that matches the tier the role requires: written exercises for written roles, live unscripted calls for spoken customer-facing roles.

Does Brazil Have Weaker English Than Spanish-Speaking Latin America Countries?

Brazil’s national EF EPI score is lower than several Spanish-speaking countries in the region, but this reflects the whole population, not the hireable talent pool. Brazil has an established, deep talent ecosystem in tech and finance with strong English speakers, and it should be evaluated on its own terms rather than benchmarked directly against Spanish-speaking countries, given its distinct labor code and market structure.

Should Every Customer-Facing Role Require Spoken English Fluency?

Only if the role involves real-time spoken conversation with US customers or prospects, like sales calls or phone support. A customer-facing role handled entirely through email or chat needs strong written English, which is a different and often more available skill than spoken fluency.

How Do I Test English Level in an Interview Without Wasting the Candidate’s Time?

Match the test format to the tier the role needs. For written tiers, use a short written exercise like a sample email response. For spoken tiers, run a live, unscripted phone or video conversation rather than a scripted, prepared one, since real-time pressure is what actually predicts on-the-job performance.

How Does Lupa Evaluate English Proficiency During Hiring?

We define the specific English tier the role requires as part of the role profile, then test for it directly with a format that matches how the language will actually be used on the job, rather than relying on resume self-reports or a generic fluency requirement.