How companies define levels

Titles don't travel

Juliana had been "desenvolvedora pleno" at a Curitiba SaaS company for three years when the email landed. A US remote startup wanted to bring her on as "Software Engineer II." Same person, same stack, three years of the same kind of Rails work. Two different words for what she does. That's not a translation error. Every company builds its own ladder. "Pleno" at a fifty-person Curitiba SaaS company describes a different scope of work from "mid-level" at a remote-first startup. Both differ again from "L4" or "E4" or "SDE II" at a company that numbers its levels instead of naming them. The title on an offer letter was never a portable unit of measurement. What travels between companies is the work itself, and learning to read that work correctly, in whatever vocabulary a given company happens to use, is what this course is for.

The axes underneath every ladder

Strip the label off any leveling framework and you find the same handful of axes repeated, in different words, at almost every company that bothers to write one down. Scope: does your work touch a single task, a feature, a whole system, or a slice of the organization. Autonomy: do you need direction to know what to build next, or do you set that direction yourself, for yourself and sometimes for others. Impact: does your work move your own output, your team's, or several teams' at once. Technical depth: how far into the guts of a system can you reason correctly, under pressure, without guessing. Influence: can you move a decision for someone who doesn't report to you and isn't required to listen to you at all. A framework that lists these five, or something close to them, per level is describing the same underlying shape as a company that just says "pleno" and leaves the rest implicit. The difference is only whether the shape got written down.

What a promotion committee looks for

A promotion committee isn't grading how hard you worked or how long you've been in the seat. It's asking whether you're already operating at the next level, consistently, and whether that's visible to people who don't sit next to you. Three things carry the most weight. Demonstrated impact at the target level, not promised impact. A committee wants to see you already doing senior-shaped work, not a plan to start once the title changes. Scope that has grown, measured against what the role asked of you a year ago, not against what a job posting says a senior does in the abstract. And legibility: work that's written down, reviewable, visible to someone outside your immediate team, because a committee can't credit impact it has to take on faith. Good work that stays invisible to everyone but your closest teammates is real work. But it isn't yet a promotion case, and that gap between doing the work and making it legible is where most stalled promotions live.

The climate has tightened

Across 2025 and 2026, internal promotion rates have generally tightened. Smaller engineering headcounts, a higher bar for the next level, and committees that meet less often than they used to at many companies. None of that means the axes above changed; scope, autonomy, impact, depth, and influence are still what gets evaluated. What changed is the denominator: fewer promotion slots relative to the number of engineers who'd qualify by any reasonable read of those axes. That's part of why the external route (interviewing somewhere else and arriving at the next level directly) has become more common than it used to be. Internal growth still matters; the two paths to the same destination now move at noticeably different speeds at a lot of companies.

Down-leveling on hire

Juliana's offer names a level, "Software Engineer II," and it's worth asking directly whether that maps above, below, or level with her current pleno title. Down-leveling on hire is common and rarely explained unless you ask. A company with a stricter, more explicit ladder than the one you're leaving often maps your current title conservatively. Your work didn't regress; their framework draws finer lines than your last company's, or weighs a different axis more heavily. The two direct questions worth asking any company offering you a level are. How was this level decided from what you showed in the process, and what specifically is the bar for the next one up. Both questions are completely normal to ask before accepting, and a company that can't answer either one clearly is telling you something about how seriously it takes its own ladder.

Brazil layer, global layer

None of this erases the Brazilian layer underneath it. Plenty of Brazilian companies run pleno and sênior as real, meaningful distinctions with their own local expectations. Scope inside a Brazilian team, influence inside a Brazilian org chart, a promotion cycle that runs on Brazilian budget calendars. A remote ladder at a foreign company sits on top of that, not in place of it. It has its own numbering, its own committee, and often its own bar for what counts as senior-shaped work. Juliana isn't choosing between two abstract systems. She's choosing whether to keep building a case inside a ladder she already understands, or start building one inside a ladder she's only seen from the outside, in an offer letter, so far. Neither ladder is more "real" than the other; they're just measuring the same underlying axes with different rulers.

Where this course goes

Lesson 2 teaches you to read an actual leveling framework row by row and gather evidence for each behavior it names. Then you turn what you find into a written promotion case months before a cycle opens. Including what to do when no framework exists at all. Lesson 3 covers the equity basics behind an offer like the one Juliana received. Options, strike price, vesting, and the questions worth asking about any grant before you compare it to a salary. Lesson 4 puts promotion and switching side by side and works out, concretely, when one beats the other. Lesson 5 covers counteroffers and competing offers, and lesson 6 covers working remotely from Brazil for a company abroad (PJ contracts and taxes). Lesson 7, "Your next move: putting it all together," runs the whole decision as one piece.