SWE Promotion Checklist

A promotion typically involves a change in scope and responsibility (e.g., L4 to L5), often accompanied by a salary increase. A raise may adjust your compensation without a level change, usually to align with market rates or reflect increased impact. Promotions require demonstrating readiness for the next level, while raises can be negotiated based on performance or market data.

For example, a senior engineer (L5) at Google might receive a raise to align with market benchmarks without changing levels, while a promotion to staff engineer (L6) would require showcasing leadership, mentorship, and architectural influence. Always clarify with your manager whether you’re targeting a raise alone or a promotion.

The timeline varies widely by company, level, and individual performance. Here’s a general ESTIMATE based on Levels.fyi and Glassdoor data:

• L3 to L4 (Mid-Level): 1.5–3 years (many engineers spend 2 years at L3).
• L4 to L5 (Senior): 2–4 years (often requires leading projects and mentoring).
• L5 to L6 (Staff): 3–5 years (requires technical leadership and cross-team impact).

Factors like company size, industry, and individual impact can accelerate or delay these timelines. For example, FAANG companies may have longer timelines due to higher competition, while startups might offer faster promotions for high performers.

Methodology note: These estimates are derived from Levels.fyi promotion timelines and Glassdoor employee reviews.

If your company lacks a formal career ladder, use this checklist as a framework to self-advocate. Start by documenting your contributions in each section (e.g., technical impact, leadership, mentorship), then schedule a conversation with your manager to discuss growth. Ask questions like:

• “What does ‘ready for the next level’ look like at this company?”
• “What gaps do you see in my current scope or impact?”
• “Are there upcoming projects where I can take on more ownership?”

Even informal expectations can be mapped to this checklist. For example, if your manager mentions leadership, focus on Section 2 (Leadership & Ownership). If they emphasize visibility, prioritize Section 3 (Visibility & Advocacy).

Documenting your contributions is critical for promotion discussions. Use this format to create a promotion narrative:

1. Impact: “I led X project, which improved Y metric (e.g., performance, cost, user experience) by Z%.”
2. Leadership: “I mentored X engineers, who successfully delivered Y outcomes.”
3. Visibility: “My work on X was recognized by Y stakeholders (e.g., manager, skip-level, cross-team partners).”

Here’s an example:

“I led the redesign of our checkout flow, reducing latency by 30% and improving conversion rates by 5%. This involved collaborating with the product team to prioritize features and mentoring two junior engineers through implementation. The project was highlighted in our company-wide demo, and my manager noted its impact on revenue growth.”

Share this narrative with your manager before promotion discussions to ensure alignment. Tools like Notion or Coda can help track contributions over time.

If your manager says you’re not ready, ask for specific feedback and a timeline. Use these questions to clarify expectations:

• “What skills or contributions am I missing to be ready?”
• “What timeline do you envision for my growth?”
• “Are there upcoming projects or roles where I can gain this experience?”

Then, map their feedback to this checklist. For example, if they mention “lack of leadership,” focus on Section 2 (e.g., leading sprints, driving cross-team initiatives). If they mention “visibility,” prioritize Section 3 (e.g., documenting impact, seeking feedback).

If the feedback feels unclear or unrealistic, consider seeking a skip-level meeting to get a broader perspective. Data from Levels.fyi suggests that engineers who actively seek feedback and align with business goals are 40% more likely to achieve promotions within 12 months.

Switching jobs can be a faster way to advance, especially if your current company has slow promotion cycles or unclear expectations. Here’s how to decide:

• Research market rates for your role/level using Levels.fyi or Glassdoor. If you’re underpaid, a job change might increase compensation.
• Compare your scope to similar roles. If you’re already doing the work of the next level but aren’t recognized, internal mobility or an external role might help.
• Talk to your manager about internal mobility (e.g., switching teams/projects). Sometimes a change in scope can accelerate growth.

Methodology note: LinkedIn’s 2023 Workplace Report found that employees who switched jobs saw a 15–20% salary increase on average, compared to 3–5% for internal promotions. However, external roles come with trade-offs (e.g., new team dynamics, ramp-up time).

If you stay, use this checklist to address gaps proactively. If you leave, use it to evaluate opportunities (e.g., “Will this role give me leadership/visibility opportunities?”).

Preparation is key. Follow these steps to make the conversation productive:

1. Schedule the meeting: Frame it as a career growth discussion, not just a promotion ask. Example: “I’d like to discuss my contributions, growth areas, and long-term goals at the company.”
2. Bring your narrative: Use the documentation format from FAQ #4 to highlight your impact, leadership, and visibility.
3. Align with business goals: Show how your contributions tie to company priorities (e.g., “My work on X supports our team’s goal of Y”).
4. Ask for feedback: “What would it take for me to be ready for the next level?”
5. Set next steps: Propose a timeline (e.g., “Can we check in on progress in 3 months?”).

Example script:

“Over the past year, I’ve led X projects, improving Y metric by Z%. I’ve also mentored A engineers and driven B cross-team initiatives. My goal is to grow into a staff engineer role, where I can take on more architectural and leadership responsibilities. Based on my contributions, do you think I’m on track for this? If not, what gaps should I address?”

Remote work can make promotions more challenging—not because remote employees perform worse, but because visibility and advocacy become harder. Here’s how to adapt:

• Proactively document impact: Remote employees need to be more intentional about tracking contributions (see FAQ #4).
• Build relationships asynchronously: Share updates in team channels, document decisions, and schedule 1:1s with managers/skip-levels.
• Seek feedback regularly: Ask for verbal/written feedback in meetings or async updates.
• Optimize for “high-visibility” projects: Volunteer for cross-team initiatives or projects highlighted in company-wide meetings.

Methodology note: Buffer’s 2023 State of Remote Work report found that remote employees are 20% more likely to feel “left out” of career growth opportunities. However, data from Levels.fyi shows that remote engineers at companies like GitLab and Zapier advance at similar rates to in-office peers when visibility is prioritized.