Perhaps not a wise move at a firm where it is within the reach of almost all staff to consider the org chart as a binary tree and analyze the changes mathematically.
The word "senior" varies by level for different job tracks -- for some it's not even until L7 (or at least it was this way in the past).
But my understanding is that, across most job tracks, it's expected that everyone should get promoted to L5 eventually just by working hard.
While it's never expected to get to L6. You might get to L5 and just stay there forever. L6 requires a certain level of achievement that they don't expect everyone to be able to achieve. That's what sets it apart.
So it makes sense this is the level where they're closing the gate even more.
Eh, you're a senior SWE at L5 in a lot of companies, but L6 is definitely where you start to be seen as closer to management in the chain than your typical IC. You start being involved in calibration for example.
L5 is mostly about reaching greater depths with your skills as an L4, L6 is more about gaining breadth that isn't guaranteed just by being an L5 for a while
Senior Software Engineer is indeed the title for L5 SWE at Google. However, whether a "senior software engineer" title is considered "senior" in a general sense these days is debatable.
Not Google but I worked at a mid-size US based company briefly last year.
The team was junior but senior in titles and highly opinionated, that was why I ended up leaving as nothing was getting done. Not last week I got a bunch of LinkedIn updates saying “Congratulate X being promoted to Senior/Staff/Principal Engineer”.
The grads I worked with who were good and what you expect for a grad where getting promoted to senior’s and the seniors who were ok, maybe a little inexperienced were getting promoted to staff.
I think roles mean nothing these days. They’re devalued and only exist for people to move up in to the next pay band.
What I consider senior from 15-20 years ago is staff engineer now and principal today feels like someone at the top of senior 15-20 years ago.
There are a lot more people in the field today so the standards have dropped as is necessary. Principal is top x%, senior is top y%, etc. It's not capability based.
L5 used to be the first terminal level, meaning that you could stay at L5 for as long as you liked as long as your performance was good. (Nowadays that so-called "growth expectation" has gotten a lot fuzzier, with some orgs letting people stay at L4 or even L3 for many years.)
So L6 was the first elective level. Anyone who reached it did so by opting in, rather than just going with the flow. That is why it carries a bit of weight.
All this was more true back in the 2000s. (Source: me, ex-Googler, 2003-22.)
This isn't surprising. "With our slower pace of hiring, we are planning for fewer promotions into L6 and above than when Google was growing quickly." Pretty straightforward, when you have fewer employees you need fewer leadership roles.
This window to self-nominate (6-8 Match, so starting today) is ahead of the layoff decision for many of the European offices. There will be people who have spent the last month prepping for promo only to get the axe in about 10-15 days.
Different countries have different employment regulations. Layoffs in the US hit in January, but layoffs in other countries have been slowly rolling out as leadership figures out how to deal with various laws. Nobody in London has been laid off yet, for example. They are still waiting to find out who will be axed.
What an odd message to fire across all employees. For an industry that wants so desperately to believe in meritocracy, to admit that there is a somewhat hidden quota on how many people you want at a given level feels to give the lie to the idea that it is strictly merit based.
No that doesn't make sense. Meritocracy doesn't automatically mean "promoting" someone when they have checked some boxes. That's actually the opposite. I see lots of people that approach work as if it's public school, that if they do the things the need to pass grade 4, they get into grade 5, and lots of companies pretend it's that way for junior roles.
There is a "quota" for each level, it's driven by the business need. That has no relationship with merit based promotion.
I hate to play the definition game, but "government or the holding of power by people selected on the basis of their ability" is given for meritocracy. If your ability is that you are at that level, you should be held to that level. If this is a meritocracy.
If promotion is also bound by availability of "slots" at a given level, than by definition you will exclude some folks that are otherwise at that level.
I fully sympathize that inflation of level is a thing. I also fully sympathize that resources to use people at a given level are finite. Such that you will have to do this for practical reasons. Still, the message for that is almost certainly tailored to the individual that you turned down and best left for the specifics. Blasting out this message as generically as it was done just feels wrong.
Aside (and this is not meant as a rebuttal), it’s interesting to me that nobody denies that managerial roles only have so many “slots” (e.g. can’t have 5 CTOs or 7 VPEs, or Directors managing teams of 2 people), and yet, nobody decries the lack of opportunities for those in the management track.
Me thinks you just don't listen to enough people complain? :D I've certainly heard those complaints. More than a few times.
Now, I'm fully onboard with what I think I read as part of your main point here. Management is a skill and it can be funny how few folks in the non-management world will acknowledge that. You can see similar with coaches. And it seems to be human nature that we love building a hierarchy up to a single point. Even in very distributed organizations.
Meritocracy has never been about that. It's always about filling the necessary roles with the best qualified people available. The purpose of meritocracy is not about rewarding people who meet arbitrary thresholds with fake titles and higher compensation. It's about giving the organization better chances to reach its goals. If you have the ability to perform at a higher level but there are enough people with even more ability, you won't get promoted in a meritocracy.
I mean, I know that it can be justified in many ways. But, know that if you have positions that are filled and only promote new ones when "merit is matched by availability," than you are bound to have some people that are more qualified than those in the currently held slots. Which will again hamstring the spirit behind the idea that this was the "best qualified people available." It is at best that with the added "at that time."
And you are trying to allude to inflation of role and expectations, I suspect? And that is a thing. But since you don't demote people that fall behind on the inflation, you are back to my first paragraph. That or you are pushing out the folks to make room, but you will regret pushing out some folks from the highest levels.
Meritocracy is fundamentally about the needs of the organization. It's about making the organization more effective.
It's common that there are people who would be more qualified to a position than the person currently holding the position, as long as we view merits in isolation. But the real ability the organization cares about is the ability to advance the goals of the organization when working within the organization. If replacing a person with a "more qualified" one demoralizes other employees enough that the organization's ability to reach its goals is compromised, the replacement is actually less qualified than the original person.
There is no "business need" like this at Google. This is a company swimming in cash for where most individuals' work has little relevance to revenue bottom lines or business success.
They'll kill or promote entire products because a given product area's position shifted in position on an org chart, or because some set of people involved don't feel they can get promotions or corporate success anymore from it.
The drive is political success. The criterion is openly about ability to promote and politic one's work. ("Demonstrating impact", key emphasis on "demonstrating". Written PRDs and design docs, name prominently placed, recognition from peers. Esp if they're on other teams, etc.)
It's frankly what you get when you have a company founded by academics who never worked in industry (but know all about defending your thesis to a committee, or "publish or perish") combined with unbounded revenue and seemingly infinite growth.
Might be true for management or leadership positions. Less true for IC roles. I find those roles tend to see promotions doled out when companies are desperately trying to keep people from leaving.
The old system was always "define each level based on business objectives and expectations and then promote people when they are demonstrating that they are hitting those objectives and expectations." So you couldn't be promoted to L7 unless there was a business need for an L7 because you must be doing L7 work, which requires a business need.
Most everything I've seen about advancing beyond "career-level" (usually into a "staff+" engineer track) has said that ability alone will not get you a promotion. In general, there needs to be a "business need" for those positions to be created in the first place.
It does not run contrary to the idea of meritocracy to assert that a firm has limit on the number of people that it can hire into a certain position - so long as the people who do fill those are selected are (more or less) the most qualified. Note that I am not saying anything about whether Google actually meets this ideal.
I mean, at a very real level, that is true for all positions. If the business doesn't have a need to pay you at a level, they won't do so.
I thought I had just always heard pride from the Google sphere about how they were much closer to the ideal of a meritocracy than other places. This feels... not that. :D
Tech isn't and hasn't been a meritocracy, I think a lot of people are having to grapple with this idea this year. Worse, a lot of people are also finding out that high salaries of tech often aren't worth it when you're forced to work in very expensive areas that negate much of that salary. There's a bubble that popped this year, and much of it was what the idea of tech to some people was.
Not at Google. Most of those things are decided for your manager with no knowledge of the person they're for. Your peers can affect your total comp by about 3 figures. Your manager can directly affect your total comp by about 4 figures. If you really go above and beyond your director can bump that to 5 figures. For anything bigger than that you'll need a promo. Bonuses, refreshers and raises were all clockwork.
Only sort of. Merit lines suck this year and O/T ratings are consumed by people on the promo track. Managers get little discretion for salary/bonus payouts. There is much more discretion for equity, but tons of line managers aren't equity planners and my experience is that equity discretion largely goes to people above L5.
I've got a high performing L5 who is critical to the success of my team. My discretion on their raise was largely undone by my director and nobody acted on my recommendation that they receive discretion on their equity refresh.
I'm not saying it is strictly merit based. But saying you are limiting the number didn't mean it isn't merit based. The idea is they still want to take the top x people, it is just that x is smaller.
Or a better way to look at it, is they are just making it harder. Someone who got promoted a year ago may not get promoted now. Didn't mean it isn't merit based
Meritocracy became racist, sexist, extremist, and various other -ists and -isms many years ago. A corporation like Google wants to be seen as supporting meritocracy in the US about as much as they want to be seen as supporting gay rights in Saudi.
Leveling at Google is supposed to be based on impact and the type of work you do. It isn’t about leadership. Going from L5 to L6 doesn’t make you a manager.
This is just a cost cutting measure as we all know. (Former googler)
If you're a former Googler, then you know that the role description for L6 indicates that an L6 is indeed supposed to exert a lot of leadership and influence, even if not a manager.
Yes, exactly. This is the case in a lot of other large companies. It basically enables management to fuck it up royally and repeatedly while the more senior engineers, which ambiguously defined technical leadership roles added to their IC responsibilities clean it up and keep the lights on.
All promotions beyond L3->L4 involve a leadership component for some definition of leadership.
Even L4->L5 promo is more than just demonstrating technical impact or ability. It involved being basically the key contact and coordinator on some project(s), "owning" some area and doing a bunch of cross-team collaboration. Being the loudest guy in the room for some thing, really. The impact that needs to be demonstrated from L4->L5 is in large part organizational/political, not technical.
I understand that L4->L5 was "fixed" after I left to leave a lot more room for immediate manager opinion/involvement. That's probably a good thing, because L4 to L5 was bullshit, especially at a smaller site where impactful work was hard to get.
Anyways, it's all stupid perverse incentives. People shoving each out of the way to grab the impactful work rather than cooperating. All over the place.
For those unfamiliar, Google engineering levels generally go from L3 (new grad) to L9 IDistinguished SWE). There is an expectation of growth to L5 (Senior SWE). I'm not sure what the figures look like today but pre-layoffs the total comp for an L5 Google SWE was typically at least $350k and can be over $400k.
Everyone who has been in this sytem knows that the bar to get to the next level (L6; Staff SWE) is gotten increasingly difficult. You packet will go through multiple promo committees and has to pass all of them. What would've gotten you promoted 10 years ago certainly wouldn't today.
But here's how promo committees work: you'll basically get stack ranked. That committee might have 10-15 packets and they'll get ranked. A certain point (usually called the bubble) will differentiate between promote those above the bubble, don't below. Committee consist of higher level ICs so a L5->L6 committe will consist of L7 ICs.
There is and probably has been a target percentage for promotions. This number is opaque. One of the things that Ruth Porat did when she came in to reduce costs was simply to reduce the promotion target percentage. I'm having difficulty finding the original leak for this but it leaked several years ago.
What slots there are to get promoted at these companies are probably filled by a revolving door of external hires.
So this is just more attacks on labor costs while executive pay is astronomically high and Google made a profit of ~$60B last year.
In addition to your points, if you go for promo once, you may have an easier time of it the second try (if your manager gets senior leads to back the idea for the next round), but if you try twice and fail both, you may as well leave the company.
+100 to the "revolving door of external hires". I was let go in the January action after almost 8 years of doing the same thing at Google. During that time, I saw 3 Cloud CEOs and I personally had 6 directors and 9 VPs. Change isn't always bad, but Google clearly does not value leadership & management as skills in the same way most large corporations do.
The leadership churn you mention is very real. The joke at Google even when I worked there (2017) was every few months you'd get an email saying your manager's manager's manager's manager now reports to a new manager. You didn't know nor had ever met any of these people.
I have a theory about this: middle management likes churn because it makes you immune to the consequences of their actions. You can't fail if none of your decisions are permanent and you constantly shift responsibilities. That's not an accident. It's by design.
My experience at Google was this was a huge problem.
>71. Now you see this at work with mistakes. You can make mistakes in the work you do and not suffer any consequences. For instance, I could negotiate a contract that might have a phrase that would trigger considerable harm to the company in the event of the occurrence of some set of circumstances. The chances are that no one would ever know. But if something did happen and the company got into trouble, and I had moved on from that job to another, it would never be traced to me. The problem would be that of the guy who presently has responsibility. And it would be his headache. There’s no tracking system in the corporation. Some managers argue that outrunning mistakes is the real meaning of “being on the fast track,” the real key to managerial success. The same lawyer continues: In fact, one way of looking at success patterns in the corporation is that the people who are in high positions have never been in one place long enough for their problems to catch up with them. They outrun their mistakes. That’s why to be successful in a business organization, you have to move quickly. (Location 2013)
Am I the only one shocked their commercial legal contract systems had zero way to trace that back, even with track changes from an old contract version with their name or approval logged somewhere?
It's less about forensics and more that the statute of limitations, so to speak, has run. What's the point in holding some regional director responsible for something that happened four levels and two teams ago?
I left in 2017 and it was still the expectation then but there was a lot of variance in orgs and with particular managers and ICs.
For example: I had known at that point people who had been L4 for years. I think 8 years was the longest I encountered. So you're right there wasn't a strict "up or out" culture but that was always the case.
The problem was if you were a long-term L4 one management change could suddenly put you in the hot seat. A new director may decide they like "up or out" so even though you had 8 years of EE+ ratings, you suddenly were vulnerable if you didn't get promoted.
Back when I worked at Google L4 and L5 promos were done by committee. These are now done in-org by leadership. This is both better and worse. It also makes long-term L4s less likely to happen. Interestingly these promotions still have target percentages. The first time it was tried they had to un-promote some people because too many got promoted.
My recall there was an explicit policy change that was communicated from the top around 2015 or so about this. Specifically about L4->L5. I recall it around this time because this is about when I got to 4 years of L4, and it was a relief to me because I really didn't want to have to go through the hassle of going through promo. My ratings were fine and I was happy with my comp and work, why would I get myself up to L5 and then start getting lower ratings at the new level?
FWIW, I was there 10 years, stayed L4 the whole time because I never wanted to go for promo because the whole process stunk. Left end of last year of my own accord (never liked the place). The only place where being "still" L4 caused me grief was from a higher up inside Access (Fiber), where they got pretend to play at being their own company for a while (with their own policies etc) after Ruth's Alphabetization -- and then they got the axe.
Ironically the new process they brought out a couple months after I left would have served me better and I would probably have ended up in L5 without having to politic for it. Though I hated the last project I was on, so.
In any case, agree about your other points. It's labour discipline coming to Google. Though I think it's less about cost and more about discipline/subservience.
There are a couple of problems with this (not the least of which is market signaling that Google is not a place to reliably advance one's career, for anyone but the most junior staff).
Clearly, it doesn't not make sense for everyone at a given firm to be in management. Facebook has recently come to this conclusion. That said, leveling and advancement at Google has always been about impact, and for the most part, employees have been able to vote with their feet (internally transfer) if they find themselves in roles that won't support "impact requirements" that justify promotion. It is utterly insane and short-sighted for Google to place such low value on things like KTLO work and optimization, and the result is the long list of deprecated and half-finished products we all know and love. The effects of these perverse incentives have been beaten to death so I won't belabor that here.
However, one thing I don't see discussed much is how this same impact-driven-promo behavior leads directly to both "rest & vest" and poor management.
It leads to rest & vest behavior by employees who no longer see a path upward so they cruise with minimal effort to maintain the status quo. Google as an organization does not reward Googleyness where the term is defined to mean "go outside your assigned tasks / projects to 'do the right thing'". In fact, it usually punishes people who are too Googley.
Similarly, it rewards poor management because these vast quantities of employees are typically peanut buttered in such a way that everything is broken all the time and new folks constantly need to be hired to keep things running. Empire building, further supported by Google's reliance on TVCs for literally every non-product-development business process (and many functions and processes that do directly support product). Nobody knows how anything works and (see punishment for Googleyness) nobody is willing to stick their neck out too far to try and fix/change anything. There are some absolutely terrific managers at Google, but management and leadership at Google is the worst I've ever come across in my 25 year working career.
This brings me to the final problem with this no-promo statement. Another common reason Googlers are dinged on perf or viewed negatively by their own leadership is when they repeatedly hit CME, maybe with a sprinkly of EE, ratings. Literally, if you are rated as "Meets Expectations" more than twice in a row you are flagged for extra review during perf calibration. If promos to L6+ are being reduced, then that logically indicates that there are fewer roles at Google scoped for L6+ impact. If that is true, then logically 1) top talent will leave (or not join), and 2) people currently in terminal roles (say an L5 SWE or an L6 TPM) have no real motivation to work harder than necessary to achieve CME since they know they can't get promoted and the bonus and equity multipliers between CME --> EE aren't really that great. Similarly, you end up with folks who, after a few years (max), are near the top end of the salary band for their level and will no longer be eligible for pay increases beyond a percent or two.
Tell me, who would want to work for a company that 1) doesn't value management as a skill, 2) doesn't have logical performance metrics in place that allow all employees to articulate why what they do is important, 3) doesn't offer opportunities for advancement, and 3b) will actually fall behind CoL pay increases within a few years as a result of #3?
Promotions aren't related to management at Google, unless you're on the management track. If you get promoted as a engineer, you're still an engineer. You might be a tech lead but you're not a people manager.
This just reinforces what I've been saying for years: seeking promotion is for chumps.
You'll make far more money and advance far quicker from job-hopping between companies than you will trying to seek internal promotion.
Google, and pretty much big tech as a whole, is completely aimless at this point and has no real plan to provide new value to customers. They just jump from shiny thing to shiny new thing. Big tech has only been able to maintain it's recent dominance through monopolistic practices, and now they've mismanaged themselves into decline. Good.
E5/L5 compensation is relatively similar across the board for normal performers ($350k-$450k). Once you get into the E7+ compensation levels, then you start to notice a real differences.
Riggght? Every couple months my managers start harassing me about going for promo. Chill out. I just want to write code. The higher L I am, the more pointless meetings I have to endure and the less code I can write. Do you not want people that actually get things done, competently? Or do you want to save all the coding for the L3s so we can really double down on that tech debt?
FWIW. I don't read this as disdain, just stating the fact that less experienced people make more mistakes or may have less experience avoiding tech debt. It's hyperbole of course (I hope) because L4/L5s should be reviewing that code, but the point I believe is that coding is sometimes too quickly removed as a valuable activity for L5s and above.
The commenter wasn't saying that the L3s "may have less experience avoiding tech debt"; but that they are, by default, to be viewed as creators of technical debt.
Which I guess we all are, at the end of the day. Still there's a snarky edge to the wording in that comment that I find hard to get past.
Maybe it is really important to know precisely what an "L3" is, and since I've never worked for whatever company this is I'm unsure; but, FWIW, as someone who was just casually reading the comment, it didn't really come off as snarky in that sense, as if you are forcing all the strongest coders to get promoted then by definition the people who are lower in the org chart are weaker coders, at which point the comment just "made sense" and didn't seem at all to offer actual "disdain" towards anyone except the promotion system (which maybe should itself be a reason to quit, but hopefully they are being paid well).
That said, I guess my explanation for the phenomenon--as someone outside such systems--is that in fact these organizations want weaker people at the bottom doing the grunt work as they are easier to control: they are all about figuring out how to build systems out of interchangeable cogs, under the premise that if you do enough build engineering then you can take almost any competent coder and get at least some contribution out of them (even if you end up needing ten times as many employees as a tradeoff).
I like your theory, which seems to explain a lot of things (like why I'm not attracted to such organizations, for example). Especially the last part:
In fact these organizations want weaker people at the bottom doing the grunt work as they are easier to control: They are all about figuring out how to build systems out of interchangeable cogs, under the premise that if you do enough build engineering then you can take almost any competent coder and get at least some contribution out of them (even if you end up needing ten times as many employees as a tradeoff).
Corollary being: if the work itself is structured so that much of it is viewed as "grunt work" - then by definition, the people stuck doing it (L3s in this case) are viewed disdainfully.
The Great Resignation gave the individuals so much negotiation and purchasing power for a brief period of time as Big Tech companies lost people left and right to Web3 Crypto Unicorns (and other Unicorns in their dying gasps).
Amazon, Microsoft, Google, all lost so many people because their systems weren't configured to be able to quickly keep up with the new market trends. But Big tech cos had 2 things could control:
1. Newhire offer bands could rise quicker than internal salaries. (Leading to resentment that newhires were getting insane offers that long-term employees could never get in a raise). Which led to a lowering of the bar across all levels in Big Tech to get those offers out.
2. Promotion bars could be lowered likewise.
Neither was nefarious. Noone ever said at a high level leadership level "Lower the bar" (for either). But what did happen is that when great coworkers all around you are constantly leaving, the people remaining start to panic. They start to realize that that "almost senior" engineer who's "not quite there" and wouldn't have been promoted 6 months ago, will absolutely leave for a Senior title and a 30-50% salary bump if you don't promote him. (And still might if you do cuz you'll only give him a 15-20% salary raise). And suddenly, everyone starts "leaning in" to promotions.
Likewise, on interview loops, when you've lost a bunch of folks and are desperate to replace your headcount to meet your goals, you start talking yourself into candidates that you wouldn't have taken risks on 6 months earlier.
This is all basic human nature, and even experienced data-driven leaders will find themselves optimizing for different criteria and justifying it to themselves as thinking outside the box. I'm genuinely not judging, it's a reasonable and logical (albeit shortsighted) way to act under the circumstances.
So now, that all of this is behind us, these companies are all sitting on hiring freeze, post-layoffs, and still with a bunch of folks that are overlevelled.
An overcorrection is the only step forward. Lose even more folks because you now have to recalibrate their inflated sense of accomplishment or worse an overly optimistic sense of their opportunity ("Jeff got promoted and I'm way better than Jeff! So I should get promoted too." Yeah, Jeff wouldn't have been promoted in 2020 or 2023. So alas, too bad for you)
I think to some degree this will happen across all Big Tech this year. But unlike during the great resignation, there's no more unicorns (Except Facebook) throwing insane offers at ex-Big Tech.
I think things will go back to normal in 2024, for a definition of normal that is closer to 2014.
88 comments
[ 4.5 ms ] story [ 161 ms ] threadThat's not true? Isn't "senior SWE" the title for L5 at Google?
But my understanding is that, across most job tracks, it's expected that everyone should get promoted to L5 eventually just by working hard.
While it's never expected to get to L6. You might get to L5 and just stay there forever. L6 requires a certain level of achievement that they don't expect everyone to be able to achieve. That's what sets it apart.
So it makes sense this is the level where they're closing the gate even more.
L5 is mostly about reaching greater depths with your skills as an L4, L6 is more about gaining breadth that isn't guaranteed just by being an L5 for a while
Not Google but I worked at a mid-size US based company briefly last year.
The team was junior but senior in titles and highly opinionated, that was why I ended up leaving as nothing was getting done. Not last week I got a bunch of LinkedIn updates saying “Congratulate X being promoted to Senior/Staff/Principal Engineer”.
The grads I worked with who were good and what you expect for a grad where getting promoted to senior’s and the seniors who were ok, maybe a little inexperienced were getting promoted to staff.
I think roles mean nothing these days. They’re devalued and only exist for people to move up in to the next pay band.
What I consider senior from 15-20 years ago is staff engineer now and principal today feels like someone at the top of senior 15-20 years ago.
So L6 was the first elective level. Anyone who reached it did so by opting in, rather than just going with the flow. That is why it carries a bit of weight.
All this was more true back in the 2000s. (Source: me, ex-Googler, 2003-22.)
There is a "quota" for each level, it's driven by the business need. That has no relationship with merit based promotion.
If promotion is also bound by availability of "slots" at a given level, than by definition you will exclude some folks that are otherwise at that level.
I fully sympathize that inflation of level is a thing. I also fully sympathize that resources to use people at a given level are finite. Such that you will have to do this for practical reasons. Still, the message for that is almost certainly tailored to the individual that you turned down and best left for the specifics. Blasting out this message as generically as it was done just feels wrong.
Now, I'm fully onboard with what I think I read as part of your main point here. Management is a skill and it can be funny how few folks in the non-management world will acknowledge that. You can see similar with coaches. And it seems to be human nature that we love building a hierarchy up to a single point. Even in very distributed organizations.
And you are trying to allude to inflation of role and expectations, I suspect? And that is a thing. But since you don't demote people that fall behind on the inflation, you are back to my first paragraph. That or you are pushing out the folks to make room, but you will regret pushing out some folks from the highest levels.
It's common that there are people who would be more qualified to a position than the person currently holding the position, as long as we view merits in isolation. But the real ability the organization cares about is the ability to advance the goals of the organization when working within the organization. If replacing a person with a "more qualified" one demoralizes other employees enough that the organization's ability to reach its goals is compromised, the replacement is actually less qualified than the original person.
They'll kill or promote entire products because a given product area's position shifted in position on an org chart, or because some set of people involved don't feel they can get promotions or corporate success anymore from it.
The drive is political success. The criterion is openly about ability to promote and politic one's work. ("Demonstrating impact", key emphasis on "demonstrating". Written PRDs and design docs, name prominently placed, recognition from peers. Esp if they're on other teams, etc.)
It's frankly what you get when you have a company founded by academics who never worked in industry (but know all about defending your thesis to a committee, or "publish or perish") combined with unbounded revenue and seemingly infinite growth.
It does not run contrary to the idea of meritocracy to assert that a firm has limit on the number of people that it can hire into a certain position - so long as the people who do fill those are selected are (more or less) the most qualified. Note that I am not saying anything about whether Google actually meets this ideal.
I thought I had just always heard pride from the Google sphere about how they were much closer to the ideal of a meritocracy than other places. This feels... not that. :D
I've got a high performing L5 who is critical to the success of my team. My discretion on their raise was largely undone by my director and nobody acted on my recommendation that they receive discretion on their equity refresh.
This is just a cost cutting measure as we all know. (Former googler)
Even L4->L5 promo is more than just demonstrating technical impact or ability. It involved being basically the key contact and coordinator on some project(s), "owning" some area and doing a bunch of cross-team collaboration. Being the loudest guy in the room for some thing, really. The impact that needs to be demonstrated from L4->L5 is in large part organizational/political, not technical.
I understand that L4->L5 was "fixed" after I left to leave a lot more room for immediate manager opinion/involvement. That's probably a good thing, because L4 to L5 was bullshit, especially at a smaller site where impactful work was hard to get.
Anyways, it's all stupid perverse incentives. People shoving each out of the way to grab the impactful work rather than cooperating. All over the place.
For those unfamiliar, Google engineering levels generally go from L3 (new grad) to L9 IDistinguished SWE). There is an expectation of growth to L5 (Senior SWE). I'm not sure what the figures look like today but pre-layoffs the total comp for an L5 Google SWE was typically at least $350k and can be over $400k.
Everyone who has been in this sytem knows that the bar to get to the next level (L6; Staff SWE) is gotten increasingly difficult. You packet will go through multiple promo committees and has to pass all of them. What would've gotten you promoted 10 years ago certainly wouldn't today.
But here's how promo committees work: you'll basically get stack ranked. That committee might have 10-15 packets and they'll get ranked. A certain point (usually called the bubble) will differentiate between promote those above the bubble, don't below. Committee consist of higher level ICs so a L5->L6 committe will consist of L7 ICs.
There is and probably has been a target percentage for promotions. This number is opaque. One of the things that Ruth Porat did when she came in to reduce costs was simply to reduce the promotion target percentage. I'm having difficulty finding the original leak for this but it leaked several years ago.
What slots there are to get promoted at these companies are probably filled by a revolving door of external hires.
So this is just more attacks on labor costs while executive pay is astronomically high and Google made a profit of ~$60B last year.
Disclaimer: Xoogler.
+100 to the "revolving door of external hires". I was let go in the January action after almost 8 years of doing the same thing at Google. During that time, I saw 3 Cloud CEOs and I personally had 6 directors and 9 VPs. Change isn't always bad, but Google clearly does not value leadership & management as skills in the same way most large corporations do.
I have a theory about this: middle management likes churn because it makes you immune to the consequences of their actions. You can't fail if none of your decisions are permanent and you constantly shift responsibilities. That's not an accident. It's by design.
My experience at Google was this was a huge problem.
Sorry you were let go.
https://thezvi.wordpress.com/2019/05/30/quotes-from-moral-ma...
(It's a rhetorical question.)
This is out of date. "Up or out" from L4 was dropped around 2015 or 2016 or so. It was considered "fine" to stay at L4.
For example: I had known at that point people who had been L4 for years. I think 8 years was the longest I encountered. So you're right there wasn't a strict "up or out" culture but that was always the case.
The problem was if you were a long-term L4 one management change could suddenly put you in the hot seat. A new director may decide they like "up or out" so even though you had 8 years of EE+ ratings, you suddenly were vulnerable if you didn't get promoted.
Back when I worked at Google L4 and L5 promos were done by committee. These are now done in-org by leadership. This is both better and worse. It also makes long-term L4s less likely to happen. Interestingly these promotions still have target percentages. The first time it was tried they had to un-promote some people because too many got promoted.
FWIW, I was there 10 years, stayed L4 the whole time because I never wanted to go for promo because the whole process stunk. Left end of last year of my own accord (never liked the place). The only place where being "still" L4 caused me grief was from a higher up inside Access (Fiber), where they got pretend to play at being their own company for a while (with their own policies etc) after Ruth's Alphabetization -- and then they got the axe.
Ironically the new process they brought out a couple months after I left would have served me better and I would probably have ended up in L5 without having to politic for it. Though I hated the last project I was on, so.
In any case, agree about your other points. It's labour discipline coming to Google. Though I think it's less about cost and more about discipline/subservience.
Clearly, it doesn't not make sense for everyone at a given firm to be in management. Facebook has recently come to this conclusion. That said, leveling and advancement at Google has always been about impact, and for the most part, employees have been able to vote with their feet (internally transfer) if they find themselves in roles that won't support "impact requirements" that justify promotion. It is utterly insane and short-sighted for Google to place such low value on things like KTLO work and optimization, and the result is the long list of deprecated and half-finished products we all know and love. The effects of these perverse incentives have been beaten to death so I won't belabor that here.
However, one thing I don't see discussed much is how this same impact-driven-promo behavior leads directly to both "rest & vest" and poor management.
It leads to rest & vest behavior by employees who no longer see a path upward so they cruise with minimal effort to maintain the status quo. Google as an organization does not reward Googleyness where the term is defined to mean "go outside your assigned tasks / projects to 'do the right thing'". In fact, it usually punishes people who are too Googley.
Similarly, it rewards poor management because these vast quantities of employees are typically peanut buttered in such a way that everything is broken all the time and new folks constantly need to be hired to keep things running. Empire building, further supported by Google's reliance on TVCs for literally every non-product-development business process (and many functions and processes that do directly support product). Nobody knows how anything works and (see punishment for Googleyness) nobody is willing to stick their neck out too far to try and fix/change anything. There are some absolutely terrific managers at Google, but management and leadership at Google is the worst I've ever come across in my 25 year working career.
This brings me to the final problem with this no-promo statement. Another common reason Googlers are dinged on perf or viewed negatively by their own leadership is when they repeatedly hit CME, maybe with a sprinkly of EE, ratings. Literally, if you are rated as "Meets Expectations" more than twice in a row you are flagged for extra review during perf calibration. If promos to L6+ are being reduced, then that logically indicates that there are fewer roles at Google scoped for L6+ impact. If that is true, then logically 1) top talent will leave (or not join), and 2) people currently in terminal roles (say an L5 SWE or an L6 TPM) have no real motivation to work harder than necessary to achieve CME since they know they can't get promoted and the bonus and equity multipliers between CME --> EE aren't really that great. Similarly, you end up with folks who, after a few years (max), are near the top end of the salary band for their level and will no longer be eligible for pay increases beyond a percent or two.
Tell me, who would want to work for a company that 1) doesn't value management as a skill, 2) doesn't have logical performance metrics in place that allow all employees to articulate why what they do is important, 3) doesn't offer opportunities for advancement, and 3b) will actually fall behind CoL pay increases within a few years as a result of #3?
You'll make far more money and advance far quicker from job-hopping between companies than you will trying to seek internal promotion.
Google, and pretty much big tech as a whole, is completely aimless at this point and has no real plan to provide new value to customers. They just jump from shiny thing to shiny new thing. Big tech has only been able to maintain it's recent dominance through monopolistic practices, and now they've mismanaged themselves into decline. Good.
Half your compensation at FAANG is name recognition for your resume.
If you view your colleagues so disdainfully - why (other than comp) are you still working there?
The commenter wasn't saying that the L3s "may have less experience avoiding tech debt"; but that they are, by default, to be viewed as creators of technical debt.
Which I guess we all are, at the end of the day. Still there's a snarky edge to the wording in that comment that I find hard to get past.
That said, I guess my explanation for the phenomenon--as someone outside such systems--is that in fact these organizations want weaker people at the bottom doing the grunt work as they are easier to control: they are all about figuring out how to build systems out of interchangeable cogs, under the premise that if you do enough build engineering then you can take almost any competent coder and get at least some contribution out of them (even if you end up needing ten times as many employees as a tradeoff).
In fact these organizations want weaker people at the bottom doing the grunt work as they are easier to control: They are all about figuring out how to build systems out of interchangeable cogs, under the premise that if you do enough build engineering then you can take almost any competent coder and get at least some contribution out of them (even if you end up needing ten times as many employees as a tradeoff).
Corollary being: if the work itself is structured so that much of it is viewed as "grunt work" - then by definition, the people stuck doing it (L3s in this case) are viewed disdainfully.
Amazon, Microsoft, Google, all lost so many people because their systems weren't configured to be able to quickly keep up with the new market trends. But Big tech cos had 2 things could control:
1. Newhire offer bands could rise quicker than internal salaries. (Leading to resentment that newhires were getting insane offers that long-term employees could never get in a raise). Which led to a lowering of the bar across all levels in Big Tech to get those offers out.
2. Promotion bars could be lowered likewise.
Neither was nefarious. Noone ever said at a high level leadership level "Lower the bar" (for either). But what did happen is that when great coworkers all around you are constantly leaving, the people remaining start to panic. They start to realize that that "almost senior" engineer who's "not quite there" and wouldn't have been promoted 6 months ago, will absolutely leave for a Senior title and a 30-50% salary bump if you don't promote him. (And still might if you do cuz you'll only give him a 15-20% salary raise). And suddenly, everyone starts "leaning in" to promotions.
Likewise, on interview loops, when you've lost a bunch of folks and are desperate to replace your headcount to meet your goals, you start talking yourself into candidates that you wouldn't have taken risks on 6 months earlier.
This is all basic human nature, and even experienced data-driven leaders will find themselves optimizing for different criteria and justifying it to themselves as thinking outside the box. I'm genuinely not judging, it's a reasonable and logical (albeit shortsighted) way to act under the circumstances.
So now, that all of this is behind us, these companies are all sitting on hiring freeze, post-layoffs, and still with a bunch of folks that are overlevelled.
An overcorrection is the only step forward. Lose even more folks because you now have to recalibrate their inflated sense of accomplishment or worse an overly optimistic sense of their opportunity ("Jeff got promoted and I'm way better than Jeff! So I should get promoted too." Yeah, Jeff wouldn't have been promoted in 2020 or 2023. So alas, too bad for you)
I think to some degree this will happen across all Big Tech this year. But unlike during the great resignation, there's no more unicorns (Except Facebook) throwing insane offers at ex-Big Tech.
I think things will go back to normal in 2024, for a definition of normal that is closer to 2014.
That all? A decade? I have 2 decades. I'm an L4. Weeeee....