The L3/L4 Question: Where Do New Grads Get Leveled?

TL;DR

Most new grads at Google land at L3, Meta at E3, Amazon at SDE I. These are the standard entry levels.
A small number of candidates with strong internship records or exceptional interview performance land one level higher.
Leveling is determined by your interview performance, your internship history, and sometimes the specific team's needs.
You can sometimes negotiate level, but it requires strong justification and isn't common at the entry level.
Non-Big-Tech companies use different systems that don't map cleanly to numbered levels.

If you're interviewing at a large tech company that uses numbered levels, you've probably wondered: where will I actually land? And does it matter?

The answer to the second question is yes, significantly. Your starting level determines your pay band, your equity grant, your promotion timeline, and the expectations you'll be held to from day one. A one-level difference at entry can mean $30K or more in total annual compensation, plus meaningfully different equity refreshes.

The answer to the first question is more predictable than most candidates think.

The Standard Entry Levels

Each major tech company has a standard entry level for new grad software engineers. These are the levels that the majority of people joining straight from school (or shortly after) land at:

Google: L3. This is where almost every new grad engineer starts. L4 is considered mid-level and requires demonstrated experience beyond a standard new grad profile.

Meta: E3. Same dynamic. E4 is mid-level and usually requires meaningful prior industry experience, not just internships.

Amazon: SDE I. Amazon's system uses titles rather than pure numbers, but the structure is the same. SDE II is where engineers with more experience or strong track records land.

Microsoft: The level system starts around 59-60 for new grads. Level 62 or above is reserved for people coming in with more substantive experience.

Apple: ICT2 is the standard new grad entry level. ICT3 is the next step and typically requires prior experience.

LinkedIn: The equivalent of an L3/E3 for new grads, with a roughly similar structure.

The pattern is consistent. There is a standard entry level. Most people start there. The question is: what moves the needle in either direction?

What Affects Where You Land

Your starting level is set during the offer process and is based on a combination of factors the company evaluates together.

Interview performance. This is the biggest lever. Candidates who perform exceptionally across all interview dimensions, not just passing, but performing at the top of the range, get flagged for potential higher-level placement. If you sail through every technical question and your system design (if included) demonstrates strong intuition, the hiring committee may consider an L4 rather than L3.

Internship history. Multiple strong return-offer internships at well-regarded companies, especially at the same company, signal that you've already operated successfully at a professional level. This factors into leveling discussions. A candidate who did two FAANG internships and got return offers from both is a different profile from someone with no internship history.

Years since graduation. If you're three or four years out of school and have been working as an engineer at another company, you're not really a "new grad" anymore. Companies that level you will treat your prior experience as a factor. At that point you should be interviewing and negotiating at a higher starting level rather than accepting the default new grad placement.

The specific team or role. Sometimes a team with an urgent need for someone who can operate with more independence may advocate for a higher-level offer for a strong candidate. This is less systematic and more situational.

Understanding where you sit on the leveling spectrum is much easier when you understand how junior, mid, and senior levels actually differ in practice.

Can You Negotiate Your Level?

In short: sometimes, but it's uncommon at the new grad level and requires a specific justification.

Negotiating compensation within your level is standard and expected. Negotiating level itself is a different ask. It typically requires either a competing offer at a higher level from a comparable company, or a strong case based on prior experience that the standard entry level doesn't reflect your actual capabilities.

If you have a concrete data point, for example, a competing offer from another FAANG company at E4 rather than E3, that's a legitimate basis for a conversation. The company may not match the level, but they may offer more compensation within your current level as an alternative.

If you don't have a competing offer but think your profile warrants a higher level, you can raise it, but be prepared for pushback. Companies have leveling calibration processes for a reason, and most will hold to their initial assessment unless you give them a specific reason to reconsider.

The place to focus your negotiation energy as a new grad is usually compensation, not level. Negotiating your first engineering offer covers how to approach that conversation effectively.

How Leveling Actually Happens Inside the Company

The process is worth understanding, because it demystifies why you land where you do.

During and after your interviews, the interviewers submit feedback using the company's internal scale. At Google, that scale goes from "strong no hire" to "strong hire" with gradations in between. At Meta, it's similar. The feedback notes aren't just pass/fail. They include an assessment of what level the interviewer thinks you're operating at.

After the interviews, a hiring committee reviews the full feedback packet. If every interviewer says you're a clear L3 with room to grow, you're getting an L3 offer. If the feedback is mixed but generally positive, you're likely still getting L3 but the committee discussion was more involved. If multiple interviewers note that you performed above the expected range for a new grad, there may be a conversation about L4.

The hiring manager for the specific team also has input, particularly if they've been working to fill a role that requires more experience.

You typically won't know the details of this process. What you can control is your interview preparation.

The Level You Get Doesn't Define Your Ceiling

Starting at L3 rather than L4 at Google is not a permanent setback. It changes your starting compensation and your starting point on the promotion ladder, but L3 engineers who perform well get promoted to L4 within 12-24 months in many cases.

Conversely, starting at L4 when you're not actually operating at that level creates real pressure. You're expected to work with more autonomy, own more scope, and demonstrate mid-level behaviors from the start. If you've been leveled up based on a strong interview but haven't actually worked at that level before, you'll need to ramp quickly.

Most people are better off starting at the right level and moving up quickly than starting at a higher level and struggling.

Non-Big-Tech Companies: A Different System

Most companies don't use numbered levels at all. They use titles: "Associate Software Engineer," "Software Engineer I," "Software Engineer II," "Senior Software Engineer." The meaning of those titles varies by company and has no universal standard.

A "Software Engineer I" at a 200-person fintech company may be doing more complex, higher-responsibility work than an L3 at Google, or less. You can't tell from the title alone.

For compensation research at these companies, you need to look at what they actually pay for those titles, using sites like Glassdoor, LinkedIn Salary, and Blind, and compare them to your local market and company stage. Salary data for software engineers in 2026 gives a useful starting point for calibrating these numbers.

What doesn't translate between systems: the promotion timelines, the rubrics, and the level definitions. An L3 at Google takes roughly 12-18 months to get a promotion shot at L4. At a startup, "when do I get promoted" depends entirely on the company's culture, growth stage, and your manager's relationship with the founders.

If You Land Lower Than You Expected

Getting leveled at a standard new grad level rather than one level up is not a failure. It's the norm. But if you feel strongly that you were leveled incorrectly, you have a few options.

First, ask your recruiter how leveling decisions are made and what would have led to a different outcome. Most will tell you honestly. This is not a negotiating tactic. It's information that helps you understand the process and calibrate for the future.

Second, if you have a competing offer at a higher level, share it. Recruiters expect this and it's a legitimate input to the process.

Third, accept the offer if it's otherwise good and plan to demonstrate senior behaviors quickly. Promotion cycles at Big Tech companies are rigorous but real. L3 engineers who operate like L4s get promoted. Track your impact from day one.

Looking Ahead

The level you start at matters. It shapes your first year's comp, your promotion timeline, and the expectations on you. But it's one input, not a verdict.

What matters more over time is whether you're growing, whether you're building the right habits, and whether you're operating at a scope that prepares you for the next level. What your first 90 days as a software engineer should focus on connects directly to this. The habits you build early set the trajectory.

Focus on the work, build your track record, and the level will follow.