How to Get Promoted from L5 to L6 Software Engineer at Airbnb

You've been at Airbnb G9 (Senior Software Engineer) for three years. Your performance ratings are consistently strong, your team relies on your judgment for the hardest technical decisions, and you've mentored several junior engineers. But every time Staff (G10) comes up, your manager talks about "org-level impact" and "cross-team influence" without giving you a clear picture of what that actually means at Airbnb. Meanwhile, you've heard on Team Blind that G9 to G10 is "several orders of magnitude harder" than G8 to G9. That checks out.

The G9 to G10 transition at Airbnb is genuinely the hardest common promotion on the engineering ladder. G10 carries the "Staff Software Engineer" title and requires sustained organization-level impact, not just strong individual execution. Based on Levels.fyi, median total comp moves from roughly $427K at G9 to $550K at G10. The refresher grant target jumps from ~$180K to ~$300K per year. But the compensation isn't the hard part. The bar is.

What Changes from G9 to G10

Dimension	G9 (Senior)	G10 (Staff)
Scope	Team-level projects, medium-to-large complexity	Org-level projects spanning multiple teams
Design ownership	Designs for your team	Drives architectural decisions affecting multiple teams
Problem finding	Solves known problems and identifies team-level gaps	Identifies problems nobody has named yet — creates scope at the org level
Influence	Strong within your team	Shapes technical direction across the organization
People	Mentors junior engineers	Develops G9 engineers, influences hiring and team health
Visibility	Known within your team	Known across the org, trusted by engineering leadership

The shift: at G9, you make your team stronger. At G10, you make the engineering organization stronger. Your impact extends beyond any single team.

How This Promotion Works

Structural factors matter as much as performance. G9 to G10 isn't just about meeting a performance bar. It requires organizational need for someone at G10 scope, headcount to support the level, and visibility with engineering directors. You can be doing G10-level work and still not get promoted if the structural factors don't align.

The evidence bar is much higher. At G9, two cycles of Exceeds gets you promoted. At G10, calibration expects sustained org-level impact demonstrated over multiple review cycles. One strong project isn't enough.

Executive visibility is required. Your manager and their manager both need to advocate for the case. If engineering directors don't know your work, the promotion doesn't happen at this level.

What Actually Gets You Promoted

Run projects that cross team boundaries

The defining G10 signal is sustained cross-team impact. Look for problems that sit between teams — migrations, infrastructure improvements, platform work that affects multiple services. These are the projects nobody owns because they span boundaries.

Create scope at the organization level

At G9, you solve problems that are already known. At G10, you identify problems nobody has named yet. Study the technical landscape across your org. What's slowing everyone down? What technical debt is accumulating that will hurt in a year? Write up the problem and propose the solution before anyone asks.

Build influence across teams

G10 engineers are known beyond their immediate team. Review code for adjacent teams. Participate in cross-team design reviews. When someone proposes an approach with downstream risks, speak up with a better alternative. Over time, engineers outside your team start seeking your input.

Develop senior engineers

G10 is where developing G9 engineers becomes an explicit expectation. Help senior engineers grow into technical leaders. The calibration question: does this person make the senior engineering population stronger?

Mistakes That Stall G9 Engineers

Expecting performance alone to get you there. This is the biggest misconception. Excellent G9 performance, even with Greatly Exceeds ratings, doesn't automatically lead to G10. You need the org need and headcount, not just the skill.

Operating at team scope no matter how complex the work. A very hard project that lives entirely within your team is still G9-scope work. G10 is about breadth of organizational influence.

Not building executive relationships. G10 promotions require director-level buy-in. If your skip-level doesn't know your work firsthand, your manager has to proxy it during calibration.

Waiting for the opportunity. G10-scope projects rarely land in your lap. You typically have to identify the problem, propose the solution, and create the project yourself.

Frequently Asked Questions

How long does it take to get promoted from G9 to G10 at Airbnb?

Typical timeline is 3 to 5 years. Some engineers do it in 2 to 2.5 years with exceptional impact and the right structural factors. G9 is a terminal level, so many excellent senior engineers stay here by choice.

Why is the G9 to G10 promotion so hard?

Because it requires more than strong performance. You need organizational need for G10-scope work, headcount to support the level, cross-team impact sustained over multiple cycles, and visibility with engineering leadership. These structural factors are outside your control, which is why the timeline varies so much.

What's the pay difference between G9 and G10 at Airbnb?

Based on Levels.fyi, median total comp moves from roughly $427K at G9 to $550K at G10. The annual refresher grant target increases from ~$180K to ~$300K, and the performance bonus target goes from 20% to 25% of base.

---

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