How to Get Promoted from IC3 to IC4 Software Engineer at Stripe

You have been at Stripe L3 for two years. Your code reviews are thorough, you have authored solid design docs, your team depends on you. And your manager keeps saying encouraging things like "you're doing great" without connecting that to a promotion timeline.

That is the L3 trap. L3 is the first terminal level at Stripe. No clock forces anyone to move you forward. No natural pressure pushes your manager to build the case. You can stay here indefinitely, doing excellent work, and nothing will change unless you change it.

The L3 to L4 transition is the jump from strong individual contributor to Staff Engineer. L4 is the first level that carries the "Staff Software Engineer" title, and it requires a fundamentally different kind of work. You are not just executing well anymore. You are setting direction, running projects that span multiple teams, and influencing how your part of Stripe's engineering organization operates.

Based on Levels.fyi, median total comp moves from roughly $400K at L3 to $576K at L4. The bar is genuinely high, and most L3 engineers do not make this transition.

What changes from L3 to L4

Dimension	L3 (Senior equivalent)	L4 (Staff)
Scope	Team-level projects, medium complexity	Division-level projects spanning multiple teams
Design ownership	Authors designs for team-scoped systems	Drives architectural decisions affecting multiple teams
Problem finding	Solves assigned or self-identified team problems	Identifies problems nobody has named yet and creates scope
Influence	Respected within immediate team	Shapes technical direction across the organization
People	Mentors L1/L2 engineers	Develops L3 engineers, influences hiring and team health
Communication	Raises risks proactively and drives discussions	Aligns stakeholders across teams, gets buy-in from leadership

At L3, you are the best player on your team. At L4, you are the person other teams come to when they need technical direction. You stop being measured by what you build and start being measured by the outcomes you create through others.

Stripe recognizes two types of Staff engineers: those whose scope is deep and those whose scope is broad. Broad-scoped Staff engineers create impact by working on cross-organizational problems and tend to be most common on product engineering teams. Deep-scoped Staff engineers are subject-matter experts in specific domains and lead ambitious multi-year projects, typically found on infrastructure and systems teams. Knowing which path fits you helps focus your L4 case.

How Stripe promotions work at L3-L4

The process is the same annual cycle (plus abbreviated mid-year window), but scrutiny increases at the L4 level.

Demonstrating L4 before getting the title. Stripe uses lagging promotions. You need to demonstrate L4-level work for roughly six months before your promotion is considered. That means running a cross-team project with genuine impact, not just talking about wanting more scope.

A big project is table stakes. On Team Blind, Stripe engineers consistently describe the primary differentiator as "having a big scope project under your belt." You have to prove you can execute a substantial project spanning 6 to 12+ months. Without that, the conversation does not start.

Cross-team peer feedback matters more. At L2 to L3, feedback from your immediate team is usually sufficient. At L3 to L4, calibration expects evidence from engineers and managers on other teams. If your work has not touched anyone outside your team, your case is incomplete.

Limited slots, higher bar. The promotion budget for Staff-level roles is tighter than for L3. There are fewer slots per org per cycle. Your manager is not just presenting your case. They are competing for a limited resource against other managers pushing their own candidates.

Writing is a superpower. Clear, concise documents that make life easier are valued at the Staff level. Design docs, post-mortems, and technical proposals all feed into how calibration perceives your influence. If your written communication is weak, it limits how far your ideas travel.

How long L3 to L4 should take

Pace	Timeline	What is happening
Fast	About 2 years	Right project, clear cross-team impact, strong manager sponsorship
Typical	3-4 years	Building credibility across the org, multiple strong projects
Slow	5+ years	Common at terminal levels. Nothing wrong if intentional

There is no hard cap at L3, so the timeline is entirely about opportunity, ambition, and project fit. Some excellent L3 engineers stay at L3 by choice and build fulfilling careers. The question is whether you are staying because you want to or because you do not know what L4 requires.

What actually gets you promoted

Run a project that crosses team boundaries

This is the single most important thing. Stripe engineers describe L4 as "being able to run projects with large impact or lots of cross-team coordination". Your project needs to involve at least one team beyond your own in a meaningful way. Not a quick API handoff, but sustained collaboration over months.

