Targeting Roles & Levels
Applying at the wrong level is one of the most expensive mistakes in a job search. Apply too low and you spend years doing work beneath your capability for less money. Apply too high and you fail the interview bar or get a no-hire because the expectations did not match your experience. Understanding how levels work across companies, and honestly assessing where you fit, determines the trajectory of your career.
IC vs. Management
The first decision is whether you want an individual contributor (IC) track or a management track. These are fundamentally different jobs, not just different titles.
Individual Contributor:
- You write code, design systems, solve technical problems
- Your impact comes from your direct technical output
- Career ceiling is principal/distinguished engineer at top companies
- At senior levels, you influence through technical leadership
- You are evaluated on technical depth, design quality, and mentorship
Engineering Manager:
- You build and lead teams
- Your impact comes from making others more effective
- Career ceiling is VP Engineering or CTO
- At senior levels, you influence through organizational design
- You are evaluated on team output, retention, hiring, and delivery
Common mistake: becoming a manager because "that's how you advance"
- Many companies have IC tracks that pay as well as management
- A great IC who becomes a mediocre manager helps no one
- The transition is reversible, but switching back has stigma
Choosing Your Path
You should consider the IC track if:
- You love solving technical problems more than people problems
- You want to go deep on a domain (databases, ML, compilers)
- You get energy from building things yourself
- You do not enjoy meetings, 1:1s, and performance reviews
- You want your day-to-day to be technical
You should consider the management track if:
- You get satisfaction from helping others grow
- You enjoy the strategic side of technology decisions
- You are good at navigating organizational complexity
- You want to influence what gets built, not just how
- You can handle the ambiguity of people problems
Understanding Engineering Levels
Most large tech companies use a leveling system. The levels roughly correspond to experience, scope, and impact. The titles vary but the underlying structure is consistent.
The Level Spectrum
Level Typical Title Years Experience Scope
L3/E3 Junior Engineer 0-2 years Task-level work
L4/E4 Software Engineer 2-5 years Feature-level work
L5/E5 Senior Engineer 5-10 years Project-level work
L6/E6 Staff Engineer 8-15 years Org-level impact
L7/E7 Principal Engineer 12+ years Company-wide impact
L8+ Distinguished/Fellow 15+ years Industry impact
Years are rough guidelines, not requirements. Some reach L6
in 6 years; some never get past L5. Performance and scope
matter more than tenure.
What Each Level Actually Means
L3 (Junior):
- Given well-defined tasks with clear specifications
- Needs regular guidance from senior engineers
- Learning the codebase, tools, and team processes
- Impact: completes assigned work correctly
L4 (Mid-level):
- Owns features end-to-end with some guidance
- Can break down ambiguous requirements into tasks
- Contributes to design discussions
- Impact: ships features that work and are maintainable
L5 (Senior):
- Owns projects across a team's scope
- Makes technical decisions independently
- Mentors junior engineers
- Defines technical direction for a component or service
- Impact: shapes how the team builds and operates
L6 (Staff):
- Sets technical direction across multiple teams
- Resolves ambiguity in large, cross-cutting problems
- Influences engineering culture and practices
- May not write much code directly
- Impact: enables other teams to be more effective
L7 (Principal):
- Defines technical strategy for a business unit or company
- Connects technology decisions to business outcomes
- Recognized as an expert in their domain
- Represents the company externally
- Impact: shapes the company's technical trajectory
Level Mapping Across Companies
Different companies use different naming schemes. When comparing offers or targeting roles, you need to map levels accurately.
Approximate level mapping:
Google Meta Amazon Apple Microsoft Netflix
L3 E3 SDE I ICT2 59 N/A
L4 E4 SDE II ICT3 60-61 Engineer
L5 E5 SDE III ICT4 62-63 Senior Eng
L6 E6 Principal ICT5 64-65 Staff Eng
L7 E7 Sr Princ ICT6 66-67 Principal
L8 E8 Dist Eng Fellow 68+ N/A
Important caveats:
- These mappings are approximate, not exact
- The bar at each level differs by company
- Amazon SDE II is roughly Google L4, but the day-to-day
looks different
- Netflix has fewer levels with higher compensation per level
- Some companies have half-levels or sub-levels
Why Level Mapping Matters
Scenario: You are an L5 at Google and interviewing at Meta.
If you target E5 at Meta:
- You interview at the same level
- Expectations match your experience
- Likely outcome: offer at E5 with comparable compensation
If you target E6 at Meta:
- Higher compensation if you pass
- But the bar is significantly higher
- Interview questions test for organizational impact
- You may get down-leveled to E5 anyway
If you target E4 at Meta:
- You will likely pass easily
- But compensation will be below your current level
- You will be bored within 6 months
- Getting promoted quickly looks good but it wastes time
Applying at the Right Level
How Companies Determine Your Level
What determines your interview level:
1. Your resume (years of experience, scope of past work)
2. Recruiter phone screen (they calibrate during the call)
3. Your stated expectations (what level you say you want)
4. Referral information (if a current employee vouched for you)
You have some influence over this. In the recruiter call:
"I'm targeting a senior role based on my experience leading
the migration of our payment system, which involved
coordinating across 3 teams and reducing processing latency
by 40%."
This naturally signals L5/Senior scope without explicitly
saying "I want to be L5."
The Danger of Applying Too High
Too high:
- Interview questions are calibrated for a higher level
- For L6, they expect you to describe org-level impact
- You struggle to provide examples at the right scope
- Even if you pass the coding, the "leveling committee"
may reject you for insufficient impact stories
- Result: no-hire or down-level offer
Indicators you are applying too high:
- Your examples are all about features, not systems or org impact
- You have not mentored or led other engineers
- You have not influenced technical direction beyond your team
- You have less than the typical experience for the level
The Danger of Applying Too Low
Too low:
- You pass the interview easily
- Compensation is 20-40% below what you should earn
- The work is not challenging enough
- Promotion takes 1-2 years even if you are clearly above the bar
- Your resume shows a "step down" that is hard to explain later
Indicators you are applying too low:
- The job description matches what you did 3 years ago
- The compensation range is well below your current total comp
- You would be the most experienced person on the team
- The recruiter seems surprised by your background
Down-Leveling & How to Avoid It
Down-leveling happens when a company makes you an offer, but at a lower level than you interviewed for. This is common and frustrating.
How down-leveling works:
1. You interview for L5 (Senior)
2. The hiring committee reviews your performance
3. They decide your coding was L5 but your system design was L4
4. They offer you L4 with a note: "we'd love to promote you quickly"
5. The "quick promotion" usually takes 12-18 months at minimum
Why it happens:
- The company liked you but not at the targeted level
- It is cheaper to hire you at L4 than L5
- They genuinely think the bar was not met for L5
- It is a compromise between hiring and not hiring
How to Avoid Down-Leveling
Prevention strategies:
1. Calibrate correctly before interviewing
- Research the level expectations thoroughly
- Be honest about whether your experience matches
2. Tell impact stories at the right scope
- L5 stories: "I designed and led the implementation of..."
- L6 stories: "I identified the problem, got buy-in across
3 teams, and drove the technical strategy..."
- Match your stories to the level you are targeting
3. Ask the recruiter directly
"What level am I being considered for, and what does the
interview committee look for at that level?"
4. Practice system design at the right scope
- L4 system design: design a single service
- L5 system design: design a system with multiple services
- L6 system design: design a platform that other teams use
If You Get Down-Leveled
Options when down-leveled:
1. Accept and plan for quick promotion
- Only if the comp difference is small
- Get the "quick promotion" commitment in writing if possible
- Understand that "quick" usually means 12+ months
2. Negotiate the compensation up to near the higher level
- "I understand the leveling decision. Can we discuss
compensation that reflects my experience? I'd like
the offer to be at the top of the L4 band."
3. Decline and re-interview later
- Some companies allow re-interview after 6-12 months
- Use the time to strengthen the areas they flagged
4. Use it as a data point for other companies
- If Company A down-leveled you, prepare differently
for Company B's interview
Common Pitfalls
- Targeting a level based on years of experience alone — scope and impact matter more than tenure
- Not researching level expectations before interviewing — the bar for L5 at Google is different from L5 at a startup
- Accepting a down-level without negotiating — at minimum, push for top-of-band compensation at the lower level
- Assuming management is the only path to advancement — IC tracks at top companies go to L8+ with compensation above most VP roles
- Applying to too few companies — you need data points to understand where you actually calibrate in the market
- Ignoring the team when focusing on level — an L5 on a declining team is worse than an L4 on a high-growth team
- Chasing title over substance — "Staff Engineer" at a 20-person startup may mean less than "Senior Engineer" at Google
Key Takeaways
- Decide between IC and management based on what energizes you, not what you think you should do
- Understand the level system: L3 through L7+ represent increasing scope from task-level to company-wide impact
- Map levels accurately across companies — the same title means different things at different places
- Apply at the right level: too high risks a no-hire, too low wastes your time and money
- Prevent down-leveling by calibrating before interviews, telling impact stories at the right scope, and practicing system design at the targeted level
- When comparing offers at different levels, consider total trajectory, not just the title on day one