How to Get Promoted from E5 to E6 at DoorDash

You've been a senior engineer for two years. You lead projects, mentor junior engineers, and your team trusts your technical judgment. But when you watch the staff engineers operate, the difference is obvious. They don't wait for someone to hand them a problem. They decide which problems the org should care about, get leadership aligned, and make the technical direction stick across multiple teams.

That gap is the E5-to-E6 jump at DoorDash. The promotion requires shifting from team-level ownership to org-level influence, then proving you can sustain it for close to a year before anyone considers promoting you.

What changes from E5 to E6

E5 at DoorDash is Senior Software Engineer. E6 is Staff. The title changes, and so does the surface area of what you own.

Dimension	E5 (Senior SWE)	E6 (Staff SWE)
Scope	Leads projects within your team	Drives technical direction across multiple teams
Strategy	Executes on team-level technical decisions	Defines org-level technical strategy and long-term architecture
Influence	Influences your team and adjacent teams	Works directly with directors and VPs on engineering priorities
People	Mentors E3/E4 engineers	Mentors E5 engineers; grows the senior talent pipeline
Problem selection	Solves important problems assigned by leadership	Identifies which problems matter most and convinces leadership to invest
Communication	Writes design docs, presents to your team	Communicates trade-offs to executives, shapes roadmap decisions

The core shift: at E5, you own the "how" for your team. You figure out the best approach, build it, and deliver. At E6, you own the "what" and "why" for a larger part of the org. You decide which technical investments will pay off, convince the right people, and coordinate the work across teams you don't directly control.

How DoorDash promotions work

DoorDash runs biannual performance reviews with stack ranking. This is the same mechanism described in the E4-to-E5 guide, but the dynamics shift at E6.

The cycle:

1. You write your self-review documenting contributions and impact from the past half
2. Peer feedback is collected from engineers and cross-functional partners 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

At the E5-to-E6 boundary, calibration gets harder. There are fewer E6 slots than E5 slots. Your manager isn't just arguing you meet Staff criteria. They're competing against other managers who are also pushing their strongest E5 for the same limited promotions.

Two things matter more than they did at E5:

• Peer feedback from outside your team. If only your teammates vouch for you, calibration reviewers will question whether your influence is truly org-level.
• Evidence your manager can explain in two sentences. "She redesigned the payments architecture and reduced P99 latency by 40% across three services" is a case. "She does great technical work" is not.

How long E5 to E6 takes

Pace	Timeline	What's happening
Fast	~3 years at E5	Strong project fit, org-level impact from early on, clear staff-scope evidence across review cycles
Standard	4-5 years at E5	Growing cross-team influence over multiple cycles, expanding from team lead to org-level contributor
Slow	5+ years at E5	Something structural: wrong team, limited scope, or gaps in leadership signal

E5 is a terminal level at DoorDash. There's no up-or-out clock. Many senior engineers stay at E5 for their entire tenure and have successful careers. But the compensation gap is large.

Based on Levels.fyi data, median total compensation at E5 is about $386K. At E6, it jumps to about $585K. Stock grants nearly double (from ~$161K/year to ~$302K/year), which accounts for most of that $199K increase. Base salary goes from ~$226K to ~$273K. Every year you sit at E5 while performing at E6 costs real money.

DoorDash also expects you to operate at E6 level for 9 to 12 months before promotion. The promotion lags behind the performance. You won't get promoted into staff-level work. You have to already be doing it.

What gets you promoted

Own a technical direction, not just a project

The clearest E6 promotion cases involve someone who defined a technical strategy that changed how multiple teams build or operate. You didn't just lead a project. You identified a systemic problem, proposed an architecture change, built consensus with engineers and leadership across teams, and drove the execution.

At DoorDash, this could mean transitioning a set of services from a monolith to microservices, redesigning a platform that other teams depend on, or defining standards that improve reliability across the org. The common thread: you shaped a direction that outlives any single quarter's roadmap.

If every project on your review is scoped to your team, your case reads as strong E5 execution. E6 requires cross-team technical ownership.

Build relationships with senior leadership

E5 engineers talk to their manager and their team. E6 engineers talk to directors and VPs. Staff engineers communicate trade-offs to the people who make resourcing and priority decisions. That requires trust, and trust takes time to build.

Start before you need it. Attend leadership reviews. Present your team's technical direction in broader forums. If a director asks a question about a system your team owns, be the person with the answer. Over time, leadership should know your name because of what you've delivered, not because your manager mentioned you.

