How to Get Promoted from L5 to L6 Software Engineer at Uber

You've been at Uber L5a (Senior Software Engineer) for three years. Your performance ratings are consistently strong, maybe even a 4 on Uber's 1-5 scale. You're the go-to person on your team for hard technical problems. And yet, every time L5b (Staff) comes up, your manager says something about "cross-team impact" and a "multi-half north star vision" without giving you a concrete picture of what that means. Meanwhile, you've heard from other L5a engineers on Team Blind that some people have been stuck at L5a for four or five years despite excellent work. That's the reality of this transition.

The L5a to L5b jump at Uber is the hardest common promotion on the engineering ladder. L5b carries the "Staff Software Engineer" title (renamed from "Senior Software Engineer II" in April 2022 when Uber restructured its levels). It requires a fundamentally different kind of work: cross-team coordination, architectural influence, and strategic thinking about your technical area over multiple quarters. Based on Levels.fyi, median total comp moves from roughly $455K at L5a to $740K at L5b. The jump is massive because the role is rare.

What Changes from L5a to L5b

Dimension	L5a (Senior)	L5b (Staff)
Scope	Multi-service projects within team scope	Complex cross-team projects spanning organizations
Design	Makes design trade-offs for team systems	Drives architectural decisions across multiple teams
Vision	Executes on team priorities	Has a "multi-half north star vision" — sets direction for the technical area
Coding	Primary IC, writing substantial code	Significantly less coding; more design, review, and coordination
Influence	Strong within team	Influences without authority across teams and orgs
People	Coaches L3/L4 engineers	Develops L5a engineers, shapes engineering culture

The fundamental shift: at L5a, you're the strongest player on your team. At L5b, you're the person multiple teams come to for technical direction. You stop being measured by what you build and start being measured by the outcomes you create through others.

How This Promotion Works

The hardest common jump. On Team Blind, Uber engineers consistently describe L5a to L5b as the hardest promotion below the very senior levels. Some engineers report being stuck at L5a for 4+ years with strong performance bonuses. The bar isn't just about doing L5b work — it's about sustaining it across multiple review cycles and having the structural factors align.

"Multi-half north star vision." This phrase comes up repeatedly in L5b expectations. It means you need to articulate where your technical area should be heading over the next 2-3 review cycles and make concrete progress toward that vision. Not a roadmap your manager gave you. A direction you identified and drove.

Staff+ promotion committees. Some Uber engineering organizations use a separate committee of Staff+ engineers (rather than just managers) to evaluate promotions to L5b and above. This adds rigor but also means your work needs to be legible to senior engineers who don't work on your team.

Structural factors matter. Budget, headcount, and organizational need all affect L5b promotions. You can meet the performance bar and still not get promoted in a given cycle due to constraints. In a typical 300-person engineering org at Uber, only about 5 engineers sit at L6 (the level above L5b). That gives you a sense of how rare these positions are.

What Actually Gets You Promoted

Run projects that span team boundaries

The defining L5b behavior is sustained cross-team impact. Find problems that sit between teams: migration projects, infrastructure improvements, platform work that affects multiple services. These are the problems nobody owns because they span organizational boundaries.

Talk to your manager about creating this kind of scope. If your current team doesn't have cross-team projects, you may need to identify the opportunity yourself.

Develop a multi-quarter technical vision

Write up where your technical area should be heading. Not a list of features for next quarter. A directional thesis: what's broken or fragile today, what will break tomorrow if nobody addresses it, and what the architecture should look like in a year. Bring this to your manager, skip-level, and the senior engineers in your org.

Influence without authority

L5b engineers get other teams to adopt their technical approaches not through org chart power but through earned trust. Review code across teams. Participate in architecture reviews beyond your immediate team. When someone proposes an approach with downstream risks, offer a better alternative. Build the reputation that makes people seek your input.

Invest in developing L5a engineers

L5b is where growing other senior engineers becomes an explicit expectation. Mentor an L5a through a challenging architectural decision. Help a strong senior engineer develop the cross-team skills they'll need for their own L5b case.

Mistakes That Stall L5a Engineers

Doing more excellent L5a work. The most common trap. You're shipping at an impressive pace, your designs are clean, your code reviews are thorough. But it's all team-scoped. No amount of excellent L5a output adds up to L5b. The calibration committee evaluates scope, not volume.

Waiting for cross-team work to be assigned. L5b-scope projects rarely arrive on your backlog. You typically have to identify the problem, propose the solution, and get buy-in from multiple teams. If you're waiting, you'll wait indefinitely.

Spending too much time coding. L5b engineers write significantly less code than L5a engineers. If you're still the person doing all the hard technical work yourself, you're operating at L5a. The shift is toward design, review, coordination, and influence.

No peer feedback from outside your team. If calibration only hears from people on your team, the verdict is predictable: strong L5a. You need engineers and managers from other teams who can speak to your cross-team impact.

Not talking to your manager about it. L5a is terminal. Your manager may assume you're content. If you want L5b, say so directly. Ask what gaps exist and what evidence calibration would need.

Frequently Asked Questions

How long does it take to get promoted from L5a to L5b at Uber?

Typical timeline is 3 to 4+ years. Some engineers do it in 2 to 3 years with exceptional cross-team impact. Many excellent L5a engineers stay at L5a permanently — it's a terminal level with no pressure to advance. The pace depends entirely on finding cross-team scope and having the structural factors align.

What's the pay difference between L5a and L5b at Uber?

Based on Levels.fyi, median total comp jumps from roughly $455K at L5a to $740K at L5b. This is one of the largest jumps on Uber's ladder, driven almost entirely by RSU grants. Bonuses can double with a top rating.

What's the difference between L5b and L6 at Uber?

L5b (Staff Software Engineer) handles complex cross-team projects. L6 (also titled Staff Software Engineer in some sources, or Senior Staff) operates at the organization level, shaping architecture and standards. In a 300-person org, there might be ~5 engineers at L6 and only ~1 at L7. The distinction is scope: L5b is cross-team, L6 is cross-org.

Should I stay at L5a or push for L5b?

Honestly, for many engineers, L5a is the right place. The work at L5b is fundamentally different — less coding, more coordination, more politics. If you love deep technical work on your team's problems, L5a is where that work lives. Push for L5b only if you genuinely want to shape technical direction across teams, not just because of the compensation.

---

CareerClimb tracks your wins, maps them to what Uber's calibration evaluates, and tells you exactly what evidence you're missing. When the next review cycle opens, your case is already built. Download CareerClimb