Look for problems that sit in the gaps between teams. Migration projects, infrastructure improvements that affect multiple services, developer experience work that touches the whole org. These are the problems nobody owns because they span boundaries. Talk to your manager about finding this kind of work. If your current team does not have cross-team projects, you may need to create the opportunity or consider an internal move.

Create scope instead of executing it

At L3, you receive problems and solve them well. At L4, you identify problems nobody has articulated yet. Look at your division's technical landscape and ask: what is broken that everyone has accepted? What is going to break in six months if nobody addresses it? What process or system is creating friction across teams?

Write up the problem and the proposed solution before anyone asks. Bring it to your manager and your skip-level with a plan. This is how you demonstrate L4 thinking before you have the title.

Build influence without authority

L4 engineers lead through influence, not through org chart position. You get engineers on other teams to adopt your approach not because you are their manager, but because your technical judgment has earned trust.

In practice: review code on adjacent teams. Participate in cross-team design reviews. When someone proposes an approach that will create problems downstream, speak up with a better alternative. Over time, people start pulling you into discussions because your input makes projects better.

Develop other engineers

L4 is the first level where growing others is an explicit expectation. This goes beyond code review. Mentor an L2 or L3 engineer through a challenging project. Help someone who is struggling find their footing. Be the person who makes the team stronger, not just the person who ships the most.

Document this in your impact doc. "Mentored [engineer] through their first end-to-end project, which shipped [result]" is calibration evidence.

Keep your impact doc sharp

Update it weekly. For each contribution, capture: what you did, what impact it had (with numbers when possible), who was involved across teams, and why it went beyond L3-level work. Your manager uses this document to build your calibration pitch. If the doc is comprehensive, the pitch writes itself. If it is sparse, your manager is guessing.

Mistakes that keep engineers at L3

Doing more L3 work faster. The most common mistake. You are shipping at an impressive pace, owning complex features, writing great code. But it is all team-scoped. No amount of excellent L3 output adds up to L4. The committee evaluates scope, not volume.

Waiting for the opportunity to come to you. L4-scope projects rarely land in your lap. You typically have to identify the problem, propose the solution, and get buy-in. If you are waiting for your manager to hand you a Staff-level project, you might wait indefinitely.

Working alone on everything. L3 rewards strong individual execution. L4 rewards outcomes achieved through others. If you are doing all the work yourself because it is faster than coordinating, you are optimizing for the wrong metric.

Having no cross-team peer feedback. If calibration only hears from people on your immediate team, the response is predictable: "This person is a strong L3." You need voices from other teams who can speak to your impact on their work.

Not having the promotion conversation. L3 is terminal, so your manager may assume you are content. If you want L4, say so directly. Ask what gaps exist in your case and what evidence the calibration group would need to see. Waiting for your manager to start this conversation can mean waiting years.

Frequently asked questions

How long does it take to get promoted from L3 to L4 at Stripe?

Typical timeline is 3 to 4 years, though strong performers with the right project fit can do it in about 2 years. L3 is a terminal level, so there is no hard cap or time pressure. The pace depends on finding cross-team scope, documenting impact consistently, and having strong manager sponsorship.

What is the pay difference between L3 and L4 at Stripe?

Based on Levels.fyi, median total compensation jumps from roughly $400K at L3 to $576K at L4. The increase is driven primarily by larger RSU grants. Stripe RSUs vest on a single-year schedule, so the equity bump takes effect quickly. The performance bonus target also increases from 15% to 20%.

Is L4 the same as "Staff Engineer" at Stripe?

Yes. L4 is the first level that carries the "Staff Software Engineer" title externally. Internally, L4 has sub-bands (L4a and L4b) that affect compensation but not the title. L4 maps roughly to Google L6 or Meta E6.

Can I switch from IC to EM at L3?

Yes. Stripe operates a dual career track, and L3 is the earliest level where lateral transfers between IC and EM paths are common. You maintain your level when switching. Many of Stripe's senior engineering leaders have moved between IC and management roles throughout their careers.

---

CareerClimb tracks your wins, maps them to what Stripe's calibration evaluates, and tells you exactly what evidence you are missing. When the next promotion cycle opens, your case is already built. Download CareerClimb