How to Get Promoted from SDE2 to SDE3 at Amazon
Building your promotion case?
Get AI coaching on what to document and how to present it.
You've been SDE2 for three years. Your Forte reviews are solid. Your manager says you're doing well. Then you hear that someone who joined a year after you just made SDE3.
The SDE2-to-SDE3 jump at Amazon trips up more engineers than almost any other transition in big tech. SDE3s make up roughly 10% of Amazon's engineering population, compared to about 40% at SDE2. The gap isn't about writing better code. It's about scope, influence, and a 15-page document you probably haven't thought about yet.
How Amazon's SDE3 promotion actually works
Amazon's promotion process is manager-driven. Your manager identifies L6-scope projects, writes a promotion document, gathers stakeholder feedback, and advocates for you before a promotion panel. You don't self-nominate.
The promo doc for SDE2 to SDE3 is at least 15 pages and takes roughly 40 hours to write well. It covers five core dimensions:
- Scope and influence (breadth of impact across teams)
- Ambiguity (operating in ill-defined problem spaces)
- Technical complexity (depth of engineering challenges)
- Execution (quality of delivery and operational excellence)
- Impact (measurable business and technical outcomes)
Beyond the document, your manager needs endorsements from at least 6 L6-level people: other SDE3s, SDMs, PMs, and TPMs who can vouch that you operate at L6 level. You can't solicit these endorsements yourself. Your manager handles it through proper channels.
The promotion panel is adversarial by design. Panelists actively look for reasons to deny the promotion, not approve it. If the promo doc has gaps or your manager can't defend the case under pressure, the promotion dies in that room.
Promotions for SDE2 and SDE3 are reviewed quarterly. But the real gatekeeping happens during the Organization and Leadership Review (OLR), where senior leaders calibrate performance ratings across teams using a forced distribution. You need a Top Tier (TT) or High Value 3 (HV3) rating to be promotion-eligible, which represents roughly the top 15-20% of engineers.
What SDE3 actually looks like at Amazon
The core shift from SDE2 to SDE3 isn't more code or harder bugs. It's moving from individual execution to multiplying the team's output.
| Dimension | SDE2 (L5) | SDE3 (L6) |
|---|---|---|
| Scope | Features and components within a single service | Systems spanning multiple teams and services |
| Autonomy | Works independently on well-defined problems | Drives ambiguous, ill-defined problem spaces |
| Design | Contributes to design docs | Authors and owns design docs for cross-team systems |
| Mentorship | Active in code reviews | Coaches engineers and shapes team development practices |
| Impact | Individual delivery within team boundary | Team-level and cross-team outcomes |
| Decisions | Technical choices within assigned scope | Architectural decisions with significant business impact |
| Delivery | Ships own work reliably | Delivers through others |
An SDE2 designs a scalable solution for their service. An SDE3 designs for scale beyond a single team's domain, thinking about long-term system evolution rather than next quarter's deliverables.
A useful benchmark from Amazon's internal guidelines: candidates should demonstrate competency at roughly 80% of L6 expectations before building a promotion case.
The promotion criteria that actually matter at Amazon
The promo doc evaluates five dimensions, but two separate the candidates who get through from those who don't.
Scope and influence is where most SDE2s fall short. Your work needs to show impact across teams, not just within your own service boundary. The panel wants evidence that other teams changed their approach because of your work.
"SDE 2 to SDE 3 promotions are generally held back because of lack of scope, influence, and impact."
Ambiguity is the second filter. SDE2s solve assigned problems. SDE3 candidates identify the problems worth solving, define the solution space, and drive alignment before writing any code. If every project you've worked on came fully scoped by someone else, the panel will notice.
Technical complexity matters, but it's table stakes at this level. The panel expects you to handle hard problems. What they're testing is whether you tackled complexity that required cross-team coordination or long-term architectural thinking.
Leadership Principle alignment runs through the entire document. At L6, the Leadership Principles most commonly cited in strong promotion cases are Ownership (taking responsibility beyond your assigned scope), Think Big (proposing solutions with org-wide impact), and Hire and Develop the Best (actively mentoring and raising the team's bar).
"You need other SDE3s to validate the complexity of your projects but you also need other key L6+ stakeholders to provide feedback that you're operating at the L6 level."
Building your SDE3 promotion case at Amazon
Step 1: Have the explicit promotion conversation
Don't wait until review season. Ask your manager: "What does L6-level scope look like on our team? What specific gaps do you see between where I am and an SDE3 case?" Get this in writing if possible.
Step 2: Find or create L6-scope work
Look for projects with cross-team dependencies, architectural decisions, or ambiguous problem spaces. If your team's roadmap doesn't have them, propose one. Write the design doc. Frame it for multi-team or org-wide impact. If no L6-scope work exists on your team after sustained effort, a team transfer may be the right move.
Step 3: Build relationships with 6+ L6-level people
Your manager needs endorsements from at least 6 people at L6 or above. These can't be strangers who review your work cold. They need to be engineers, SDMs, PMs, and TPMs who have seen your L6-level contributions firsthand through cross-team projects, design reviews, or operational partnerships.
Step 4: Document your impact in real time
Don't reconstruct your wins at promo time. Keep a running log of design docs, launch posts, metric improvements, incident responses, and mentoring outcomes. The promo doc is 15+ pages. Your manager can't write it well from memory, and neither can you.
Step 5: Help your manager build the case
Your manager accounts for roughly 40% of your promotion success. Feed them concrete material: your impact metrics, your LP-aligned accomplishments, the names of stakeholders who've seen your L6 work. Make their 40-hour promo doc easier to write. If your manager can't or won't advocate for you after you've done this, that's a signal worth acting on.
Common mistakes that stall SDE2-to-SDE3 promotions at Amazon
Shipping at SDE2 scope and expecting it to add up. Three years of excellent SDE2 execution doesn't accumulate into an SDE3 case. The promo panel evaluates scope, not tenure. If every project you've touched stays within your team's boundary, the panel won't see L6 evidence no matter how many things you shipped.
Ignoring stakeholder relationships until promo time. You need 6 L6-level endorsements, and those relationships take months to build organically. Engineers who start networking only when they want a promotion end up with endorsements that feel thin. The panel notices.
Staying on a team without L6-level scope. Some teams don't have cross-team work on the roadmap, and no amount of individual excellence will produce an SDE3 case without it. On Team Blind, engineers consistently report that changing teams was the unlock.
Treating documentation as an afterthought. The promo doc isn't a summary you write after the work is done. It's a 15-page argument that needs specific artifacts: design docs, launch metrics, operational improvements, and before/after measurements. Engineers who don't document as they go produce weak promo docs.
Depending on a manager who can't advocate. A good manager lines up scope, gathers stakeholders, and writes a promo doc that survives an adversarial panel. A weak one struggles with all of those things. If your manager has never promoted someone to SDE3, pay attention to whether they know the process well enough to navigate it.
Timeline and realistic expectations for SDE2 to SDE3 at Amazon
| Timeline | What it looks like | How common |
|---|---|---|
| ~2 years | Exceptional scope from day one, TT rating, strong manager | Rare |
| 3-4 years | Standard successful path with multiple cycles of L6-scope evidence | Most common |
| 4-6 years | Includes a failed attempt, team change, or scope drought | Common |
| 6+ years or indefinitely | SDE2 is a terminal level; many engineers stay permanently | Not unusual |
You'll need to demonstrate consistent L6-level work for at least 6 months before your manager puts you up. Amazon's "prove it first" bar means you're already doing the job before you get the title. Beyond the promo doc criteria, the informal signals managers watch — trust, cross-team reputation, how you handle ambiguity — shape whether your manager feels confident enough to stake their credibility on your case.
SDE2 is terminal at Amazon. No organizational pressure pushes you toward SDE3, and engineers can stay at L5 for decades without being managed out. This also means the L5 pool is deep and competitive, making OLR stack ranking harder. The Amazon performance review process covers how OLR ratings and forced distribution work in detail.
Frequently asked questions
How long does it take to get promoted from SDE2 to SDE3 at Amazon?
Most engineers who make SDE3 spend 3-4 years at SDE2. The fastest path (about 2 years) usually requires strong manager support, a Top Tier OLR rating, and immediate access to L6-scope work. Some engineers stay at SDE2 for 6-10+ years or indefinitely. SDE2 is a terminal level at Amazon with no automatic promotion timeline, and the SDE3 population is roughly 10% of all engineers.
What OLR rating do I need to get promoted to SDE3 at Amazon?
You need a Top Tier (TT) or High Value 3 (HV3) rating, which represents the top 15-20% of engineers in the forced distribution. Back-to-back High Value 1 (HV1) cycles will stall any promotion case regardless of tenure. The OLR process evaluates performance and potential on separate dimensions, and both feed into the overall value score that determines your rating.
Should I change teams to get promoted to SDE3?
If your current team lacks L6-level scope (cross-team projects, ambiguous problem spaces, architectural decisions), a transfer may be necessary. But team changes reset your stakeholder relationships and force you to rebuild context. Have an honest conversation with your manager about whether L6-scope work exists or can be created before making that call. The general approach to building a promotion case still applies regardless of team.
Can I write my own promo doc at Amazon?
No. The manager writes the promo doc. But you should feed your manager the raw material: tracked wins, impact metrics, LP-aligned accomplishments, names of stakeholders, design docs, and launch posts. The doc is 15+ pages and takes about 40 hours. The better your documentation, the stronger the case your manager can build.
CareerClimb helps you track your wins and map them to Amazon's Leadership Principles and promotion criteria week by week, so when your manager writes that 15-page promo doc, they're working from evidence instead of memory. Download CareerClimb