12 ms·
This is very wise: "When I was at GM, you were a failure if your next move was not up—managing more people or taking on bigger, more complex projects. For many
by cmrdporcupine 6y ago
This is very wise:
"When I was at GM, you were a failure if your next move was not up—managing more people or taking on bigger, more complex projects. For many, this made for a miserable career path"
As I've said before, I think this is a corrosive aspect of the perf/promo process at many FAANGs. The "level" system encourages/pushes people to "upgrade" in this manner, and I think contributes to a number of problems. For one, organizational incompetence when people who were valuable contributors where they were are elevated up into roles where they no longer can apply those skills as effectively (i.e. technical team lead to management or architect) leaving a vacuum below. A form of the Peter Principle I guess, except the individual may have competence in their new role but not be happy, or make the team itself less successful.
And most importantly, as he touches on: being asked to 'level up' and told that this is your mission can lead to an unpleasurable career. Either when you do get that promo and then find that you don't enjoy the new responsibilities (but become trapped by the position / upgraded compensation etc.) or when you don't get the promo (or don't try) and find that your value in the eyes of yourself and others seems less.
And finally, I think this type of thing can really take hold in places with a highly academic background / focus / origin (like Google, etc.) as it mimics in many ways the grade / peer review achievement structure of academia. And that reward / grading structure may not at all correspond to either the monetary or cultural success of a corporation.
Smaller companies looking to grow/formalize should exercise caution when looking at the rating/performance/promo process @ FAANGs / MS as a model for their own.
(I'm at 20-25ish years in the industry, but really feel junior in so many ways when I read the words of veterans like this.)
- mathattack 6y agoYes. The challenge is how to measure individual contributors. It’s easy in Sales, which is why salespeople can do very well without being managers. Harder with engineers, whose work is very interconnected.
- cmrdporcupine 6y agoFor sure. And it's why frankly in my opinion it's very hard to scale software development effectively beyond 25-50 engineers. After that politics and faux-meritocracies take over as people lose personal touch with each other. Not that small companies can't be hell, too.
- mathattack 6y agoYes. Most good people know who the other good people are, but it’s hard to turn that into a plan fit for large companies.
- guytv 6y agoTeam mates, usually know who is a good engineer, and who's not - much more accurately than management. When I was in Google, Perf process was based on peers feedback, and it worked well.
- mathattack 6y agoHow much variable in rewards and comp are based on the peer reviews? Another challenge with large firms is the overall lack of variance.
- Accujack 6y agoExpecting a talented software engineer to "upgrade" to become a manager of a development team makes exactly the same amount of sense as expecting a talented accountant to gain a bit more skill and suddenly become a lawyer.
- karmakaze 6y agoIt might be closer to a pro athlete retiring from playing and going into coaching, but not so many would be good in that role.
- rileymat2 6y agoThis is interesting I did a bit of Googling, I guess it varies by sport quite a bit. https://www.post-gazette.com/sports/around-the-league-nfl/2014/08/24/Why-NFL-coaches-rarely-rise-from-ranks-of-players/stories/201408240108 https://www.post-gazette.com/sports/around-the-league-nfl/20... Some sports, most coaches came from players, but the NFL notably does not.
- bradstewart 6y agoI wonder if team size has anything to do with that. Football teams are much larger than those in other sports.
- justinwp 6y agoHaving been employed at Google for about nearly two years, your take doesn't seem accurate at all. > And that reward / grading structure may not at all correspond to either the monetary or cultural success of a corporation. The key feedback/suggestions I see for my own performance review is to define my impact on both the monetary and cultural success of my org. Exactly the opposite of what you are saying. > being asked to 'level up' and told that this is your mission can lead to an unpleasurable career I don't see this happening either. I commonly hear others say the opposite and make it known they are no longer trying to level up and that they are happy where they are. > technical team lead to management or architect This does not jive at all with the various career ladders I see. There is no ceiling that requires me to move to management in my tech ladder. > find that you don't enjoy the new responsibilities To some extent, the promo process levels up employees already working at that n+1. Sure, some may not want to maintain that, but that is ultimately up to the individual. Disclaimer: I work at Google, opinions are my own.
- cmrdporcupine 6y agoI also work at Google and in my 9 years there I've never had a perf process where monetary or profit-success goals of the company were mentioned once. EDIT: I guess when I worked in ads, there were ad performance type metrics discussed to some degree. Not much though.
- justinwp 6y agoGoes to show how diverse a large company can be even with the same underlying processes.
- cmrdporcupine 6y agoI think there are product areas in the company that lend themselves more to this, for sure.
- ThrowawayR2 6y ago> "to define my impact on both the monetary and cultural success of my org" What you get out of that is people frantically chasing impact and visibility instead of focusing on the humdrum drudgery of keeping the lights on. The result is penny wise and pound foolish behavior that definitely does not correspond to the monetary or cultural success of the corporation. People who are good at gaming the system in this can create their "impact", collect the rewards, and make an internal transfer before the costs or superficiality of their "impact" catch up with them.
- duxup 6y agoFirst real job I had there was this guy who had one specialization. He was in charge of some software that drove tape drives. Every outside new manager would come in and in some form or another look down on this guy in some form due to his age and generally not doing "a lot" of tasks and new products. It took the local VP to come down and regularly high five him after his product git rave reviews from customers (regularly) and make the point every time some manager didn't get it. That guy's code, documentation, everything was rock solid, and the number of support cases for everything he did was so low that the dude was without a doubt the most productive person as far as income goes. You could sell the product that he worked on and just rake in money with almost no costs after that. Almost everything else had a lot of support costs and etc. Meanwhile the guys who were doing all the new stuff, sucked at trying to juggle 12 things because it looked good on a resume.
- riku_iki 6y agoThat guy could perfectly be some tech lead, establishing his rock solid approaches on team of junior 4-10 engineers and delivering rock solid new products.
- jdbernard 6y agoNot everyone has the disposition to teach and lead.
- sli 6y agoBefore we even get to disposition, some folks simply do not want to do those things.
- duxup 6y agoI didn't say it outright but I picked this guy as an example as ... hey ABSOLUTELY did not want to lead anyone / should not lead anyone. Very much the high performer type who SHOULD NOT 'progress' to management or supervisor or ... reviewer of any sort. He was professional, but "prickly". I found the keys to get along with him but a lot of folks didn't have the patience.
- cletus 6y ago> As I've said before, I think this is a corrosive aspect of the perf/promo process at many FAANGs. So I have to ask: do you or have you worked at a FAANG with these systems? I may be wrong but I suspect you haven't, particularly if you're equating them with more traditional hierarchies. The whole point of a system like this (and I have direct experience at Google and Facebook) is so you can go pretty far as purely as an IC. You're not forced to become a manager. So at Google for example, new hires start as a T3 (T4 for PhDs). There is an expectation for growth up to T5, meaning technically you are meant to progress over time. When I was there this wasn't strictly enforced (eg I knew people who had been T4 for 5+ years) but it may vary from PA to PA or manager to manager and it may well have become stricter. IIRC the general guidance was 2-3 years T3 to T4 another 2-3 years for T4 to T5. At that point you can sit at T5 forever if that's what you want to do. People's desire to get promoted leads them to becoming managers because it is demonstrably easier to promoted from M1 (T5 equivalent) to M2 as en EM than it is from T5 to T6 as an IC. These higher levels are really an indication of your organizational and technical impact and for this you really have to influence others. This is not being a people manager however. But the point is that there's no "up or out" (beyond T5) like you may find at IBM or KPMG. Now there are definite issues with Google's approach here and that's really a whole other topic. I just don't think your observations here adequately describe the FAANG career paths (IMHO).
- cmrdporcupine 6y ago> So I have to ask: do you or have you worked at a FAANG with these systems? Yes, 9 years at Google. But yes, not experience beyond the L4/L5 tier. It is true that the IBM type structure isn't the same, and yes, Google is fine with you staying around L5 forever (well, L4 now). But the matrix of things to get beyond L4 really is, in the grand scheme of things, about moving beyond development and into delegation, or at least ownership. It's not management, but it is about leadership/cross-team collaboration and "demonstrating impact" to others. So, like I said elsewhere, small-p political. At least that's my experience from seeing the L4 to L5 transition. But it may also be a product of my smaller office, where the number of projects is smaller, team size is smaller, and larger technical contributions of impact are harder to find. EDIT: Also I've seen a lot of change in the 9 years, in terms of how the organization as a whole behaves, and it is becoming more and more like a traditional BigCorp. I just checked percent/ and within engineering 86.43473% full-time employees are newer than me. And a lot more if you count non-engineering. It is a way larger company than I started in. EDIT2: I should underline, that the perf/promo process obviously works for a large, perhaps the majority, number of people. But it doesn't for all. It requires adapting to an organizational model that not everybody accords with. And I think that's in the spirit of the original topic: organizational structures / procedures that become your career goals may not make you happy, so find a company whose process matches what you want to get out of life. Or try.
- macjohnmcc 6y agoI'm happy to lead as long as I also am allowed to work on the code itself from design to actually writing code. I have been doing this full time for 35 years and I would be miserable had I switch to a pure management role at any point including now. Meetings kill motivation for me.
- ralphc 6y agoI was 33 years in the industry, as a developer. Some times I considered going into management, and was asked about it, but fairly early on I realized I would hate it and it would hate me.
- sli 6y agoI'm about where you are, but when I read the word of veterans like this it just galvanizes my desire to leave the tech industry.
- dave_sid 6y agoI’m with you
- cmrdporcupine 6y agoDon't get me wrong, me too. I just want to retire and write code for fun.
- Gibbon1 6y ago> Smaller companies looking to grow/formalize should exercise caution when looking at the rating/performance/promo process @ FAANGs / MS as a model for their own. Robert Townsend had a comment that stuck with me, you don't get to be GM by behaving like GM. Which is beware of cargo culting successful organizations as they exist now. I'll also suggest don't cargo cult hyper funded startups if you aren't one either.
- irrational 6y agoI think of it as vertical vs horizontal career path. Vertical is becoming a manager of more and more people and/or projects. Horizontal is becoming an expert at more and more technologies/languages/etc.
- barnacled 6y agoThere is a corollary to this - having a career of sideways moves and simply not progressing even in ways that are positive and to your liking because each move effectively puts you back to zero and companies taking advantage of the 'flat structure' myth to avoid having to provide career progression.
- WaitWaitWha 6y ago> I think this is a corrosive aspect of the perf/promo process at many FAANGs Disagree on personal experience with two of the FAANG Cos I have worked for. A person content in their position, performing/delivering as expected can (and many do) coast. There was little to no pressure from these firms to "move up or move out".
- Vadoff 6y agoAt FAANG there's always an IC track and management track. Additionally, promotions are almost always lagging, meaning the individual needs to performs at that level for some time before being promoted.