How to Get Promoted from T4 to T5 at Lyft

You ship clean code. Your PRs get approved without fuss. You finish your tasks ahead of schedule and pick up extra work when the sprint looks light. But the engineers who got promoted to T5 last cycle weren't doing more of the same work you're doing. They were doing different work.

The T4-to-T5 jump at Lyft is where "productive individual contributor" stops being enough. T5 is where Lyft expects you to lead projects, author technical proposals, and grow the engineers around you. The gap between a strong T4 and a T5-ready engineer shows up in how you spend your time, not how many PRs you merge.

What Changes from T4 to T5

T4 at Lyft is a mid-level software engineer. T5 is Senior. The title changes, and so does what the company measures.

Dimension	T4 (Mid-Level SWE)	T5 (Senior SWE)
Ownership	Owns features end-to-end within your team	Leads projects across teams, scopes work for others
Decision-making	Makes technical decisions within your domain	Drives technical direction for your team and influences adjacent teams
People	Minimal mentorship expected	Actively mentors T3/T4 engineers; grows the team
Scope	Individual contributor with growing complexity	Tech lead scope; responsible for outcomes across a group of engineers
Design work	Contributes to design docs	Authors design docs and drives technical proposals
Independence	Manager gives you problems to solve	You identify the problems worth solving

At T4, someone upstream decides what matters and you execute well. At T5, you figure out what matters, get buy-in, and make it happen through a combination of your own work and the work of others.

How Lyft Promotions Work

Lyft runs biannual performance reviews. These cycles are where promotions, ratings, and compensation adjustments happen.

The process works like this:

1. You write your self-review, documenting your contributions and impact from the past half
2. Engineers you've worked with submit peer feedback
3. Your manager writes their assessment and proposes your rating
4. Calibration: managers compare engineers at the same level and finalize ratings
5. Managers finalize promotion decisions during calibration based on next-level evidence
6. Your manager delivers results in a 1:1

Your manager drives the promotion nomination. They build your case and argue for it during calibration. If your manager doesn't have concrete evidence of T5-scope work, they can't make the argument.

One thing to know about Lyft's process: employees on Team Blind describe it as opaque. Some say the process is driven by relationships rather than a transparent rubric. This means your relationship with your manager matters more than at companies with committee-based promotion decisions. If your manager understands your work and is willing to fight for you, the process works. If they don't, it stalls.

How Long T4 to T5 Takes

Pace	Timeline	What's happening
Fast	~2 years at T4	Strong project fit, visible leadership, clear T5-scope work from the start
Standard	2.5-3 years at T4	Steady growth, building mentorship evidence, expanding scope across review cycles
Slow	3+ years at T4	Something structural: wrong projects, limited scope, or gaps in leadership signal

T4 is a terminal level at Lyft. There's no up-or-out clock forcing the promotion. You can stay at T4 indefinitely, and plenty of engineers do. But compensation growth stalls without a level change because Lyft doesn't offer annual bonuses.

Based on Levels.fyi data, average total compensation at T4 is about $250K. At T5, it's about $330K. That's roughly an $80K jump. Stock grants increase from ~$90K/year to ~$135K/year, which accounts for most of it. Every cycle you sit at T4 without advancing costs real money. Lyft's equity-heavy structure means the gap compounds.

What Actually Gets You Promoted

Lead a project from problem to delivery

The clearest T5 promotion cases at Lyft involve someone who owned a project from problem identification through delivery, coordinating multiple people along the way. You scoped the work, wrote the design doc, broke it into tasks, assigned pieces to teammates, unblocked them when they got stuck, and delivered the result.

If every project on your review is something you contributed to but someone else led, your case reads as strong T4 execution, not T5 readiness.

Author design docs that shape decisions

At T4, you implement designs. At T5, you author them. Your promotion case should include at least one design doc where you identified the problem, proposed the approach, gathered feedback from senior engineers, and drove the decision. The doc doesn't need to describe a massive system. A focused proposal that changed how your team handles a specific problem is enough.

If you've been at T4 for a year and haven't authored a design doc, talk to your manager about which upcoming problems would benefit from a written proposal. Start now.

Mentor a junior engineer with visible results

T5 candidates need evidence that they grow the people around them. The strongest evidence is a concrete story: you mentored a T3 engineer, they shipped their first independent feature, and your manager noticed the change. This doesn't need to be a formal program. Pairing on hard problems, reviewing their design docs with real feedback, helping them debug their first production incident, all of it counts.

