In the United States "senior" is a rung with more rungs above it — staff, principal, distinguished. In Brazil it is usually the top of the individual-contributor ladder, which runs júnior, pleno, sênior and then stops. That one difference causes most of the mis-levelling: the same word marks the middle of one ladder and the end of the other. A Brazilian sênior can be a strong mid-level engineer four years in, or someone doing staff-level work who has held the title for eight years, and the two CVs can look almost identical.
The fix is not a conversion table. It is to read four other things first: the start date, the employer type, the verbs in the bullets, and the answer to one written question.
Why do the two ladders not line up?
Júnior, pleno and sênior are not a software convention. They are the general job-classification scale Brazil uses to name salary bands across professions — the same three rungs turn up in accounting and civil engineering job ads — and software inherited them intact. Two consequences follow.
"Pleno" has no English word. A pleno writing for a U.S. reader must translate a rung that does not exist in your market. The careful ones write "mid-level"; the pragmatic ones write "senior", on the reasonable grounds that they are certainly not junior. Both arrive looking the same.
The ladder stops, so the title stops moving. Where nothing sits above sênior, promotion runs out while scope keeps growing, and you get the eight-year sênior whose last three years were architecture and mentoring. The employers that have adopted the U.S. ladder are mostly newer product companies and the Brazilian offices of foreign firms. Everywhere else, the ceiling is the word you are calibrating.
What do the Brazilian titles actually mean?
| On the CV | Usual reading | What to check |
|---|---|---|
| Estagiário | Intern, usually still enrolled; typically paid, 12–24 months | Overlap with the degree dates |
| Pleno | Mid-level; a real middle rung, not a mistranslation | Shipping without a defined backlog |
| Sênior | Five years, or the rest of a career | Everything else below |
| Especialista | Where it exists, the rung above sênior — nearest to U.S. staff | Whether that employer had the rung |
| Coordenador / Gerente | People management, not coordination | When they last wrote code |
| Arquiteto de software | In consultancies, often standards and design documents | Recent hands-on code |
One word deserves its own warning. Analista — as in Analista de Sistemas — is the generic Brazilian term for a professional individual-contributor role, the noun the júnior/pleno/sênior scale attaches to. It does not mean business analyst: "Analista de Sistemas Sênior" is a hands-on engineer in almost every case, and screening it out as non-technical removes a large part of the experienced market.
Why does "eight years of experience" start earlier in Brazil?
Computing degrees run four to five years, with a paid internship inside a real company as the normal path through them rather than a summer extra. Plenty of engineers work twenty to thirty hours a week in a production codebase from their second year, so employment dated 2018 against a 2021 graduation is not padding. Count it deliberately: full-time years from the first post-internship role, with the internship years read as an early start rather than as experience. That usually moves the total down by one to two years — the gap that makes a Brazilian sênior look over-titled when they are not.
Two related non-signals. An unfinished degree followed by continuous employment is ordinary here. So is a line naming the person's own company as the employer: most senior Brazilian engineers invoice through an entity they own, which is a payment arrangement rather than a freelance career, as the piece on PJ contracting explains.
What does the employer type tell you that the name cannot?
You cannot read a Brazilian CV by logo, and learning the local prestige order is a poor use of your time. What the page gives you instead is the kind of employer.
- Allocation firms — consultoria, or what Brazilians call a fábrica de software. The tell is one employer with client projects listed underneath, or a run of six-to-twelve-month engagements. This is the most misread pattern on a Brazilian CV: you see six jobs in three years and screen for instability, when the page shows one employer and six allocations. Read that as a project list.
- Banks, payment institutions and fintechs. Brazilian retail banking runs on real-time rails used nationwide, so many engineers there have production experience with regulated, always-on systems. Those CVs skew strong on reliability and audit trails, thinner on greenfield product work. The market guide covers where the depth sits by sector.
- Captive centres — the Brazilian office of a foreign company. The engineer may be excellent and may never have chosen an architecture, because scope was set on another continent. Check which decisions were theirs.
- Product companies and startups. Closest to what you expect, and where title inflation is likeliest: a young company promotes to sênior on its own schedule.
That is as far as the page takes you. Turning the classification into a judgement is interview work, and the piece on interviewing has the questions.
Is a short tenure a red flag here?
Usually not, and this is where a U.S. screen does the most damage. Changing employer every eighteen to twenty-four months is common in this market, because internal increases have tended to lag what the market pays someone who switches. A ten-year career assembled from two-year stints is an ordinary CV. What is worth reading is whether the moves climbed in scope, and whether one stint ran three years or more — not as a loyalty test, but because staying long enough to live with your own decisions is different from arriving, shipping and leaving.
What about the education line?
- Análise e Desenvolvimento de Sistemas is a tecnólogo degree: accredited higher education, typically two to three years, vocational in emphasis. Not a bootcamp certificate — locally, a normal route into the profession.
- Ciência da Computação, Engenharia de Computação, Sistemas de Informação are the four-to-five-year bachelor's routes, and what most senior engineers hold.
- A public university — the federal and state institutions — charges no tuition and admits by competitive entrance exam. That selection signal is invisible abroad. Not a reason to hire, but a reason not to discount a CV for carrying no name you recognise.
How do you level someone in four lines?
- Count full-time years from the first post-internship role, not from the first date on the page.
- Classify the employer type, not the employer. Allocation firm, bank, captive centre, product company.
- Read the verbs, ignore the technology list. "Owned", "designed", "was on call for", "migrated", "chose" carry level. Thirty tool names carry none — long tool lists are a local CV convention, not a claim of depth.
- Ask one question in writing. "What is the most consequential technical decision you made in the last two years, and what would you do differently?" The answer levels people better than any title, in either market.
Then match the answer against a scope you wrote down before opening the first CV — one sentence per band. A mid-level engineer ships well-scoped features independently and needs a defined backlog; a senior owns a service or product area end to end and reviews other people's code; a tech lead sets architecture, leads a squad and deals with your stakeholders. Those three sentences are how the rate card at HireBrazilDevs is banded, at $3,500, $4,900 and $6,400 a month; the pricing page shows the year ranges beside each. Pick the sentence before you open any CVs and most of the levelling problem disappears: you are matching scope to scope, not word to word.
Where does the CV stop being useful?
At the English line, which is a claim rather than evidence. "Inglês avançado" is a self-assessment against a language-school ladder rather than CEFR, and it skews conservative on reading and writing and optimistic on speaking — the opposite of what remote engineering demands, since the job is mostly written. The English guide covers what each level supports day to day.
It also stops at the personal-data block: city, age, sometimes a photo. That is a leftover local convention, not a signal.
Level the scope, not the word. Count from the first real job, classify the employer type, read the verbs, ask the one decision question in writing. The rest of the gap between these two markets is noise on the page.