How to Get Promoted from L3 to L4 at Google
Building your promotion case?
Get AI coaching on what to document and how to present it.
You've been at Google for about a year. You shipped your first feature, got through the ramp-up period, and your manager says your work is solid. But you have no idea if you're actually on track for L4 or if you're going to be one of those people who stays at L3 for three years wondering what went wrong.
The L3 to L4 promotion at Google is the first real level transition for new-grad engineers. It's the jump from "still learning" to "independently productive." Google expects most competent L3 engineers to make this transition within two years. The compensation bump is substantial, roughly $100K in total comp, which makes it one of the highest-percentage increases on the entire Google engineering ladder. But it still requires a promotion packet, a committee review, and a manager who actually builds the case. Here's how all of that works.
What Changes from L3 to L4
L3 is Google's entry-level engineering role, Software Engineer II. L4, Software Engineer III, is where Google considers you a fully independent contributor. The expectations shift in specific ways.
| Dimension | L3 (SWE II) | L4 (SWE III) |
|---|---|---|
| Independence | Needs guidance on task breakdown and approach | Works independently on assigned features with minimal direction |
| Scope | Individual tasks within a larger feature | Owns features and small projects from design through launch |
| Design work | Implements designs created by senior engineers | Contributes to design docs, may author designs for smaller features |
| Debugging | Solves bugs with help from the team | Debugs complex issues independently, including in unfamiliar code |
| Code quality | Writes correct code, learning team patterns | Writes robust, well-tested code that earns trust in review |
| Communication | Asks good questions, absorbs feedback | Communicates status proactively, raises risks, gives useful code reviews |
The shift comes down to one thing: your manager gives you a problem, not a task list. You figure out the approach, break it down, execute, and ship it. At L3, someone else does that scoping for you. At L4, that's your job.
How Google Promotions Work at L3-L4
Google's promotion process is committee-based but manager-driven. Under the GRAD system (Googler Reviews and Development), the process works like this:
- Your manager nominates you by writing a "next-level assessment"
- You write your self-review covering your contributions
- Peer reviews are collected from people you and your manager select
- Your manager writes their assessment and summarizes the peer feedback
- A calibration committee of your manager plus 2-3 peer managers reviews everything and decides
Two promotion windows open each year: March (primary, after the GRAD review cycle) and September (smaller off-cycle). The minimum eligibility is 6 months at your current level.
One thing that confuses L3 engineers: performance ratings and promotions are separate at Google. Your GRAD rating measures how you're performing at L3. Promotion evaluates whether you've been consistently doing L4-level work. You can hold a standard Significant Impact rating and still get promoted, because the committee is asking a different question.
The manager's role matters more than most new engineers realize. Under GRAD, your manager both nominates you and writes the narrative the committee reads. If your manager doesn't know what you've accomplished, or doesn't think you're ready, the process doesn't start.
How Long L3 to L4 Should Take
| Pace | Timeline | What's happening |
|---|---|---|
| Fast | 12-18 months | Strong ramp, good project fit, clear L4-scope work early |
| Standard | 18-24 months | Solid contributor, steady growth across two review cycles |
| Slow (flag) | 2.5-3+ years | Something structural is off: wrong project, disengaged manager, or skill gaps |
L3 to L4 is the promotion Google expects you to make. Unlike L4, which is a terminal level where you can stay indefinitely without pressure, L3 carries an informal expectation that you'll advance. Getting stuck at L3 beyond three years starts raising questions about your trajectory, both from your manager and from the system.
The compensation jump reinforces why this matters. Based on Levels.fyi data, median total comp moves from roughly $191K at L3 to $296K at L4. That's over a $100K increase. Every cycle you wait is real money.
What Actually Gets You Promoted
Own a feature end-to-end
The clearest signal of L4 readiness is completing a feature from problem identification through launch without someone else breaking down every step. This doesn't need to be a massive system. It could be a well-scoped improvement to an internal tool, a new API endpoint, or a user-facing feature your team needs. What matters is that you drove it: you understood the problem, proposed the approach, built it, got it reviewed, shipped it, and confirmed it worked.
If your current workload is entirely tasks that someone else scoped and handed to you, talk to your manager about getting work where you own the full cycle.
Get comfortable with ambiguity
L3 engineers receive well-defined tasks. L4 engineers receive problems. The transition means getting comfortable with figuring things out. When your manager says "this system is slow and users are complaining," the L4 response is to investigate, identify the bottleneck, propose a fix, and execute. The L3 response is to wait for someone to tell you which file to look at.
Practice this before it shows up in your review: when you hit a problem, try to figure it out for 30-60 minutes before asking someone. When you do ask, come with what you've tried and a hypothesis, not just "I'm stuck."
Write strong self-reviews
Your self-review is one of the primary documents the promotion committee reads. Treat it like a promotion case, not a task log. For each contribution, cover what you did, what impact it had, and how it went beyond L3 expectations.
"I got promoted after 18 months. Had one solid project where I owned the whole thing from design to launch. My self-review was the difference because I wrote it like I was making the case, not filling out a form."
Choose your peer reviewers carefully
You get to suggest who provides peer feedback. Pick people who observed your strongest L4-scope work: the engineer whose code you unblocked, the PM whose feature you shipped, the senior engineer who reviewed your design. Avoid people who will write generic praise. The committee discounts vague feedback like "great teammate" but weighs specific evidence like "independently drove the migration of our payment service, coordinating across three teams."
Talk to your manager about promotion directly
Don't wait for them to bring it up. After your first full review cycle, ask: "What does L4 readiness look like for me? What would make my case clear to the committee?" This conversation gives you a target and signals to your manager that you're thinking about growth.
On Team Blind, Google engineers consistently describe manager support as the single biggest factor in promotion outcomes. Your manager writes the packet the committee reads. They need specific wins to build that case.
Mistakes That Keep Engineers at L3
Staying in the comfort zone. You've gotten fast at the kind of tasks you were assigned during ramp-up. But doing more of the same work at the same scope doesn't build an L4 case. The committee evaluates scope growth, not speed at L3 tasks.
Treating every problem as a question. L3 engineers are expected to ask questions. But if you're still asking for help on things you could reason through after 18 months, your manager notices. The shift from "asks good questions" to "proposes solutions" is what separates L3 from L4.
Not tracking your work. When the self-review window opens, you have a week or two to recall 6 months of contributions. Engineers who track wins as they happen write stronger self-reviews. Engineers who scramble to remember produce vague summaries the committee can't evaluate.
Assuming your manager is tracking everything. Managers at Google can have 8-12 reports. They're not remembering every PR you merged or every bug you fixed. If you're not surfacing your contributions in 1:1s and status updates, your manager's packet will reflect what they remember, not what you actually did.
Avoiding design work. Some L3 engineers are happy implementing designs from senior engineers forever. But the committee expects to see growth toward design ownership. Contributing to a design doc, even as a co-author, signals you're moving in the right direction.
Frequently Asked Questions
How long does it take to get promoted from L3 to L4 at Google?
Most engineers who get promoted spend 18-24 months at L3. Strong performers with the right project fit can do it in 12-18 months. The minimum eligibility is 6 months at level. Unlike L4, which is a terminal level, L3 carries an informal expectation that you'll advance. Getting stuck beyond 3 years is unusual and worth a direct conversation with your manager.
Is L3 to L4 considered easy at Google?
Relative to later promotions, yes. The bar for L3 to L4 is lower than L4 to L5, and the expectations are more straightforward: ship features independently, debug without hand-holding, communicate clearly. The same applies for data scientists making the L3-to-L4 jump, though the evidence looks different. But it's still a committee decision that requires your manager to write a convincing packet. "Easy" doesn't mean automatic.
What's the pay difference between L3 and L4 at Google?
Based on Levels.fyi, median total compensation jumps from roughly $191K at L3 to $296K at L4. That's over a $100K increase, driven by base salary increases and significantly larger stock grants. This is one of the largest percentage jumps on Google's engineering ladder.
Should I switch teams if I'm stuck at L3?
Only if the problem is your team, not your skills. If your team doesn't have L4-scope work (rare at Google, but possible on small maintenance teams), switching can help. But a team change resets your context. Your new manager won't know your work, and you'll spend months ramping up again. If your manager is the issue (disengaged, not building your case), try having the direct conversation first. If that doesn't change anything over a full review cycle, then consider moving.
CareerClimb tracks your wins, maps them to what Google's promotion committee evaluates, and tells you exactly what evidence you're missing. When the next promotion window opens, your case is already built. Download CareerClimb