What doesn't count: being available to answer questions. That's baseline helpfulness. Mentorship means someone's trajectory changed because of your involvement.

Build cross-team visibility before you need it

T5 work crosses team boundaries. If the first time you talk to engineers on another team is when you need something from them, the collaboration will be harder and slower. Start building those relationships during normal work: review their PRs when they touch shared code, attend their design reviews, show up to cross-team planning sessions.

Lyft's post-layoff engineering org is smaller than it used to be. This is actually an advantage for building cross-team relationships because there are fewer layers between you and engineers on adjacent teams.

Make your contributions easy for your manager to argue

Your manager is comparing you to every other T4 in the org during calibration. If your work is invisible outside your immediate team, your manager has a harder time making your case.

Share project updates in engineering channels. Present technical decisions in broader forums. Make your design docs discoverable. When peer feedback time comes around, people outside your team should have enough context to write something specific about your work.

Mistakes That Keep Engineers at T4

Treating more code as the path forward. The most common T4 trap. Shipping more features faster looks like strong T4 execution, not T5 readiness. T5 is about leverage: leading a project, mentoring someone, driving a technical decision. An engineer who merges 50 PRs but never leads a project or grows another engineer stays at T4.

Waiting for your manager to hand you T5-scope work. Your manager has a full calendar and multiple direct reports. They are not going to find you the perfect leadership opportunity. You need to identify projects where you can lead, propose taking ownership, and negotiate for the scope. Engineers who wait to be assigned T5-level work wait a long time.

Ignoring the relationship factor. Lyft's promotion process is manager-driven, and employees describe it as relationship-dependent. If your manager doesn't understand your work or can't articulate your impact, they can't argue for your promotion during calibration. Have direct conversations about what T5 readiness looks like for you. Ask what evidence would make your case clear. Surface gaps you didn't know about.

Getting downleveled and checking out. Lyft is known for downleveling during hiring. If you interviewed for T5 and received a T4 offer, the recruiter may have hinted at a fast promotion path. But the bar is the same regardless of how you entered the level. Instead of feeling stuck, use the first six months to build the evidence: lead a project, mentor someone, write a design doc. Calibration evaluates your work at Lyft, not your expectations at hire.

Not having the promotion conversation. Many engineers assume their manager tracks their progress toward T5 automatically. Ask directly: "What does T5 readiness look like for me? What evidence would make my case clear in calibration?" This conversation surfaces gaps and tells your manager you're serious. Without it, you might spend a full year working on the wrong things.

Frequently Asked Questions

How long does it take to get promoted from T4 to T5 at Lyft?

Most engineers spend 2 to 3 years at T4 before reaching T5. Strong performers with good project fit and clear leadership evidence can do it in about 2 years. T4 is a terminal level with no forced timeline, but compensation growth stalls without advancement because Lyft doesn't offer annual bonuses.

Is T4 a terminal level at Lyft?

Yes. There's no up-or-out policy at T4. You can stay indefinitely without being managed out. But average total comp at T4 ($250K) is roughly $80K lower than T5 ($330K), and without annual bonuses, the only way to increase your pay is to get promoted.

What's the compensation difference between T4 and T5?

Based on Levels.fyi, average total comp jumps from roughly $250K at T4 to approximately $330K at T5. Stock grants increase from ~$90K/year to ~$135K/year, which drives most of the increase. Base salary rises from ~$161K to ~$195K.

How does Lyft's promotion process work?

Lyft uses biannual performance reviews. Your manager nominates you for promotion, builds your case with evidence from self-reviews and peer feedback, and argues for it during calibration. Calibration compares you against other T4 engineers in the org. Employees describe the process as opaque compared to committee-based systems at companies like Google.

I was downleveled to T4 when I was hired. Does that affect my promotion timeline?

Not formally. The promotion bar is the same regardless of how you entered the level. Downleveling is common at Lyft, especially for candidates with 6-7 years of experience who expected T5. Focus on building evidence: lead a project, mentor someone, write design docs. Calibration evaluates your work at Lyft, not your expectations at hire.

---

CareerClimb tracks your wins as they happen, maps them to what Lyft evaluates in calibration, and shows you which evidence gaps remain before your manager builds your case. When the next review cycle opens, your self-review writes itself from documented impact. Download CareerClimb