A director who can say "I've seen her work firsthand, she operates at staff level" during calibration carries more weight than your manager making the same argument alone.

Mentor senior engineers, not just juniors

At E5, you mentor E3 and E4 engineers. At E6, you grow other senior engineers. This is a different skill. Junior engineers need help with execution: how to debug, how to write a design doc, how to scope a project. Senior engineers need help with judgment: when to push back on a requirement, how to navigate a political situation, when to invest in long-term quality versus shipping fast.

The evidence: an E5 engineer you mentored took on larger scope, led a cross-team initiative, or made a technical decision that they wouldn't have made without your guidance. If you can point to two or three people whose trajectory shifted because of your involvement, that's strong staff-level signal.

Drive decisions through written proposals

E6 engineers shape how DoorDash builds software. The way that influence spreads is through written proposals: architecture decision records, technical strategy docs, and RFCs that other teams adopt.

Your promotion packet should include at least two documents where you identified a problem, proposed an approach, gathered feedback from engineers across multiple teams, navigated disagreements, and drove a decision that stuck. The quality bar is higher than E5. These documents should address org-level concerns (reliability, scalability, developer productivity) rather than team-level feature work.

If you've been at E5 for two years and haven't written a proposal that changed how a team outside yours operates, that's a gap you need to close.

Mistakes that keep engineers at E5

Doing E5 work faster instead of E6 work. The most common trap. You lead bigger projects, ship more features, and handle more complexity within your team. All of that is excellent E5 performance. E6 requires a different kind of work: defining strategy, building cross-team alignment, and influencing technical direction beyond your team's boundaries. Volume of E5 work does not convert into an E6 case.

Waiting for org-level scope to appear. Staff-level opportunities don't show up in sprint planning. You have to find them. Look at the problems that sit between teams, the systems nobody owns, the architectural debt that slows down multiple groups. Propose a solution, get buy-in, and lead the work. If you wait for your manager to assign you staff-level scope, you'll be waiting a long time.

Having influence but no documentation. You might be the person everyone comes to for technical advice. People Slack you with architecture questions. You unblock teams without anyone asking. But if none of that shows up in your self-review, peer feedback, or design docs, it doesn't exist during calibration. Your manager can't argue for your promotion based on work they can't point to.

Staying invisible to leadership. If the directors and VPs in your org don't know what you've delivered, your manager fights alone during calibration. Present in broader forums. Write technical updates that reach beyond your team. If leadership is discussing a system you shaped, be part of that conversation.

Mentoring only downward. Growing E3 and E4 engineers is E5 work. At E6, you also grow senior engineers and help them take on larger scope. If your mentorship stops at junior engineers, the promotion committee sees a strong senior, not a staff engineer.

Frequently asked questions

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

Most engineers spend 4 to 5 years at E5 before reaching E6. Strong performers with clear org-level impact and good project fit can do it in about 3 years. DoorDash expects you to perform at E6 level for 9 to 12 months before the promotion happens, so the actual timeline includes a sustained period of staff-level work before the title change.

Is E5 a terminal level at DoorDash?

Yes. There's no up-or-out policy at E5. You can stay at Senior indefinitely. Many engineers build long careers at E5 without advancing further. But median total comp at E5 ($386K) is $199K less than E6 ($585K), and the stock component barely grows without a level change.

What's the compensation difference between E5 and E6?

Based on Levels.fyi, median total comp jumps from roughly $386K at E5 to approximately $585K at E6. Stock grants nearly double (from ~$161K/year to ~$302K/year), driving most of the increase. Base salary rises from ~$226K to ~$273K. High-end E6 packages reach $700K or more.

What's the biggest difference between E5 and E6 at DoorDash?

Scope of ownership. E5 owns technical execution for their team. E6 owns technical direction for a part of the org. The shift is from "I built this" to "I decided we should build this, got the org aligned, and made sure it shipped across three teams." E6 also involves working directly with directors and VPs, which most E5 engineers rarely do.

Does DoorDash stack rank E5 engineers against each other for E6 promotions?

Yes. DoorDash evaluates engineers relative to peers at the same level during biannual reviews. For E5-to-E6 promotions, your contributions are compared against other E5 engineers across the org. There are fewer E6 slots than E5 slots, which makes the calibration more competitive than the E4-to-E5 boundary.

---

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