The path to SDE3 and beyond

SDE3 (senior) is the level where "strong individual contributor who ships features" stops being enough. The job shifts toward owning ambiguous problems, setting technical direction in a local sphere, raising the quality bar, and multiplying other engineers. Staff and principal continue that arc across a wider surface area. Titles vary; the behavioral change does not.

If you are a solid SDE2 wondering what "more senior" means — not just harder interviews — start here, then read the pages in order.

Concepts in this section

Step	Concept	What it answers
1	Owning ambiguity	What does a senior-shaped problem look like?
2	Technical leadership without management	How do you lead with designs, standards, and reviews?
3	Navigating organizations	How do you get alignment without authority?
4	Staff archetypes	Which staff shape, and IC vs manager?
5	A plan from SDE2 to SDE3	What does the next 12–24 months look like?

Seniors still write code. They stop being the only way code gets written in their area. A useful early-senior split is often about 40–60% deep coding or design, with the rest in review, writing, and mentoring. Track a month and adjust before habits calcify. If coding is 95%, you are still in strong-SDE2 habits. If coding is 5% and the calendar is meetings, reclaim maker time or you will lose the taste that makes leadership trustworthy.

Mentorship at this level is structured growth for someone else: pairing on design, reviews that teach, safe first-on-call, and their name on the launch note when they did the work. Track first ship, first design doc, first incident command. If the team is tiny, mentor sideways — a peer team ramping on your system, or a guide that scales past one person. See mentorship.

Being indispensable is not the same as being senior. If your vacation breaks the team, you have concentrated risk. Seniors make themselves replaceable on yesterday's work so they can take tomorrow's ambiguity. Management is a lateral craft switch, not a promotion above senior IC. Do not take a manager seat only because the IC path is blocked.

Common mistakes

Snacking on many small wins with no senior-shaped narrative.
Ghost chasing the perfect staff project while peers ship.
Local-maximum hero who cannot go on vacation.
Architecture astronaut whose designs have no adoption.
Meeting senior invited everywhere, leaving no artifacts.
Accidental manager because the IC path was blocked.

Key takeaways

SDE3 is owning ambiguity, direction, bar-raising, and multiplication.
Technical leadership does not require reports.
Organizational alignment is part of the craft.
Keep coding enough for credibility; spend real time on leverage.
Staff archetypes and the manager fork are choices. A 12–24 month plan with artifacts beats vague "be more senior."