TL;DR
I have watched a lot of engineers stall out somewhere between SDE1 and Senior, and it is almost never because they cannot code. It is because nobody explained how promotion actually works. The technical bar matters, but so does how you present your work, how you build relationships across teams, and how well you understand your company’s leveling rubric.
This guide breaks down what promotion committees are really scoring, how long the climb from SDE1 to Senior takes at different types of companies, what the pay jump looks like at each stage, and the specific moves that speed things up. I pulled the numbers from BLS OEWS data, Levels.fyi, and Glassdoor, so nothing here is guessed.
What SDE1 to Senior Actually Means
SDE1 is the entry point. You are writing code against well-scoped tickets, learning the codebase, and leaning on a mentor or tech lead for most decisions. Titles vary by company. Amazon calls it SDE1, Google calls it L3, Meta calls it E3, but the scope is the same across the industry.
If you want the full national picture on where these titles land on pay, this breakdown of software engineer salaries across the US is worth a look before you set expectations for your own offer or review.
Senior is where the job changes shape. You are not just writing good code anymore. You are expected to scope your own projects, make architectural calls without someone checking your work line by line, and help junior engineers grow.
Most companies treat Senior as a terminal level, meaning the bar to go further, to Staff or Principal, gets a lot steeper and a lot more political.
How Long the Climb Actually Takes
The honest answer is 4 to 7 years for most people, based on aggregated Stack Overflow and BLS survey data. But that number hides a lot of variation.
Startups and smaller companies with looser leveling can promote exceptional SDE1s in 12 to 18 months. FAANG and other large tech employers usually want 18 to 36 months and two consecutive strong performance review cycles before they will sign off on a jump from SDE1 to SDE2, and a similar runway again from SDE2 to Senior.
Traditional enterprises, banks, insurance companies, and government contractors tend to run slower, often 5 to 8 years to reach Senior, partly because promotion cycles are less structured and partly because return-to-office mandates at these employers have changed how visibility and face time factor into review conversations.
Salary by Level: SDE1 to Staff
Here is how base pay and total compensation actually move as you climb, based on 2026 data from BLS OEWS, Levels.fyi, and Glassdoor. Total comp includes RSUs, signing bonus, and annual bonus on top of base.
| Level | Experience | Base Salary (US) | Total Comp Range | Core Focus |
| SDE1 / Junior | 0 to 2 years | $75K to $95K | $85K to $150K | Learning fundamentals, shipping well-defined tasks under review |
| SDE2 / Mid-Level | 2 to 5 years | $100K to $140K | $150K to $280K | Owning features end to end, contributing to system design |
| Senior / SDE3 | 5 to 8 years | $140K to $185K | $230K to $390K | Technical leadership, cross-team impact, mentorship |
| Staff / Principal | 8+ years | $180K to $350K | $400K to $700K+ | Org-wide architecture, technical direction, glue work |
Figures reflect national averages across tech and non-tech employers. FAANG and frontier AI labs run well above these ranges once equity and refreshes are included.
Promotion Criteria Companies Actually Score You On
Every formal promotion process I have seen, whether at a startup or a company with a full leveling committee, comes down to four things.
Ownership
Can you take a vague problem and turn it into a shipped solution without someone else driving it for you? SDE1s execute tickets. SDE2s own features. Senior engineers own entire problem spaces and are trusted to decide what should get built in the first place.
Impact Metrics
Committees do not promote based on effort. They promote based on outcomes you can quantify. Did you cut latency by 40 percent? Reduce infrastructure cost by a specific dollar amount? Increase a conversion metric? Vague claims get skipped over in review. Numbers get remembered.
Technical Leadership
This is the clearest line between mid-level and Senior. It shows up as writing design docs other teams actually follow, making architectural calls that hold up under scrutiny, and being the person others pull into a discussion when a decision is hard.
Mentorship
Senior engineers are expected to make the people around them better, not just ship their own code faster. Pairing with junior engineers, running design reviews, and onboarding new hires all count, and committees specifically look for this because it is a signal you can operate at scope beyond your own tickets.
The Performance Review Cycle, Explained
Promotions are lagging by design. Most companies want to see you performing at the next level for six months to a year before they will actually promote you into it. That is why the promotion conversation usually starts during a performance review, not after one.
Pay transparency laws in states like Colorado, New York, and California have made this process a little less opaque, since companies now have to publish salary bands.
If you want to understand how those bands affect your negotiating position once you do get promoted, this guide to salary transparency in job postings walks through what the published range actually means and what it does not guarantee.
A good manager will build a promotion packet with you well before the review window opens. That packet maps your work against the ladder criteria for the next level, with specific examples and numbers attached. If your manager has never mentioned a promotion packet, ask about it directly. It is the single most useful document in this whole process.
Skill Growth: The Real Gap Between SDE1 and Senior
The technical skill gap is smaller than people think. A strong SDE1 and a Senior engineer often write comparable code. The real gap is in judgment. Seniors know which problems are worth solving well and which ones deserve a quick fix.
They understand tradeoffs between speed and correctness, and they can explain those tradeoffs to a non-technical stakeholder.
Specialization also starts mattering more around the mid-level to Senior transition. Some engineers move toward infrastructure and reliability work, and pay for that path can look different from a standard product engineering track.
If you are weighing that switch, this comparison of software engineer and DevOps pay is a useful reference before you commit to a specialization.
Building a Promotion Case That Actually Works
Keep a running document of your work, updated monthly, not scrambled together the week before review season. For every project, note the problem, what you did, and the measurable outcome. This is often called a brag document, and it exists because your manager genuinely will not remember everything you shipped six months ago.
When you write up your impact, always close the loop with what it demonstrates about the next level. Do not make the reviewer infer it. A line like this project shows the cross-team ownership expected at Senior is far stronger than just describing the project and hoping the connection is obvious.
Common Mistakes That Slow People Down
Staying at one company for years without pushing for a leveling conversation is the biggest one. Comfort is not the same as growth, and managers rarely nominate someone for promotion who has not asked.
Chasing only technical depth while ignoring visibility is another. Committees cannot promote work they do not know about. And undervaluing total compensation when you do get an offer or a promotion is a real cost. Base salary is only part of the picture once RSUs, bonuses, and benefits and perks like extra PTO or wellness stipends are factored into what the role is actually worth.
How Company Choice Changes Your Timeline
Not every employer promotes at the same pace, and this matters more than most engineers realize when they are choosing where to work. Some companies run tight, structured ladders with predictable cycles.
Others leave it almost entirely up to individual managers, which can work in your favor or against you depending on who you report to. This breakdown of the top software engineering companies is a good starting point if promotion velocity is a factor in where you want to work next.
Should You Consider a Different Path
Senior is not the only direction from SDE2. Some engineers move toward product management once they realize they enjoy the strategy side more than the implementation side. If that is on your radar, this comparison of software engineer and product manager roles lays out how the day-to-day and the pay actually differ.
Others leave the traditional ladder entirely and go independent. Freelance and contract work has grown fast in this market, and it comes with a different risk and reward structure than climbing an internal ladder. This look at freelance software engineer income is worth reading if you are weighing that option against staying on the promotion track.
And if you want a deeper, step-by-step walkthrough of the promotion process itself, this real software engineer promotion guide goes further into the mechanics of building a packet and presenting it to a committee.
For a broader look at what the software engineering career actually looks like day to day in the US, including hiring trends and role variety, this overview of being a software engineer in the US is a solid companion read to this guide.
Frequently Asked Questions
-
How long does it take to go from SDE1 to Senior?
Most engineers take 4 to 7 years. FAANG companies with strong, consistent performance reviews can compress that to 2 to 3 years. Traditional enterprises often take 5 to 8 years.
-
What is the salary difference between SDE1 and Senior?
SDE1 total compensation typically runs $85K to $150K. Senior total compensation typically runs $230K to $390K, based on 2026 Levels.fyi and Glassdoor data, with FAANG packages often landing at the higher end.
-
Can I skip levels on the way to Senior?
It happens, but it is rare and usually tied to exceptional, well-documented impact over a short window, or a lateral move to a company with a lower leveling bar for the same title.
-
Does switching companies help you get promoted faster?
Sometimes. A new employer evaluates you fresh, without the baggage of being seen at your old level. But you also start over on trust and context, which can offset the advantage if the new team does not ramp you quickly.
-
What matters most for a Senior promotion, technical skill or leadership?
Both, but leadership tends to be the deciding factor once technical competence is no longer in question. Committees assume you can code at Senior level. What they are actually evaluating is scope, ownership, and mentorship.
-
Do performance reviews directly control promotion timing?
Yes, at most structured companies. Promotions are lagging, meaning you typically need two consecutive strong review cycles at the next level’s scope before a promotion is approved.
-
Is a promotion packet actually necessary?
It is not always required on paper, but in practice it is the document that makes or breaks a promotion case in front of a committee. Engineers who keep one consistently tend to get promoted faster than those relying on their manager’s memory.
A Final Word
The jump from SDE1 to Senior is less about grinding longer hours and more about understanding what is actually being measured. Track your impact, ask for the leveling conversation before you think you are ready, and treat mentorship as part of the job, not a favor you do on the side. That combination moves people up faster than raw output ever does.
Shahzada Muhammad Ali Qureshi (Leeo)
I’m Shahzada — a software engineer by education and an SEO professional by trade. I built WhatIsTheSalary.com to go beyond just showing salary numbers — every page is manually researched across sources like BLS, Glassdoor, LinkedIn Salary, and PayScale to give you the full picture in one place. If you found what you were looking for here, that’s exactly the point.
