What Is L5 at Google? The Senior Software Engineer Level Explained

L5 at Google is the Senior Software Engineer level. It is the level most Google engineers hold for the longest time, and it is the level the company treats as the standard for an experienced engineer. Most external hires at L5 have about five to nine years of experience, although the interview result decides the level, not the resume. An L5 engineer owns a project from design to launch, works without day-to-day direction, and guides the L3 and L4 engineers around them.

The Google ladder is numbered, and each number has a fixed title. The table places L5 among its neighbors.

The Google Engineering Ladder Around L5

The experience column describes a pattern, not a rule. Google decides the level from interview performance and from the scope of past work. An engineer with four years of experience who has already led a service can be offered L5. An engineer with ten years of experience who has only worked on assigned tasks is often offered L4.

What an L5 Engineer Is Expected to Do

Own a problem, not a task. The difference between L4 and L5 is who decides what to build. An L4 engineer receives a well defined feature and delivers it. An L5 engineer receives a goal, such as "halve the p99 latency of this service", writes the design document, splits the work, and delivers the result. The p99 latency is the response time that 99 percent of requests beat.

Design systems that other people will maintain. L5 engineers write and review design documents. They are expected to choose between a queue and a direct call, or between one database and two, and to state the trade-off in writing before the code exists.

Improve the engineers around them. An L5 engineer reviews code from L3 and L4 engineers, mentors at least one of them, and is often the technical lead of a group of two to five people. They do not manage anyone. People management at Google is a separate ladder with the same level numbers.

Work without supervision. The internal phrase is that an L5 engineer "operates independently". A manager checks the outcome of a quarter, not the progress of a week.

Google L5 Years of Experience

Google does not publish a years-of-experience requirement for L5. Postings for Senior Software Engineer usually ask for five years or more, and most people who receive an external L5 offer have between five and nine years. Internal promotion from L4 to L5 typically takes two to four years at L4.

Two things move the number. Scope moves it down, because leading a service that other teams depend on counts for more than time served. A narrow career moves it up, because many years of maintenance on one codebase, with no design work, usually results in an L4 offer.

How the L5 Interview Differs From L4

The shape of the loop is the same at L4 and L5: a phone screen, then four or five onsite rounds, then a hiring committee that reads the written feedback and decides. Two rounds change at L5.

A system design round is added. L3 and L4 candidates rarely see one. L5 candidates get one system design round of about 45 minutes, and a low score in it is the most common reason an L5 candidate is offered L4 instead. The scope of that round is described in what a Google L5 system design interview covers.

The behavioral round asks for leadership. Google calls this round Googleyness and Leadership. At L4 the questions are about teamwork. At L5 the interviewer wants a story in which you set the direction for others, resolved a disagreement between engineers, or made a decision with incomplete information.

The coding rounds stay. An L5 candidate still writes code in three or four rounds, and the standard for correctness and clean code does not drop. The typical questions are listed in the top coding interview questions for Google.

Down-Leveling and the Hiring Committee

Google fixes the level after the interviews, not before. The hiring committee reads every interviewer's written feedback and can offer a level below the one you applied for. This is called down-leveling, and it is common for L5 candidates whose coding rounds were strong and whose design round was weak.

You can decline a down-leveled offer, or accept it and pursue promotion inside. Promotion from L4 to L5 is also decided by a committee, which reads a packet of your design documents and launches.

Compensation Structure

Google pays L5 engineers a base salary, an annual bonus, and stock grants that vest over four years. The amounts change with location, with negotiation, and with the share price, so this page does not quote figures. Compare against published offers on a salary aggregator before you negotiate.

How to Prepare

• Treat the system design round as the deciding round. Practice complete designs with capacity estimates and a written trade-off for every choice. Grokking the System Design Interview covers the designs that appear in Google L5 loops.
• Keep the coding rounds strong. Three or four coding rounds remain at L5, so practice by pattern rather than by problem. Grokking the Coding Interview teaches the patterns.
• Prepare six leadership stories. Each story should show you setting direction, not only contributing. Grokking the Behavioral Interview shows how to structure them.
• Know the full loop before it starts. Read what the five rounds of the Google interview are so nothing in the schedule surprises you.