How to Get Promoted from SE to Senior SE at LinkedIn
Building your promotion case?
Get AI coaching on what to document and how to present it.
You've been an IC2 Software Engineer at LinkedIn for a couple of years. Your code ships, your PRs get approved, and you haven't broken anything in production. But nobody has told you whether you're actually tracking toward Senior or whether you're going to spend another two years doing the same work at the same level while your equity vest runs out.
The IC2 to IC3 promotion at LinkedIn is the jump from "reliable contributor" to "technical leader on the team." It's the first promotion where the expectations shift meaningfully. You're no longer being evaluated on whether you can do the work. You're being evaluated on whether you can own the work, including the parts nobody assigned to you.
What Changes from IC2 to IC3
| Dimension | IC2 (Software Engineer) | IC3 (Senior Software Engineer) |
|---|---|---|
| Independence | Works on features within defined scope | Owns medium-to-large projects from design through delivery |
| Design | Implements designs from senior engineers | Authors design docs, drives architectural decisions for your area |
| Problem solving | Solves assigned problems well | Identifies problems worth solving without being told |
| Mentorship | Collaborates with teammates | Actively mentors IC2 engineers, helps with code reviews and onboarding |
| Codebase knowledge | Knows your team's code | Understands cross-team dependencies and how your systems interact with adjacent services |
| Communication | Reports status when asked | Proactively surfaces trade-offs, risks, and architectural concerns |
The core shift: at IC2, someone scopes the work for you and you execute. At IC3, you get a problem and you figure out the scope, the approach, the edge cases, and the trade-offs. Then you execute and ship it.
How LinkedIn Promotions Work
LinkedIn runs a manager-driven promotion process. Your manager builds your case based on demonstrated impact, scope growth, and peer feedback, then submits it for leadership review. The minimum eligibility is 1 year at your current level.
There's an important compensation dynamic at LinkedIn that makes this promotion feel urgent: stock refreshers are notably limited. Even strong performance ratings don't guarantee refreshers. After your initial 4-year RSU vest runs out, your compensation can drop significantly unless you've been promoted or received a rare refresher grant. Promotion is the most reliable path to maintaining and growing your equity.
How Long IC2 to IC3 Should Take
| Pace | Timeline | What's happening |
|---|---|---|
| Fast | 2-2.5 years | Strong project ownership, design doc authorship, visible mentorship |
| Standard | 2.5-4 years | Steady scope growth over multiple review cycles |
| Slow (flag) | 4+ years | Something structural is off: project fit, manager engagement, or skill gaps |
Based on Levels.fyi, median total comp jumps from roughly $248K at IC2 to $315K at IC3. The increase comes primarily from larger RSU grants and a higher base salary. Given LinkedIn's limited refresher policy, this promotion is the clearest way to reset your equity trajectory.
What Actually Gets You Promoted
Own a project end-to-end
The single strongest signal. At IC3, LinkedIn expects you to have driven at least one meaningful project from problem identification through launch. Not a ticket someone scoped for you. A feature, system improvement, or infrastructure change where you understood the problem, proposed the approach, built it, shipped it, and measured the results.
If your current work is entirely pre-scoped tasks, talk to your manager about taking on a project where you own the full lifecycle.
Author a design doc
At IC2, you contribute to design discussions. At IC3, you're expected to have authored at least one design doc that the team executed on. The doc doesn't need to describe a massive system. It could be a well-reasoned proposal for refactoring a service, redesigning a data model, or solving a performance bottleneck. What matters is that you evaluated trade-offs, got buy-in from stakeholders, and the team built your design.
Build cross-team awareness
LinkedIn's systems are interconnected. At IC3, you're expected to understand how your team's services interact with adjacent teams. When a bug crosses service boundaries, you trace it instead of filing a ticket. When another team's design review affects your area, you attend and offer input.
Start reading code and documentation outside your immediate area. Attend architecture discussions for adjacent services. This builds the cross-team perspective that separates IC3 engineers from strong IC2s.
Mentor deliberately
Not just answering questions when someone asks. IC3 engineers actively help IC2 teammates grow. Take on an onboarding buddy role. Review PRs with the goal of teaching, not just approving. Help a junior engineer work through a technical decision instead of just giving them the answer.
Your manager should be able to name a specific IC2 engineer who grew because of your mentorship.
Mistakes That Keep Engineers at IC2
Executing perfectly at IC2 scope. Being fast and reliable at pre-scoped work isn't an IC3 case. The promotion evaluates scope growth, not speed at your current level. If your work looks the same as it did a year ago, just faster, your manager doesn't have a story to tell.
No design doc with your name on it. After 2+ years at IC2, the absence of a design doc becomes a visible gap. It's the most tangible artifact of IC3 readiness, and without it your manager has to rely on softer evidence that's harder to justify in a promotion review.
Not surfacing your work. LinkedIn's promotion process is manager-driven. If your manager doesn't know about your best contributions, they can't build your case. Send weekly updates in your 1:1 doc. When you finish something significant, make sure it's visible.
Treating problems as someone else's responsibility. IC2 engineers fix what's in front of them. IC3 engineers look at the system and ask "why does this keep happening?" and then propose a fix. If you notice a pattern of incidents and stay quiet, you're operating at IC2. If you write up the pattern, propose a prevention strategy, and drive the fix, that's IC3.
Ignoring the equity cliff. LinkedIn's limited refresher policy means your total comp can drop meaningfully after your initial RSU vest. Engineers who don't realize this until year 3 or 4 suddenly feel the urgency too late. Understanding this timeline early gives you motivation to build your IC3 case deliberately rather than hoping it happens naturally.
Frequently Asked Questions
How long does it take to get promoted from IC2 to IC3 at LinkedIn?
Most engineers who get promoted spend 2.5-4 years at IC2. The minimum eligibility is 1 year at level. Getting stuck beyond 4 years is unusual and worth a direct conversation with your manager about what's missing.
Is IC3 the terminal level at LinkedIn?
Yes. IC3 (Senior Software Engineer) is the most common terminal level. There's no organizational pressure to advance beyond it. Many engineers spend their entire career at IC3. Advancing to IC4 (Staff) requires a fundamentally different kind of impact: cross-team influence rather than team-level excellence.
What's the pay difference between IC2 and IC3 at LinkedIn?
Based on Levels.fyi, median total comp moves from roughly $248K at IC2 to $315K at IC3. The increase is driven primarily by larger equity grants. Given LinkedIn's limited stock refresher policy, this promotion is especially important for long-term compensation.
Do stock refreshers change at IC3?
Not dramatically. LinkedIn's refresher policy is limited across most IC levels. Even with strong performance ratings, refreshers aren't guaranteed. Promotion remains the most reliable path to equity growth at LinkedIn.
CareerClimb tracks your wins, maps them to what LinkedIn evaluates at each level, and tells you exactly what evidence you're missing. When the next promotion window opens, your case is already built. Download CareerClimb