How to Get Promoted from SDE1 to SDE2 at Amazon
Building your promotion case?
Get AI coaching on what to document and how to present it.
You shipped your first feature. You're handling on-call without panicking. Your Forte reviews say you're doing well. But you just watched someone who started six months after you get promoted to SDE2, and nobody told you why.
The SDE1 to SDE2 promotion at Amazon is the transition the company expects you to make. SDE1 is not a terminal level. Amazon assumes competent engineers will grow into SDE2 within roughly two years. The total comp jump is massive: median SDE1 pay is around $170K versus roughly $267K at SDE2. That's nearly $100K in annual compensation sitting on the other side of a promotion your manager decides when to initiate. Here's how that decision gets made and what you can do to influence it.
What Changes from SDE1 to SDE2
SDE1 is Amazon's L4, the entry-level engineering role. SDE2 is L5, the mid-level position where the largest chunk of Amazon's engineering population sits. The title change is straightforward: Software Development Engineer I to Software Development Engineer II. The expectations behind it are not.
| Dimension | SDE1 (L4) | SDE2 (L5) |
|---|---|---|
| Independence | Works with guidance; tasks scoped by others | Owns features independently with minimal direction |
| Scope | Individual tasks within a larger project | Full features and small projects end-to-end |
| Design | Implements designs from senior engineers | Authors design docs for features and service changes |
| Debugging | Debugs issues with help from the team | Debugs complex production issues independently |
| On-call | Shadows or handles straightforward pages | Fully owns on-call rotation, drives incident response |
| Communication | Status updates, asks good questions | Proactively raises risks, drives alignment across stakeholders |
| Leadership Principles | Demonstrates LPs in daily execution | Shows strong LP stories across multiple principles |
The shift boils down to one question: can your manager hand you a problem and trust you to deliver the solution without breaking it down into subtasks for you? At SDE1, someone else does that scoping. At SDE2, that's your job.
How the SDE1 to SDE2 Promotion Works
Amazon's promotion process is manager-driven. Your manager identifies when you're ready, nominates you, and builds the case. You don't self-nominate.
Here's the sequence:
- Forte reviews feed the process. Twice a year (Q1 and Q3), you submit 3-5 accomplishments through the Forte system, each showing concrete impact tied to Amazon's Leadership Principles (LPs)
- Your manager calibrates your performance against L5 expectations during the Organization and Leadership Review (OLR), where managers present cases and committee members compare engineers across teams
- Your manager nominates you if they believe you're operating at L5 level, writing a promo doc that summarizes your evidence
- OLR calibration finalizes the decision. Senior leaders stack rank engineers across the org using a forced distribution
The promo doc for SDE1 to SDE2 is shorter than the 15-page document required for SDE2 to SDE3. But it still needs specific evidence: features you owned, problems you solved, Leadership Principle alignment, and impact metrics. Your manager writes this document. The quality of what you feed them determines the quality of what ends up in that room.
Your OLR rating matters. Amazon's stack ranking uses fixed distribution targets: roughly 20% Top Tier (TT), 15% Highly Valued 3 (HV3), 25% Highly Valued 2 (HV2), 35% Highly Valued 1 (HV1), and 5% Least Effective (LE). For SDE1 to SDE2, you generally need HV2 or above. TT or HV3 is the clearest signal that you're promotion-ready.
What Actually Gets You Promoted
Own a feature from problem to production
The single clearest signal of SDE2 readiness is taking a feature from problem identification through launch without someone else defining every step. This doesn't need to be a massive system redesign. A well-scoped service improvement, a new internal tool, or a customer-facing feature all count. What matters is that you drove it: you understood the problem, wrote or contributed to the design doc, implemented the solution, got it reviewed, shipped it, and monitored it in production.
If your current work is entirely subtasks that someone else scoped and assigned, talk to your manager about getting a project where you own the full lifecycle.
Get serious about on-call
SDE2s fully own their on-call rotation. They don't just respond to pages. They drive incident response, write postmortems, and identify operational improvements that prevent future incidents. If you're still shadowing or avoiding on-call, your manager notices.
The engineers who get promoted fastest treat on-call as an opportunity to demonstrate Ownership and Dive Deep. Handle an incident without escalating when you could have figured it out yourself. Write a postmortem that identifies the root cause, not just the symptoms. Propose and implement the fix.
Write Forte entries like promotion evidence
Your Forte submission is what your manager cites in OLR calibration. Vague accomplishments give them nothing to work with. Specific entries with numbers, scope, and clear Leadership Principle connections give them the material to build your case.
For each accomplishment, cover:
- What you did (the specific action, not a team summary)
- What impact it had (latency reduced by X%, incidents dropped by Y, feature adopted by Z customers)
- Which Leadership Principles it demonstrates (Ownership, Deliver Results, Dive Deep)
"I rewrote my Forte entries from 'helped with the migration project' to 'owned the data migration for the payments service, reducing query latency by 40% and eliminating 3 weekly on-call pages.' My manager told me that version was what she used in calibration word-for-word."
Build LP stories across multiple principles
At SDE1, demonstrating Leadership Principles in daily work is enough. At SDE2, the bar rises. Your manager needs LP-aligned stories that hold up in a calibration room.
The four principles that matter most at this transition:
- Deliver Results means you ship features reliably and meet commitments
- Ownership means you take end-to-end responsibility, including for things outside your assigned scope
- Dive Deep means you debug thoroughly, understand systems beyond the surface level, and don't accept the first explanation
- Bias for Action means you don't wait to be told what to work on next
You don't need to be exceptional across all 16 Leadership Principles. You need documented evidence across the ones that define the SDE1-to-SDE2 bar.
Have the promotion conversation with your manager
Don't wait for review season. After your first full Forte cycle, ask your manager directly: "What does SDE2 readiness look like for me specifically? What gaps do you see between where I am now and a strong promotion case?"
This conversation does two things. It gives you a concrete target instead of guessing. And it tells your manager you're thinking about growth, which shapes how they allocate work and advocate for you during calibration.
If your manager gives a vague answer, push for specifics. Ask what a recent SDE1-to-SDE2 promotion on your team looked like. Ask what evidence the OLR committee found most convincing.
Mistakes That Keep Engineers at SDE1
Taking subtasks instead of owning features. Three cycles of executing assigned subtasks well doesn't build an SDE2 case. The OLR committee evaluates scope, not volume. If every piece of work you've delivered was defined and broken down by someone else, the committee won't see L5 evidence.
Writing vague Forte entries. "Contributed to the redesign of the notification service" tells your manager nothing they can use in calibration. "Owned the notification batching redesign, reducing API calls by 60% and cutting notification delivery latency from 800ms to 200ms" gives them a sentence they can read verbatim to the committee.
Avoiding operational ownership. SDE2s own production. Engineers who avoid on-call, skip writing postmortems, or always escalate instead of investigating signal that they're not ready for L5 responsibility. Operational maturity is one of the things managers weigh most heavily.
Assuming the promotion will happen automatically. SDE1 isn't terminal, but "not terminal" doesn't mean "automatic." Your manager still has to nominate you, write the case, and defend it in OLR. If you're not feeding them evidence and having explicit promotion conversations, the nomination might not happen when you expect it to.
Staying on a team without SDE2-scope work. Some teams keep SDE1s in narrow support roles with no path to feature ownership. If you've been on your team for over a year and haven't had a chance to own something end-to-end, have an honest conversation with your manager. If the work doesn't exist, an internal transfer may be the right move.
Timeline and Realistic Expectations
| Pace | Timeline | What this looks like |
|---|---|---|
| Fast | 12-18 months | Strong ramp, immediate feature ownership, supportive manager, TT or HV3 rating |
| Standard | 18-24 months | Solid contributor, steady growth across two Forte cycles, clear L5-level evidence |
| Slow (flag) | 2.5-3+ years | Something structural is off: narrow scope, disengaged manager, or skill gaps not being addressed |
You'll need to show consistent L5-level work for at least one to two Forte cycles before your manager puts you forward. Amazon's "prove it first" bar means you're already doing the job before you get the title.
Compensation makes every extra cycle expensive. Amazon's RSU vesting schedule is back-loaded (5%, 15%, 40%, 40% over four years), which means your Year 1 and Year 2 cash compensation is heavily supplemented by signing bonuses that eventually run out. Getting to SDE2 before your signing bonus cliff hits is financially significant. The SDE2 refresher grants and higher base help close that gap.
If you've been at SDE1 for two years with decent Forte feedback but no promotion conversation, treat it as a signal. Either the team doesn't have L5-scope work, your manager doesn't think you're there yet and hasn't told you, or something in calibration is working against you. All three are worth a direct conversation.
Frequently Asked Questions
How long does it take to get promoted from SDE1 to SDE2 at Amazon?
Most engineers who make SDE2 spend 18-24 months at SDE1. Strong performers with the right project fit and a supportive manager can do it in 12-18 months. SDE1 is not a terminal level, and Amazon expects competent engineers to advance. Getting stuck beyond 2.5 years is unusual and worth investigating directly with your manager.
What OLR rating do I need to get promoted from SDE1 to SDE2?
You generally need HV2 or above in the OLR forced distribution. TT or HV3 are the clearest promotion signals. Back-to-back HV1 ratings will stall any promotion case regardless of tenure. The Amazon performance review process covers how OLR ratings and forced distribution work in detail.
Is SDE1 a terminal level at Amazon?
No. SDE1 (L4) is not terminal. Amazon expects engineers to grow into SDE2 (L5). SDE2 is the terminal level where engineers can stay indefinitely without being managed out. The fact that SDE1 isn't terminal means there's informal organizational pressure to advance, but it doesn't mean the promotion is automatic. You still need your manager to build and defend the case.
What's the pay difference between SDE1 and SDE2 at Amazon?
Based on Levels.fyi, median total compensation jumps from roughly $170K at SDE1 to $267K at SDE2. That's nearly a $100K increase. The jump comes from higher base salary, larger RSU grants, and the transition off of signing-bonus-dependent compensation onto refresher equity that vests more evenly.
Should I switch teams if I'm stuck at SDE1?
Only if the problem is the team, not your skills. If your team keeps SDE1s in narrow support roles with no feature ownership, a transfer can unlock the right scope. But team changes reset your context: your new manager won't know your work, and you'll spend months ramping up again. Have the direct conversation with your current manager first. If L5-scope work doesn't exist and can't be created, then moving makes sense.
CareerClimb tracks your wins and maps them to Amazon's Leadership Principles and promotion criteria week by week, so when your manager builds that promo doc, they're working from documented evidence instead of memory. Download CareerClimb