How to Get Promoted from E4 to E5 at DoorDash

You've been at E4 for over a year. Your code ships on time. Your PRs get approved without drama. But when you look at what senior engineers on your team actually do, you notice a gap that has nothing to do with writing better code. They run projects. They decide what gets built. They pull junior engineers through problems instead of solving everything themselves.

That gap is the E4-to-E5 jump at DoorDash. E5 is where DoorDash expects you to lead. The difference between "strong E4" and "ready for E5" shows up in how you spend your time, not how much you produce.

What Changes from E4 to E5

E4 at DoorDash is a mid-level software engineer. E5 is Senior. The title changes, and so does what the company measures.

Dimension	E4 (Mid-Level SWE)	E5 (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 E3/E4 engineers; grows the team
Scope	Individual contributor with growing complexity	Tech lead scope; responsible for outcomes of a group of 5+ 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

The core shift: at E4, someone upstream decides what matters and you execute well. At E5, 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 DoorDash Promotions Work

DoorDash runs biannual performance reviews with stack ranking. This is the mechanism that determines promotions, ratings, and compensation adjustments.

The cycle runs like this:

1. You write your self-review, documenting contributions and impact from the past half
2. Peer feedback is collected from engineers you've worked with
3. Your manager writes their assessment and proposes your rating
4. Stack ranking: engineers are evaluated relative to peers at the same level
5. Calibration finalizes ratings and promotion decisions
6. Your manager delivers results in a 1:1

Stack ranking means your performance is measured against other E4 engineers, not against an abstract rubric. Roughly 15% of engineers land in the bottom tier during each cycle. This creates real pressure, and it shapes how you should think about your promotion case: you're not just arguing that you meet E5 criteria, you're showing that your contributions stand out relative to every other E4 in the org.

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 E5-scope work, they can't make the argument regardless of how good your code is.

How Long E4 to E5 Takes

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

E4 is a terminal level at DoorDash. There's no up-or-out clock forcing the promotion. You can stay at E4 indefinitely, and many engineers do. But compensation growth stalls, and the gap between E4 and E5 total comp is large enough to notice.

Based on Levels.fyi data, median total compensation at E4 is about $273K. At E5, it's about $386K. That's a $113K jump, mostly from stock grants nearly doubling (from ~$93K/year to ~$161K/year). Every cycle you sit at E4 costs real money.

What Actually Gets You Promoted

Lead a project, not just contribute to one

The clearest E5 promotion cases at DoorDash 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 looks like strong E4 execution, not E5 readiness.

Mentor at least one junior engineer with visible results

E5 candidates need to show they grow the people around them. The best evidence is a concrete story: you mentored an E3 engineer, they shipped their first independent feature, and your manager or their manager noticed. This doesn't need to be a formal program. Pairing on a hard problem, 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.

Write design docs that shape decisions

At E4, you implement designs. At E5, you author them. Your promotion packet 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 E4 for a year and haven't authored a design doc, start now. Talk to your manager about which upcoming problems would benefit from a written proposal.

Build cross-team relationships before you need them

E5 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.

When you lead a project that requires their team's cooperation, you'll already have trust in place.

Make your contributions visible

DoorDash uses stack ranking. Your manager is comparing you to every other E4 in the org. If your work is invisible outside your immediate team, your manager has a harder time arguing for your promotion during calibration.

This isn't about self-promotion for its own sake. Share project updates in engineering channels. Present technical decisions in broader forums. Make your design docs discoverable. When peer feedback rolls around, people outside your team should have enough context to write something specific about what you did.

Mistakes That Keep Engineers at E4

Treating more code as the path forward. The most common E4 trap is thinking that shipping more features faster earns a promotion. E5 is about leverage, not velocity. An engineer who ships 50 PRs but never leads a project or mentors anyone looks like a productive E4, not a future E5.

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

Ignoring the stack ranking reality. It's not enough to meet E5 criteria in the abstract. Your contributions need to stand out relative to other E4 engineers in calibration. If you're doing solid work but three other E4s on your team are also doing solid work, differentiation matters. This is where leadership, mentorship, and cross-team impact create separation.

Not having the promotion conversation. Many engineers assume their manager is tracking their progress toward E5. Ask directly: "What does E5 readiness look like for me? What evidence would make my case clear in calibration?" This conversation surfaces gaps you didn't know about and tells your manager you're serious.

Getting downleveled and giving up. DoorDash is known for downleveling during hiring. If you were hired at E4 when you expected E5, the recruiter may have suggested 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 you'd need anyway: lead a project, mentor someone, write a design doc. The promotion case doesn't care about your hiring story.

Frequently Asked Questions

How long does it take to get promoted from E4 to E5 at DoorDash?

Most engineers spend 2 to 3 years at E4 before reaching E5. Strong performers with good project fit and clear leadership evidence can do it in about 2 years. E4 is a terminal level with no forced timeline, but compensation growth stalls without advancement.

Is E4 a terminal level at DoorDash?

Yes. There's no up-or-out policy at E4. You can stay indefinitely without being pushed out. But median total comp at E4 ($273K) is $113K lower than E5 ($386K), and the stock component of compensation barely grows without a level change.

What's the compensation difference between E4 and E5?

Based on Levels.fyi, median total comp jumps from roughly $273K at E4 to approximately $386K at E5. Stock grants nearly double (from ~$93K/year to ~$161K/year), which drives most of the increase. Base salary rises from ~$178K to ~$226K.

Does DoorDash use stack ranking for promotions?

Yes. DoorDash evaluates engineers relative to peers at the same level during biannual review cycles. Roughly 15% of engineers land in the bottom rating tier each cycle. Promotions are decided during calibration, where your manager argues your case against competing claims from other managers.

I was downleveled to E4 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 can feel demoralizing, and recruiter promises of "fast-track to E5" don't translate to guaranteed timelines. Focus on building evidence: lead a project, mentor someone, write design docs. Calibration evaluates your work at DoorDash, not your expectations at hire.

---

CareerClimb tracks your wins as they happen, maps them to what DoorDash evaluates in calibration, and shows you exactly 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