How to Get Promoted as a Software Engineer at Big Tech

Getting promoted as a software engineer at a big tech company isn't just about writing good code. It requires understanding how the system works, tracking your impact, and building a compelling case for why you're ready for the next level.

Here's what you need to know.

Understanding the Leveling System

Each big tech company has its own leveling structure, but they follow similar patterns:

Google uses L3-L10 for individual contributors. New grads start at L3, mid-level is L4, Senior is L5, Staff is L6, and it continues up to L10 (Google Fellow). The terminal level—where promotion becomes optional—is L5.

Meta uses E3-E8 (also referred to as IC3-IC8). Senior is E5, Staff is E6. Like Google, E5 is the terminal level, and promotions beyond that become increasingly competitive.

Amazon uses L4-L8 for software engineers, with slightly different scope expectations at each level.

The key insight: promotions below the terminal level (L5 at Google, E5 at Meta) are relatively straightforward if you demonstrate competence. Above that, you're competing for limited slots and need to show organizational-level impact.

How Promotion Committees Actually Work

At companies like Google, promotions aren't decided by your manager alone. You go before a promotion committee—a group decision that evaluates your packet against the rubric for your target level.

Here's what most engineers don't realize:

Lagging promotions are the norm. Google and similar companies require you to demonstrate you can work at the next level for approximately six months before they'll promote you. You have to prove yourself capable before getting the title.

Committees are conservative. When in doubt, committees tend to wait rather than promote early. This means your evidence needs to be clear and compelling.

Your manager advocates, but doesn't decide. Even great managers need ammunition. If they can't articulate why you deserve the promotion with specific examples, the committee won't be convinced.

What Gets Evaluated

The specific rubric varies by company, but most evaluate similar dimensions:

For L3/L4 (Entry to Mid-level):

• Coding skills and algorithmic expertise
• Ability to deliver assigned work reliably
• Basic collaboration with the team

For L5 (Senior):

• Technical design capability
• System design knowledge
• Leading projects end-to-end
• Mentoring others
• Communication and influence

For L6+ (Staff and beyond):

• Organizational-level impact
• Driving technical strategy across teams
• Handling highly complex, ambiguous problems
• Setting architectural direction

The jump from L5 to L6 is where many engineers get stuck. It's no longer about being a great individual contributor—you need to show you can multiply the effectiveness of others.

The Brag Document Strategy

One of the most effective tools for promotion is maintaining what Julia Evans popularized as a "brag document"—a running record of your accomplishments. (We've created a free brag document template you can start using today.)

Here's why it works:

You will forget what you did. Performance review time often brings a demoralizing feeling of "wait, what did I actually do?" A brag document prevents this.

Your manager forgets too. No matter how great your manager is, they're managing multiple people. They need help remembering your impact when advocating for you.

It makes the case undeniable. It's hard to argue with a factual list of achieved goals, completed projects, and positive outcomes.

What to Record

Every week, document:

• Key code changes and their impact
• Code reviews you've done
• Design documents you've written
• Discussions and planning sessions you've led
• Times you've helped others
• Postmortems and learnings

For each entry, note what you did, why it was important, and the result. Add dates for context. Example: "Jan 2025—Optimized image loading on the homepage, cutting page load time by 30%, which improved conversion rates."

Converting to a Promotion Packet

Your brag document becomes the raw material for your promotion packet. When it's time:

1. Synthesize aggressively. Depth with supporting evidence beats breadth. Pick your strongest examples.
2. Map to the rubric. Find the expectations for your target level. Show how your work demonstrates each dimension.
3. Make it easy for your manager. Work with them in a 1:1 to translate your brag document into a 2-minute pitch. The less work they have to do, the better they can advocate.
4. Connect to org goals. Hunt down the OKRs for 1-2 levels above yours. Map your contributions to that baseline to show organizational relevance.

Common Mistakes to Avoid

Waiting until promo season. If you start documenting your work when reviews are coming up, you've already lost months of evidence. Start now.

Focusing on what you did, not the impact. "Refactored the authentication module" is weak. "Refactored the authentication module, reducing login errors by 40% and saving 10 engineering hours per week in debugging" tells a story.

Assuming your manager knows everything. They don't. Over-communicate your wins. Share your brag document with them regularly.

Not asking what "next level" looks like. Talk to your manager explicitly about what you need to demonstrate. Get concrete examples of what success looks like.

Trying to do it alone. Share your brag document with peer reviewers if your company does peer feedback. Get input from Staff+ engineers on what strong evidence looks like at your target level.

The Path Forward

Getting promoted at big tech requires intentionality. You need to:

1. Understand your company's specific leveling system and rubric
2. Track your work continuously, not just at review time
3. Map your accomplishments to the criteria that matter
4. Build a promotion packet that makes the committee's job easy
5. Partner with your manager to advocate effectively

The engineers who advance aren't necessarily the best coders—they're the ones who can articulate their impact clearly and consistently.

Related Guides

• Free Brag Document Template - Start tracking your wins today
• Google Promotion Guide - L3 to L6 at Google
• Meta Promotion Guide - E3 to E6 at Meta
• Amazon Promotion Guide - SDE levels at Amazon
• Apple Promotion Guide - ICT levels at Apple
• Snap Promotion Guide - L3 to L6 at Snap

Sources

This guide draws on publicly available information about big tech promotion processes:

• Julia Evans on Brag Documents
• Staff Eng Guide on Promotion Packets
• FAANG Levels Explained
• Google Engineering Levels
• The Pragmatic Engineer Work Log Template