The gap between reading and speaking is wider than you expect
A Brazilian senior engineer has read English every working day for a decade. Documentation, Stack Overflow, error messages, RFCs, their own code comments. Written comprehension is rarely the problem.
Speaking is a separate skill acquired separately, and often not at all — a career can be built in the Brazilian domestic market without ever holding a conversation in English. So you will meet candidates who read your architecture document perfectly and struggle to argue about it out loud.
This is why a résumé that says "English: advanced" tells you nothing. Self-assessment in this market is unreliable in both directions: some candidates who write "intermediate" speak fluently, and some who write "fluent" have not spoken English in three years.
Where Brazil actually ranks
On international English proficiency indices Brazil sits in a moderate band — behind Argentina, Portugal and much of Northern Europe, and roughly comparable to its Latin American neighbours other than Argentina. Among software engineers specifically the level is well above the national average, because the profession selects for it.
The honest summary: better than the country-level statistic suggests, worse than a vendor promising "fluent English guaranteed" implies. Anyone selling you a national guarantee is describing their sales script rather than the market.
How to screen for it in fifteen minutes
Ask the candidate to explain a technical decision they made — not to describe their background. Rehearsed answers cover biography, not architecture.
Interrupt with a follow-up question halfway through. Listening comprehension under interruption is the skill that determines whether they can function in a real meeting, and it is invisible in a monologue.
Disagree with something they said and see what happens. The engineer who says "no, that would break because…" in imperfect English is more valuable than the one with flawless grammar who agrees with everything.
Do not screen for accent. It has no relationship to comprehension, and filtering on it removes excellent engineers for no reason.
What improves fastest once they start
Spoken fluency improves quickly with daily use — noticeably within two to three months of regular standups. The plateau is usually confidence rather than vocabulary.
Two things help more than a language course: putting the engineer in meetings where they are expected to speak rather than listen, and writing culture. A team that decides things in writing gives non-native speakers an equal footing on the decisions that matter, and it is a better way to run a distributed team anyway.
Key takeaways
- Written English is rarely the constraint; spoken English usually is.
- Self-reported levels on a résumé are unreliable in both directions.
- Screen with an unscripted technical conversation and interrupt on purpose.
- Ignore accent; test whether they can disagree with you.
- Fluency improves markedly within a few months of daily standups.