An SDE 1 delivers well-defined tasks with guidance; an SDE 2 owns features end to end, handles ambiguity, reviews others' work and needs little supervision. The exact bar differs by company, so read your company's career ladder and collect evidence of independent ownership.
What people tell me
I am an SDE 1 and I keep hearing people talk about getting to SDE 2, but nobody at work has explained what actually changes. Some colleagues were promoted after two years, some after four. I also see companies advertising SDE 2 roles with very different experience requirements. I want to understand what the difference really is so I can work toward it on purpose.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- The difference is scope and independence, not years or the number of tickets closed.
- SDE 1: well-defined tasks, guidance expected. SDE 2: whole features, ambiguity handled, little supervision.
- Levels are company-specific; an SDE 2 at one company can equal a senior title elsewhere.
- Read your company's ladder and collect written evidence against each expectation.
- Start doing SDE 2 work before the title, and tell your manager that is what you are doing.
The short version
SDE 1 and SDE 2 are titles used by many large tech companies for the first two levels of software engineer. The difference is not years of experience or how much code you write. It is scope and independence.
- An SDE 1 takes well-defined tasks and delivers them with guidance. People expect to review their work closely and help them when they get stuck.
- An SDE 2 takes a loosely defined problem, turns it into a plan, delivers a whole feature and needs little supervision. Others start relying on them for reviews and help.
Side by side
| Area | SDE 1 | SDE 2 |
|---|---|---|
| Scope | Tasks and small features | Whole features or a component |
| Ambiguity | Needs clear requirements | Clarifies requirements themselves |
| Design | Follows an existing design | Writes small designs and defends trade-offs |
| Code review | Receives most feedback | Gives meaningful reviews to others |
| Operations | Fixes bugs when assigned | Handles on-call, investigates incidents, prevents repeats |
| Mentoring | Learns from others | Helps interns and new SDE 1s |
| Communication | Updates their lead | Updates stakeholders, flags risks early |
Levels are not the same everywhere
This confuses people when they compare offers. Titles are company-specific. An SDE 2 at one company might match a mid-level engineer at another and a senior engineer at a smaller startup. Some companies use numbers (L3, L4), some use words (junior, mid, senior), some use both.
Two useful resources:
- levels.fyi maps levels across companies and shows compensation reported by engineers.
- Engineering Ladders is a free framework that describes what each level is expected to do across technology, systems, people and process.
When you apply externally, ask the recruiter which level the role is and what the expectations are, rather than trusting the title.
What usually decides the promotion
In most companies, promotion from SDE 1 to SDE 2 needs evidence of three things:
- Ownership of something meaningful. A feature you took from a vague request to production, including the parts that were not coding: clarifying requirements, handling edge cases, monitoring after launch.
- Sound technical judgement. You made design decisions that held up, and you can explain the trade-offs.
- Reliability without supervision. Your manager stopped checking in on your work daily because they did not need to.
Notice what is not on the list: the number of tickets closed. Volume without ownership often keeps people at SDE 1 longer.
How to work toward it on purpose
- Read your company's ladder. If there is none written down, ask your manager what SDE 2 means in your team.
- Ask for a feature, not tasks. Tell your manager you want to own the next feature end to end.
- Write a short design note before you build anything larger than a few days of work. Share it for review.
- Review others' code seriously. Useful review comments are one of the clearest signals of growth.
- Keep a brag document. Record what you did, the impact, and who saw it. Julia Evans' guide to brag documents explains how.
- Talk about it early. Say in your one-to-ones: "I am working toward SDE 2. What gaps do you see?" Ask again every quarter.
The career growth roadmap and its cheat sheet go deeper on growing scope and visibility.
How long does it take?
It varies widely. Some engineers move in under two years, others take longer, and the difference is usually scope and evidence rather than talent. If you have been at SDE 1 for a long time, ask your manager directly what is missing and whether the team has the kind of work you need.
If you are still stuck
Read How do I get promoted from junior to mid-level developer? for a step-by-step plan. If you want help mapping your work against your company's ladder, join Sefism and, as a member, book a 1:1 session.
Was this answer helpful?
Read next
- What Actually Changes in Your First Two Years as an EngineerJunior software engineer tips for the part interviews never test: reading unfamiliar code, asking questions that cost nothing, shipping small, using code review, using AI without stalling your learning, and what really gets you promoted.
- Twelve Moves That Take You From Mid Level to SeniorGoing from mid level to senior software engineer is about scope, not years. Twelve moves that actually get you there: leverage over volume, a written promotion bar, design docs, multiplying through others and choosing a direction.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.