How to Get Promoted from T5 to T6 at Lyft
You're a strong Senior engineer. You lead projects, mentor junior engineers, and your team trusts your judgment on technical decisions. Your manager gives you good reviews. But when promotion season comes around, you stay at T5.
The T5-to-T6 jump at Lyft is a different kind of transition than T4-to-T5. Moving from mid-level to Senior is about shifting from execution to leadership. Moving from Senior to Staff is about shifting from team leadership to organizational influence. The skills that made you a great T5 will not, by themselves, get you to T6. In some cases they'll hold you back.
What Changes from T5 to T6
T5 at Lyft is Senior Software Engineer. T6 is Staff Engineer. The title changes, and the scope of what counts as "your work" gets much wider.
| Dimension | T5 (Senior SWE) | T6 (Staff Engineer) |
|---|---|---|
| Ownership | Leads projects within your team, scopes work for others | Oversees multiple projects across teams |
| Scope | Team-level; responsible for outcomes across a group of engineers | Organization-wide; sets technical direction for multiple teams |
| Decision-making | Drives technical direction for your team | Shapes technology strategy across the engineering org |
| People | Mentors T3/T4 engineers | Develops senior engineers; grows organizational talent |
| Design work | Authors design docs for team projects | Drives architectural decisions that affect multiple teams |
| Daily work | Codes regularly, leads projects | Less coding; more design reviews, strategy, cross-team coordination |
| Problem-finding | Identifies problems worth solving for your team | Creates scope by finding problems no one has named yet |
At T5, your manager or your director points you at important problems and you solve them well. At T6, you find the problems. You see a gap in the architecture, a scaling bottleneck that will hurt in six months, a process that wastes engineering time across teams. Then you build the case for fixing it, recruit the people, and make it happen. Nobody assigned this to you. Nobody would have if you hadn't surfaced it.
How Lyft Promotions Work at the Staff Level
The mechanics are the same biannual review cycle as T4-to-T5, but the bar is higher and the openings are fewer.
- You write your self-review documenting organization-level impact
- Engineers across teams submit peer feedback
- Your manager writes their assessment and proposes your rating
- Calibration: managers compare Senior engineers and evaluate Staff-level evidence
- Managers finalize promotion decisions during calibration
- Your manager delivers results
At the Staff level, your manager's advocacy matters even more. They need to argue that your impact extends beyond the team, that you're operating at organizational scope, and that you've been doing it consistently for multiple review cycles. One strong half isn't enough. Calibration at this level looks for sustained evidence.
Lyft's engineering org is smaller than FAANG companies. This means fewer Staff openings exist at any given time. Even if you're doing T6-scope work, the promotion may take longer because the number of slots is constrained. This isn't something you can control, but it is something to factor into your timeline.
How Long T5 to T6 Takes
| Pace | Timeline | What's happening |
|---|---|---|
| Fast | ~2.5 years at T5 | Exceptional project fit, clear organizational impact, visible architecture work |
| Standard | 3-5 years at T5 | Building cross-team influence, accumulating multi-cycle evidence |
| Slow | 5+ years at T5 | Structural barriers: limited scope, few Staff openings, impact stays team-bound |
T5 is a terminal level. Most Senior engineers at Lyft stay at T5 for their entire tenure. There's no pressure to advance, and many engineers build fulfilling careers without reaching Staff. But the compensation difference is large enough that the question comes up.
Based on Levels.fyi data, average total compensation at T5 is about $330K. At T6, it's about $455K. That's a $125K jump, with stock grants nearly doubling from ~$135K/year to ~$230K/year. This is the largest single-level compensation increase in Lyft's engineering ladder.
What Actually Gets You Promoted
Work through others instead of doing everything yourself
This is the hardest shift for strong Senior engineers. You built your career by being the person who ships. At T6, your value comes from making five or ten engineers more effective, not from writing more code yourself.
This means delegating projects you could do faster alone. It means spending your time in design reviews, architecture discussions, and 1:1s with other Senior engineers instead of writing the implementation. It means your name isn't on the most important PR in the project, but you're the reason it exists.
If you catch yourself thinking "it would be faster to just do it myself," you're operating at T5 scope.
Drive technical direction beyond your team
T5 engineers own technical direction within their team. T6 engineers shape it across the org. The evidence needs to be concrete: a design doc that changed how three teams approach a shared problem, an architecture review process you created that multiple teams adopted, a technical standard you proposed and implemented across services.
Find the problems that sit in the gaps between teams. Those are the problems nobody owns, and they're where Staff-level impact lives. At Lyft specifically, the post-layoff org restructuring created new gaps between teams. Systems that used to be maintained by dedicated teams now need cross-team ownership. This is where T6-scope work shows up.
Create scope instead of executing on assigned scope
At T5, your manager or director gives you a hard problem and you solve it. At T6, you find the hard problem. You notice that on-call rotations are burning out engineers because alerting is noisy. You identify that a shared library has become a bottleneck for three teams shipping independently. You recognize that a data pipeline designed for 10x the current load will fail at 50x.
Then you propose the fix, get buy-in from leadership, and lead the effort across teams.
The key distinction: nobody asked you to do any of this. You saw the problem, quantified it, and convinced people it mattered.
Develop other Senior engineers
At T5, you mentor T3 and T4 engineers. At T6, you develop T5 engineers. This is a meaningful difference. Senior engineers don't need help debugging or writing better code. They need help thinking about their scope, identifying the right problems, and positioning their work for visibility.
The evidence your manager needs: a T5 engineer whose trajectory changed because of your involvement. They took on bigger projects, expanded their scope, or got promoted, and you can point to specific conversations or collaborations where you influenced that.
Build relationships with leadership
Staff promotions require buy-in beyond your direct manager. Your skip-level manager, other engineering managers, and directors need to know your work and your impact. If the only person who can argue for your promotion is your direct manager, the case is fragile.
Present at engineering all-hands. Write technical blog posts or postmortems that circulate beyond your team. Attend cross-team architecture reviews and contribute substance. Make your work visible to people who will be in the room during calibration.
Mistakes That Keep Engineers at T5
Solving harder problems instead of bigger problems. The most common T5 trap. You take on increasingly complex technical challenges within your team, and you solve them well. But the scope stays team-level. T6 is about breadth of impact, not depth of difficulty. An engineer who solves a moderate problem that affects five teams has a stronger Staff case than one who solves a brilliant problem that affects one team.
Continuing to be the best coder on your team. If you're still the person who writes the most code, reviews the most PRs, and ships the most features, you're demonstrating T5 excellence. T6 requires a different kind of output: architecture decisions, cross-team standards, organizational improvements. You need to let go of being the top individual contributor and start being the person who makes everyone else more effective.
Not building influence without authority. Staff engineers lead without managing anyone. You have no direct reports, no hiring power, no performance review authority over the people you need to influence. If you can only get things done through your own manager's authority, you haven't demonstrated T6-level leadership. Build relationships with engineers and managers on other teams. Earn trust through technical credibility, not org chart position.
Waiting for a Staff-shaped project to appear. There is no project labeled "this will get you to Staff." You create Staff-level scope by identifying cross-team problems and proposing solutions. If you're waiting for someone to hand you organizational-scope work, you're waiting for something that won't happen.
Underestimating the timeline. The T5-to-T6 transition takes longer than T4-to-T5 at every company, and Lyft's smaller engineering org makes it longer still. There are fewer Staff slots. You need multiple cycles of sustained evidence. If you set your expectations for a two-year path and it takes four, the frustration can cause you to disengage. Plan for a longer timeline and focus on the work itself.
Frequently Asked Questions
How long does it take to get promoted from T5 to T6 at Lyft?
Most engineers who reach T6 spend 3 to 5 years at T5. Some do it in about 2.5 years with exceptional project fit and clear organizational impact. T5 is a terminal level, and most Senior engineers stay there for their entire tenure at Lyft. The smaller engineering org means fewer Staff slots compared to FAANG companies.
What's the compensation difference between T5 and T6?
Based on Levels.fyi, average total comp jumps from roughly $330K at T5 to approximately $455K at T6. Stock grants nearly double from ~$135K/year to ~$230K/year. This is the largest single-level comp increase in Lyft's ladder.
Is T5 a terminal level at Lyft?
Yes. Most Senior engineers stay at T5 indefinitely. There's no up-or-out pressure. Many engineers build long, successful careers at T5 without pursuing Staff. The decision to go for T6 should be driven by your interest in organizational-scope technical leadership, not just compensation.
What's different about Staff promotion compared to the T4-to-T5 jump?
T4-to-T5 is about shifting from execution to leadership within your team. T5-to-T6 is about shifting from team leadership to organizational influence. The scope expands from your team to multiple teams. The work shifts from leading projects to setting technical direction. And you need to create scope rather than execute on scope someone gave you.
How many Staff engineers does Lyft have?
Lyft does not publish exact headcount by level. Based on Levels.fyi submissions and Team Blind discussions, Staff engineers (T6) make up a small percentage of the engineering org, fewer proportionally than at larger companies like Google or Meta. This means fewer openings and a more competitive promotion path.
CareerClimb tracks your organizational-scope wins as they happen, maps them to what Lyft evaluates at Staff calibration, and shows you which evidence gaps remain. When your manager builds your T6 case, every cross-team impact and architecture decision is already documented. Download CareerClimb
Are You Ready to Make This Jump?
Get a personalized score and find out what's holding you back.
8 questions · about 2 minutes · free score
1 of 8
