|
|
|
|
|
|
by sangnoir
1624 days ago
|
|
|
You may have misread my comment - I said 1 director[1] to every 15 L5s. > And I believe the moment you said "1:3 manager to L5 ratio" your interviewer would give you a subtle but questioning look and expect you to revise that. I deliberately chose a high number to show that the number of Director interviews is still large after steelmanning your PoV (at the lower boundary of director-to-L5 ratio): I don't imagine many teams have 3+ L5s on them. Also, in the spirit of learning, could you perhaps plugin numbers that you think are more reasonable (L5 per team, and number of teams a director is responsible for)? 1. I'm calling the L5's skip-level manager a Director - I'm assuming that's what they are called at Google, but I could be wrong. That's the ratio I'm calculating |
|
|
L6 is Engineering Manager 1. That's how far up an L8 is.
And L6s are usually estimated to be 10% of Google. You can assume that there are order of magnitudes fewer devs each time you go up from there.
Also to be clear, it's extremely to be hired into Google higher than an L6. Even getting hired in as an L6 takes more experience than it does to join as an L5 and become an L6.
Most L6s at other FAANG companies would be downleveled without a very very strong performance, so getting reached out to as an L8 is not a small deal...