Leaving Google
jayconrod.com
jayconrod.com
Is it possible that it is simply because of survival? The general theme of business I see is if you do not keep up with others, you will lose to your competitors. Especially in a winner take all business with network effects and low marginal costs like tech.
Most businesses in the world survive with their piece of the pie and remaining having the same profits or slightly lower/higher than previous years. You don't disappear over night, and no market is really a "winner takes it all", it's just what management wants you to believe so you fight the good fight for your company.
I am not sure if that is called survival.
And no, most businesses in the world do not survive that long. Lifetime of businesses are often much shorter than lifetime of humans. Even many of them that look like have survived may share the name only and are effectively new businesses.
This assertion presumes that it is impossible to propose any form of compensation that's enticing without involving stock. This is not only baseless but also flies in the face of reality, as other tech companies, including other FAANGs, barely offer any stock and still manage to attract top talent.
With a gross profit of 100 billion dollars a year [1] they can easily outbid the market compensation if they want to and stay with current revenue. But again how many Jeff Deans can one company need before it calls itself The Man?
[1] https://www.macrotrends.net/stocks/charts/GOOG/alphabet/gros...
Market for OSes for PCs (not Macs) is a great example. Windows has what, 98% market share there? It got there thanks to the dynamics of this particular market, which is totally a "winner takes all" one. In particular, if Microsoft were more relaxed in 80ties and 90ties, there likely would not be Microsoft or Windows at all today, and everybody'd be using Os/2 Warp or BeOS or something else on our PCs.
While this may be the case for capital-intensive businesses (oil, consumer goods, energy), this is usually not the case for intangible-asset businesses (media, tech). In the former, the assets will generate cashflow, whereas in the latter it's a people-centric model
What was the last time you chose yahoo over google or altavista over google?
Google was always greedy, but when it was small it was cool to be the disruptor. Now it's perceived as only greedy. This is typically the case for any successful company (from HP, IBM, to the new 'big tech').
Good (related) book recommendation btw: capitalism without capital
Everything a capitalist market teaches us is against this, if they don't obsolete themselves before somebody else can then they will fall into obscurity and ultimately lose what they've built, just like other companies before it who didn't.
FAANGS companies aren't at fault for when they're winning a game which is rigged from the start.
No such thing. In capitalism you are either growing or dying. Stagnation means others will grow around you, and relative to them you are shrinking in the same market. Thus, stagnating == dying.
[1] https://medium.com/hps-insight/on-short-termism-8e28fbe4ccc6
Are these business in industries with fierce large competitors? If not, it's an unreasonable comparison - they are only not getting eaten because nobody's trying to eat them.
I love small and medium businesses but just making a game theoretical point - you can only chose to limit your competitive effort to the extent that nobody is increasing theirs.
that's why we have public benefit corporations.
It's not hard to imagine a Google that had taken this path, just focused indefinitely on search & search ads, run itself with <1000 highly skilled, highly paid employees, and never done email, maps, docs, payments, mobile phones, video, or and any of the rest of it.
First Chrome, then Android were critical, life-or-death maneuvers for Google. Without paving their own path straight to users’ eyeballs, Google would have never survived. But succeeding in that path also required an entire ecosystem to back it up.
Google also does a lot of frivolous stuff to explore, but all of the major expansions are required just to protect their Search and Ad products.
Besides, junior developers / interns are supposed to do what exactly if there is no increasing revenue at a company and no one leaves above them? Just hang out until someone quits even though they're not going to?
Retraining a junior developer is costly. Advancing them is as well, but less costly than constantly cycling in new junior developers and interns to do the HTML/CSS + ETL script jobs no one likes doing.
Growth is natural and important towards keeping your staff happy and moving up.
Both Basecamp and Valve were growing massively, so I don't think those are good examples.
Actually I think they're not in enough danger. They take things for granted, our attention and private information for example. Denying Google, Facebook those should put some real fear in them.
https://www.youtube.com/watch?v=Z93yWXb9Tb0
I do not know what you mean by sympathy, I am just opining on the economic reasons for why successful businesses keep trying to expand, and that is if they do not, then they risk falling behind.
A common sentiment on this forum is that companies who fail to keep challenging themselves and get complacent on rent seeking from one product/service will eventually lose to an upstart.
When it was created, gitlab core value was to be the open source alternative to GitHub. Then, it started to add light premium features.
Now, free versions have a lot of frustratingly limited features with nag screens to push you to subscribe. The free core is less and less a priority and less and less sufficient.
After the ipo, things will get even worse. Most of new shareholders (Ie owners) are just profit led. It's an investment for them and they will want the net result to grow at whatever cost.
Management has no choice else than to follow what shareholders require.
So, if it is economically viable, nothing prevent gitlab to stop new versions to be open source if they think that will make them more profitable.
This seems over simplified. A large company is a complex system that is shaped by all kinds of forces. I'm not sure we can attribute Google's scale to a single heinous factor
Only then would people be able to roll out peer to peer solutions that bypass the big tech companies.
My idea is still the wrong PM incentive structure, which is harming the work culture and projects.
Somebody in the online ad space is going to eat that conventional ad revenue, or "build that value", or whatever we want to call it. If it isn't Google it will be Facebook, or Twitter, or Apple, or Tiktok, etc.
What happens to Google if Facebook has a $1tn online ad business in 10 years time, and Google's ad business is still 'only' worth their current $200bn?
This is absolutely about survival. In a super high-growth industry, you grow or you die.
How? With that argument, neither Facebook nor any other ad networks would already be dead since Google basically owns the space already, but they are not, they are also pulling in huge profits, just not as huge as Google, but they are still well off.
In a high growth business there is no stable static strategy. Staying the same is functionally equivalent to shrinking, in terms of scale effects and relevance, as the rest of the market dwarfs you. As long as you keep growing, you can keep relevant.
If facebook had a $1tn ad business and Google still had $200bn, would Google's business actually be the same as it is now? Would they still be able to hire the cream of graduates? Would they find it as easy to replace lost business from natural attrition with new clients? Would they find it as easy to launch new ad products and get attention for them?
This seems to be an interesting concept to keep a somewhat flat hierarchy.
Right, if you look from very far away and put "all large US company" in the same bag.
Otherwise, if you zoom on "Silicon Valley Tech Companies" then Apple and Google's perf process and associated incentives look quite radically different in many aspects.
Why are they still able to continuously pushed out great products and keep innovating? What’s your hypothesis?
Big assumption that Apple is indeed innovating right now. Yeah, M1 was a great innovation, but before that, the iPhone was the previous innovation. Everything between has just been iterations basically, so I disagree with your assumption that Apple is in-fact highly innovative.
Example: You are making a search engine, you use technology X. Would you rather hire a person who worked on Google search but didn't work with technology X, or would you want an expert on technology X?
I wish what you're saying was the truth but I think it's very much the minority.
The alternative is to not borrow from the future. Then your country/tribe is at a severe competitive disadvantage on the global playing field.
In the examples the author cited, those activists and researchers were fired for reasons going beyond “asking Google to be a bit more ethical. And frankly it doesn’t seem ethical for activists, researchers, and the author to deliberately misconstrue facts whenever they believe they’re on the right side of an ethical (and sometimes just political) issue.
I've looked at some of the correspondence between Timnit and others and it's fairly unprofessional on her part if you ask me and it has this self righteousness tone to it too.
Another very funny thing people believe is that Google wanted to do "evil" things but their perfectly crafted plan fell apart at the last second when they realized that they have "do no evil" in their code of conduct. After much scrambling the order came from the top to quickly remove it to unblock the evil plans.
That said, there sure are jerks at Google like any other company but I've realized most these dramatic stories regurgitated by the media is BS
She was publishing studies critical of Google, Google wanted at least the right to have studies of the company reviewed and to include more updated information etc. which is extremely gracious on the part of Google.
She gave the company an ultimatum i.e. 'Change the Terms or I Quit' so they said 'We're not changing the terms, we accept your resignation'.
It's galling how many people (and their supporters) think that they have a right to be employed by a company and then publicly criticize them with misleading information, unmitigated or reviewed by the company.
Of course the CoC is not binding, but having that in there was a statement, which meant, roughly interpreted, "the impact of our work should not be net negative". The removal of the line itself did not change anything, of course, but it was a clear statement that this priority had been dropped. I think it's quite obvious why this is seen as not great.
Second, if you were wearing "I'm a good guy" badge on your shirt and later on decided to go rogue and work for the enemy, would you then remove that badge right away? Of course not unless you're truly incompetent at being bad.
I'd understand it if they got rid of the wording because of how much headache it creates for them.
Btw, that's basically why government and business officials often resort to saying the least informative statements. Because every word and sound bite will be used against them.
Well otherwise it would be considered securities fraud
Objectively, there was nothing wrong with her paper.
You may have a point about the other researchers. I'm not familiar enough with their situations. But I dug into Timnit's pretty thoroughly.
Their recent behavior isn't too encouraging either: https://archive.md/7jCQY
(Related Twitter thread: https://twitter.com/jackclarkSF/status/1451273190974660612)
Hopefully everyone will just chill out and focus on research.
It’s pretty likely the reviewer would have been harassed - a good thing perhaps if you have one view of thing - but a bad thing from another perspective.
Google refused and accepted that she writing be able to continue working there
I think it's worth reflecting on why we're so quick to believe the corporate version of events. Corporations have an astronomical amount of power and influence. Aren't you at least a little curious whether it's true?
And if there was nothing wrong with her paper, that raises the question of why an anonymous reviewer was grilling her about it.
Her paper got got flagged during internal review. There wasn’t time to revise it because she submitted it late. She then wrote an angry rant to her coworkers that claimed she was oppressed and told them to stop working. And then she demanded the name of the anonymous reviewer and threatened to quit if the company did not meet her demand.
Your defense is that most papers were submitted late without a problem. Perhaps most papers don’t need revisions, but this one did, and there’s no excuse for how she handled it.
I’ve had papers rejected from my company’s internal review process. It sucks, but it’s not the end of the world. You make some revisions and submit to the next conference. You don’t go ballistic and tell your coworkers their work is meaningless and threaten to quit unless you get your way.
I reflected on it and found that it mainly happens when the person affect have their entire work life on basis of their politics as opposed other victims of corporate malfeasance who get plenty of support/ empathy from general community.
She's a disgrace to the research community.
The details: https://news.ycombinator.com/item?id=25313994
Discussion about whether the review process was normal: https://news.ycombinator.com/item?id=25308847
Regardless, being upset because you didn’t get your way doesn’t give you carte blanche to do unprofessional things that will get you fired. You can’t say “Give me X or I quit” and not assume there’s a chance your bluff will be called (especially when “X” is a demand for the company to violate its own policies).
A social-justice themed charade is being made out of just being salty at getting fired.
That sounds to me like what strikes do. Sometimes they do go down well, sometimes they don't.
Not once in the paper does she mention that Google has been carbon neutral since 2008, because that would trash half her paper. The paper seemed of desperation to make non existent arguments.
It sounds like you're saying that the calculations weren't mistaken, but that she didn't mention the carbon neutral status of Google as a whole.
"We first consider environmental risks. Echoing a line of recent work outlining the environmental and financial costs of deep learn- ing systems [129], we encourage the research community to priori- tize these impacts. One way this can be done is by reporting costs and evaluating works based on the amount of resources they con- sume [57]. As we outline in §3, increasing the environmental and financial costs of these models doubly punishes marginalized com- munities that are least likely to benefit from the progress achieved by large LMs and most likely to be harmed by negative environ- mental consequences of its resource consumption. At the scale we are discussing (outlined in §2), the first consideration should be the environmental cost."
This whole paragraph is such a reach, and so absurd that it seems like a parody. Are we supposed to believe that marginalized communities are being harmed by Google training NLP models using green energy? Or will they benefit from better translation from English language content into marginalized languages?
Timnit has zero interest in what actually benefits marginalized communities. She uses them as a prop to build a career in high paying AI field where, apparently, the sub field of ai fairness has a low bar for publication.
Electricity from the grid can come from green sources, and in the particular case if Google, it actually does. Comparing electricity consumption for a one time training with jet fuel usage is absurd.
Moreover, the paper doesn't mention any possible benefit of building such nlp models. Increased accessibility of web content across languages and for disabled people.
Google, simply through its search, maps and navigation saves a lot of wasted carbon. Complaining about the power consumption of ML models is absolutely ridiculous.
Her paper reeked of desperation to find something, anything within the AI space that could be posted as an ethical dilemma.
Reading that paper convinced me that Timnit could bring absolutely no value to AI as a field, in terms of ethics or otherwise.
Google buying green electricity makes green electricity cheaper, not more expensive. More producers are incentivized to produce green electricity as Google's demand increases continuously. Other companies like Microsoft and Facebook go green as well, and the economies of scale kick in. Prices start collapsing. This is actually happening right now.
If I go solar today with my home, it is not a negative action that displaces someone else. It actually expands the solar industry and enables cheaper solar in the future.
Without early customers, green energy would never have taken off.
https://www.dezeen.com/2021/07/30/carbon-neutrality-google-s...
The point is that electricity can have a green source, liquid carbon fuel can't. You absolutely cannot compare the two. FWIW, Google's data centers are primarily powered by green energy.
Google handled Dr Gebru’s exit differently than that of Anthony Levandowski, Andy Rubin, David Drummond, etc etc because Jeff Dean made the call in timing and he was really that clueless about public optics, especially with Tensorflow’s huge following. Moreover, Dr Gebru didn’t have the bankroll to fund a legal team like any of the others listed.
A lot of the posts here suggest Google is struggling with scale. Dr Gebru’s case definitely would have been handled differently were Google a smaller company. Also if there wasn’t COVID—- keep in mind she was fired a couple days before Thanksgiving during COVID. The whole country was a mess then.
That is just very dishonest. She gave an ultimatum. Execs accepted the ultimatum. You are gaslighting other people on this topic. At the very least, you should've acknowledged that this is up to an interpretation.
Regardless whether she was fired or quit, she was toxic as hell. She dragged Jeff Dean into an unrelated matter in public and implied Jeff Dean supported personal attack.
https://twitter.com/timnitGebru/status/1278569638532530177 -- this happened a few months before she left or was fired from google
If a direct report did this to me, I would've wanted them to leave. In this case, Gebru wanted to leave (according to her ultimatum). Jeff Dean wanted her to leave (I don't doubt this. nobody wanted to work with a colleage who attacked them on twitter). I see a happy ending for both.
Gebru and her supporters have been dishonest about the whole thing.
The reason Dr Gebru’s case is so divisive in tech (especially in this thread) is because so many are agnostic or ignorant of the role of ethics in tech; and almost every employee is ignorant of how Legal/HR execute retaliation. Anthony Levandowski is a literal criminal and yet is still enjoying tens of millions of dollars of Google’s money. Same with Andy Rubin. Even Michael Church is rich. If one percent of the energy spent fighting Dr Gebru was put into fighting the real scumbags in tech… you’d have something more like Google before it got greedy with scale.
Please note that this was months before she left.
The 3 names you mentioned have nothing to do with Jeff Dean.
Handling those 3 people has nothing to do with supporting Gebru or Jeff Dean.
This has nothing to do with Gebru being a toxic person.
Before or after she demanded that the company release the name of an anonymous reviewer?
Before or after she told them to schedule her last day if they didn’t meet her demands?
Indeed, this line is the takeaway, in my opinion: “…is because we've been at least a little brainwashed into thinking a job at Google is the pinnacle of employment.”
I haven’t worked for one so this take might be quite hot, but I get the sense that big tech companies do a great job selling you on the idea that they’re elite and therefore you must be elite too if you get the job. But then you’re really just another fungible developer in a pool of tens of thousands. There’s exceptions of course.
In 2005, it was a wonderful, prestigious place to work with many great people and a startup vibe, the place was vibrant. By 2013, Larry and Sergey were put out to pasture, and the company took on a much more bureaucratic, compartmentalized feel.
I was working hard, most of my work was fighting bureaucracy and optimizing what I did for the horrific perf process, and going through constant re-orgs so that I had no consistent manager, and no chance of promotion (this is a big deal at Google). Joining in 2005 was the best thing I've done for my career, and leaving in 2013 was again the best thing I've done for my career. I value the time there, but the Google that I remember no longer exists.
Just as people are different at age 10, 20 and 40, companies are different in different stages and sizes. Know what you want and look for it.
I realized I want to be at small companies, and have not worked at a company larger than 25 people since.
I'm sure it varies widely. I just feel like a tiny company leaves too much room for unhealthy and unprofessional dynamics, even though I'm sure it can be perfectly fine in other cases. Just depends on the people.
What makes it more special was the stellar team that I got to be a part of with whom I’m still in touch with. It’s like being part of a secret club.
The only thing we used to discuss among colleagues most of the time was solving some hairy interesting engineering problem. That changed as years wore on, it became more gossip and internal politics and who got promoted how and when etc.
However its outcome in practice can't be any worse. To this day, people "cook up" a project that doesn't need to exist and won't share the credit or their territory with anyone (or else the committee will doubt their ownership) and abandon the project less than six months after their promotion and switch to a new team.
A: Get a job at Facebook at E4, get promoted to E5, and get hired back at Google L5.
Do you have to be elite to work there? In some roles you absolutely do. In other roles you just need to do the work. You're often working alongside people who care a great deal(and some unknowingly toxic people whose self-worth seems to come solely from their career achievements), and that can raise the bar for what you and/or the company expect from yourself.
The "toxic" thing in my experience often just comes from rapid, unmanaged growth. The company is literally morphing into something new with every passing day. People are being sucked up the management chain without merit. Systems aren't yet in place to deal with the changes. New employees are flooding in faster than they can assimilate the old culture.
I'm not saying I love the valley or anything, but I'm glad I got to spend a couple years of my life here and contribute 0.0001% to some of the greatest discoveries in the last few decades. I hope more engineers get a chance to have that feeling.
Also true of Ivy League Schools, movie studios, and certain neighborhoods. Prestige is weird, and if you value it, that's totally fine, but it's probably better the separate the myth from the real-world entity that's made up of people doing stuff.
They're the new Oracles, except they own mobile, social, and web instead of databases.
Start new companies and push them over. Fight their ability to land grab more.
That all being said, the quality of humans there is pretty amazing. I count almost all of my old managers as friends and I felt privileged constantly to be surrounded by such intelligent people and to work on such huge ranging vastly impactful projects as I did. But I'm happy I left. The self-direction feels too good after being in such a behemoth to start my career.
On to new adventures!
There are employees that will create pressure out of nothing and will ruin the cushy possibilities just out of their own boredom and misery due to not being able to progress the hierarchy of the monopoly (most old monopolies don't really give big raises and it's very hard to reward employees because most don't really have any impact). (managers that start micromanaging employees that somehow do something productive, regular workers that overdo it at the task managing platforms and then stress over the backlog, etc.) But it's not the monopoly that's taking the cushy from them.
It's interesting that the author mentions this, but doesn't make a connection between feeling burned out and feeling that they have to be personally responsible for everything the company does.
I don't even disagree with many of the demands of internal "activist", but the strategies they use (walkouts, trying to keep everyone outraged as much as possible) seem ineffectual to me: The main effect seems to be that it makes ordinary employees feel more burned out since they're made aware of many things that they're suppose to be angry about but at the same time they're powerless to change them. That's a recipe for burnout.
I get that the thinking is that ordinary employees are not powerless due to collective action, but for that to work you have to be a lot better at picking your battles. You can affect one to two larger things per year, so getting up in arms over every (comparatively) little thing just has the effect that your activism achieves nothing but burn out the people who want to have on your side.
It would be rude to describe my anatomical response to having 25 reports, but suffice to say it wasn’t good. I generally consider 6-7 the ideal max, and 8-9 the “I’m dropping all the unimportant balls in order to keep juggling” line. 25 is so far beyond the pale I can’t imagine how any manager of managers’s worth their salary would let it get that bad. 10 reports is “you put this off a bit too long” territory, 25 is in the “someone up the chain should be fired” territory.
While working in consulting I spent about 4 months with a manager who had 60 direct employees. That was a disaster, but I got to spend 3 /4 months with no responsibilities :)
The rule of thumb at Google is 10 directs in an engineering management role, less if you’re a TLM (an IC with some management responsibilities) since you’re still evaluated on the IC ladder. There are exceptions, but they usually involve “managing” a number of contractors where you have significant program management support for coordinating their day to day activities.
A micromanager will be absolutely crushed by a high number of reports. In fact 10+ years at Google, managers intentionally had a large number of directs so they couldn't micromanage.
If you have a pretty autonomous team, strong tech leads, can delegate, ~20 still isn't great, but it's not horrible. It's not the steady state you want, but it's doable for a few quarters.
I think the real solution here is to find the micromanagers and train them or fire them, rather than hampering all the managers in order to cut the micromanagers off at the metaphorical pass.
Personally I’d quit in such a situation. If I’m going to be managing 20 people and creating informal team structures under me, then some of my directs deserve a management title and I would want a title befitting a manager of managers. The whole thing has a whiff of “how can we avoid promoting a bunch of people” to me.
My manager has about 25 reports and he thinks it's ok, because we're all organized in smaller teams that manage daily work themselves. That's true, but the effect is that the person who should care about people aspects has no idea about you (how you're doing, how you want to evolve, whether you're performing, what you need to improve, whether you deserve a raise or a promotion, whether you're burnt out, whether you're looking for a new position...).
And nobody tells him, because he's the manager and you don't go to your manager with problems, especially if he doesn't maintain a close relationship with you.
For instance, has she had to reduce the frequency, duration, and/or quality of her 1:1s? I’m guessing the answer is “of course” and maybe some ameliorating fact like having more 1:1 time with the team lead. The “so what?” here is that 1:1s are how you head off problems before they get serious. So either the tech lead is picking up that slack and is your de facto manager or you’re simply coasting on the strength of past 1:1s, but inertia will only get you so far.
Also, this tech lead you mention is likely doing less actual technical work because they are picking up slack left by your manager not having enough time in the day. This might not be a problem right now, but the first question I would be asking in your manager’s shoes is: “is my TL happy? Is this sustainable for them?” The second would be something like “What long term technical objectives are being sacrificed to deal with this management issue?”
It’s often the case in the situation you’re describing that the TL is interested in moving into management, and this is a “try out” effectively. Personally I like to be open about situations like this, although there are valid arguments against that. In any event, I think most people would agree that it’s best do such “try outs” when the stakes are relatively low, and the TL can have an easy escape if they need it. The situation you’re describing doesn’t fit my definition of low risk, although ymmv — maybe conditions are such that this is a very temporary state and the machinery to fix it is already in motion.
The best way I’ve seen to accomplish this is have a job title that’s purposefully ambiguous. Usually I’ve seen this as a “lead engineer”, which can come with or without direct reports. This lets people try out management while giving them space to change their mind without losing title or status.
I’m good friends with one of the high school teachers at “an elite private school in the Bay” (HRS) and it’s fun comparing and contrasting our jobs, but they are not at all the same job.
They're saving a bunch of money just having one useless person.
I think it was 2008 or so when I was sitting at a table with about eight other people, and somehow or other the question came up "who has a 20% project?" Only one of us did.
The main utility of a 20% was that you could try out a new group before transferring to it, and they could try you out. Other than that, very few people actually had one, even then.
* we have a lot of work to do, the poster in this thread who is bored and only has 5 hours of real work a week is definitely not in my BU
* they may be concerned how such a project will reflect on them in perf. it may seem better to go all in on one thing vs splitting your attention
* we’re relatively new (acquisition) so perhaps the 20% ethos hasn’t percolated over to us yet
But at any rate, I think I’ve gotten exactly 2 requests for 20% projects, which I approved after confirming the person wasn’t going to be doing the dreaded 120% project.
This is interesting given Google used to have a reputation for being an "engineer led" organization, I guess that's slowly changing over time.
One of the very first requirements for a man who is fit
to handle pig iron as a regular occupation is that he
shall be so stupid and so phlegmatic that he more
nearly resembles in his mental make-up the ox than
any other type. The man who is mentally alert and
intelligent is for this very reason entirely unsuited to
what would, for him, be the grinding monotony of work
of this character.
It is sad to see this happen at places like Google, where engineers had a lot more autonomy.Most knowledge workers who have the mental capacity to grasp deep technical topics will find the "cross functional relationships and strategies" discussed in garden variety business books a light stroll in the park.
Actually understanding science and manipulating the world is hard. Try to explain to a non techie how a car moves, or how a web request happens. They can never understand it on the required level to fix things.
Now try to explain to an engineer how a bond works, or how industrial strategy works. He can do both his own work and the manager's work.
I sound pretty bitter for a guy who's managed to dodge most of the BS things in large corporations his while career, but that's because I really think this aspect of the world needs fixing.
It seems like just about every human endeavour is encumbered by MBA people who pretend to understand something hard, who get paid at least as well as those people who can both solve the technical and the strategic problems.
This might be more of a problem in the Anglo world. Engineers getting promoted is more common in Europe according to rumor.
I always love a classic hacker news take where software engineers are the only people who can understand how things work. It's not like high school dropouts are ever car mechanics.
The issue I have with bad PMs is the same issue with bad engineers. They can cause so much damage to a product or codebase, especially when they have free reign and an ear from higher management.
I'm pretty sure that being a car mechanic is one of those trades jobs that people are discouraged from pursuing if they're seen as having alternatives.
Also a lot of what comes up on a search for "redneck engineering" is I think not consistent with this assertion.
> We were expected to hit precise deadlines on multi-quarter projects (within two weeks), and when that inevitably didn't happen, we had to track all the time we spent on anything in 30 minute increments. It felt very cog-in-the-machine.
It's inertia-led.
I bet most googlers hate ads so it's a big state of cognitive dissonance too.
They lack real-world experience and ability to grasp non-technical concepts.
As a founder, and having worked in multiple startups is hard for me to communicate with their relative worldview. Despite how brilliant they are.
For checkboxes one needs to be constantly in touch with customers, sales, pre-sales, need to be full time demo giver, etc. These are not the job of engineers and even if it is made so, it is setting them and the team/org/company up for failure on both fronts - frontend and backend.
In enterprise applications (which solves for workflows - business, IT etc.) one needs lot of PM thinking for feature identifications, what to prioritize, gathering requirements etc.
In Search defined Google one did not need PMs as requirement is pretty straight forward from feature perspective, but one needs deep engineering and computing science knowledge for making the best search algorithm. Whereas in Cloud IT world the focus shifts more towards product & roadmap planning.
I wonder if there's any "big, established" company where IC engineers have more weight than the PHB types. I'd be genuinely curious if anyone knows of some good examples, I suppose HN would be the place where people might.
It seems like that's one of the natural equilibrating factors that offer some small amount of competitive grace to Davids competing against Goliaths. Google hasn't been David for a long time now, I think.
This isn't a future engineers want either -- I hear complaints about meetings from nearly every engineer I know. The idea that you should have low level knowledge of the system you're working on and high level knowledge of all the cross functional team's responsibilities along with the responsibility for cultivating those relationships is ridiculous.
People say this without having any idea what PMs do.
Do you think the engineer who leads a 1000 man org is not talking to people? I talked to the engineer leading our 500 man org, he talked to a lot of people and wanted their input and tried to understand the whole to make decisions. He had technical expertise so he could talk to low level engineers as well, but also to business people etc.
The idea that (good) engineers are somehow not able to understand cross-functional relationships, business strategies, or don’t know what PMs do, is absurd. You’re digging your own grave there.
Compensation in tech is so insane.
Other high earning occupation just doesn't even come close.
It would take doctors years to earn 250k a year. In tech with stock growth + RSU, you might get that as a junior eng. I earned 450k as a junior per year with pre-ipo company.
This is why engineers can just leave and others are surprised.
Most things promoted in Google about growth boils down to promotion, which is just a cover word of getting your hands on promising project without proactively doing much by yourself.
Self motivated ideas actually get me into various trouble. In hindsight, I can see that many coworkers are silently watching this guy getting burnt without offering much helping hands.
In the end, I learned the googely way of working at Google, and find it not worthwhile to stay...
It turns out that you can't apply to Google's JAX team. You have to apply to Google, and then managers at various teams select whether they want you.
The thing is, JAX is amazing. So I'm now faced with the uncomfortable idea that this process must make sense, because it clearly works. Yet I profoundly dislike it.
Perhaps my ideas are the problem, and Google is four steps ahead. I don't know. It just seemed like you should be able to apply to specific teams at Google, and that the team should be able to choose whether you'd be a valuable teammate.
This is what I do. Every single person on my team applied directly to my team.
- you’re established, no longer a startup, you prioritize the momentum in the current cash cow.
- your hiring pool changes. Instead of people who want to come build the “next big thing” you tend to attract folks who value the security of a big name. And they will tend to hire folks like them, and so on..
- you’re publicly traded. Holding an asset that reliably produces steady growth, creates very different incentives than trying to hit some kind of hockey stick unicorn growth
A small improvement for billions adds up. Though burnout and pain are real, there’s more to all this. Hope OP finds what he’s looking for!
There is some strange fixation Google currently has, especially towards getting people into their New York offices - must be some tax incentives or other deals with the city....
A friend just recently wanted to work from google office in another tech hub city (not remote/from home by any means) and during offer negotiation it was denied, so she didn't join - as she didn't wanna move to NYC.
Odd things happening at Google lately - I mean even Amazon is more remote friendly these days. Lol
For example, NYC Metro would have cheaper housing 60min from work than San Diego. I generally find land in coastal CA to be more expensive than everywhere else in the US.
Note that Google was a huge, profitable, publicly traded company before this happened - it was possible to be an institution and be publicly traded, but for how long? Can we build long term focused companies that are subject to the whims of the stock markets? I'm not sure. Truthfully, I think it's a social problem.
I make 75% of what a Google would make for the (high) position they would hire me for, but I work 1/5 of what I would work at Google and with little overhead such as performance review, promotion packages, and excuse my French, other assorted bs I have zero interest for at my age and with my experience.
If the hiring process were more reasonable, i.e., not dependent on the mood, accent, question of the day of interviewers whom I will (probably) never meet again after they nonchalantly determine my future employment, I might agree to interview again and then evaluate their proposal, but otherwise I think Google will continue to bleed talent and hire little uninteresting robots (mine is a salty-fish generalization of course) who have the patience for nonsense that I, and people like me, do not have.
I am not a hardcore tech guy, in the sense that I could switch tomorrow to selling bicycles (for the same money, of course), and not miss tech one bit, so my north stars are money conditional on time spent working and stress (assuming the job itself if not terrible).
I would guess that my current position, given zero stress, little time at work, and good salary, is on par with the Google position I was interviewing for.
But I am not willing to go through those ridiculous interviews again, then waiting for weeks for a the committee decision, then the recruiter cannot say what happened, are you kidding me.
What does this mean?
I also want to say that it's completely acceptable to work on a place without exorbitant pay, stocks, or promotions every 6 months. A job can be many other things. Different people want different things at different phases of their life. For some of them, a job is just a job.
The above seems to explain how a thing that fills a gaping functionality hole in one google product via another just gets deleted without any consideration for the interaction between the two.
If you have this luxury, use your precious time to work less.
He didn't like working enough to make himself happy, I guess. It's a person who is at a different point in their life than when they started. Notably with enough money that they question their own motivations to continue.
These blog posts seem devoid of anything interesting or actionable.
i'm curious. What exactly they don't use internally?
The first time I went to work on a personal project using Go after I joined Google, tried using Bazel because I was so used to Blaze and I liked it a lot. I was very disappointed to find that the integration between Bazel and Go was severely lacking and required me to use third party extensions to get things working as expected, which was quite disappointing. That was a few years ago so things might better now
Obsession with promotions instead of product quality won't lead anywhere nice.
Maybe changing teams or company can get you working again. 1 year seems too long to me
Work isn't worth doing just for work's sake. You have to feel aligned.
> I still feel uncertain about everything though. Google approved my remote work application last week, but I haven't gotten a new offer letter yet, and I've been told to expect a pay cut of at least 10% because the market rate for software engineers is supposedly lower in southern California. This feels like a shitty thing to do. My work is not less valuable. It's a reminder that this is nothing more than a business relationship, and the company is not interested in loyalty to workers or support in a difficult time. I'm not sure what, if anything, I'm going to do yet, but it has me thinking harder about my career and future.
Not sure why _this_ is what it took to get to that revelation, but better late than never. But on the point about value vs. cost of living... I mean how do you work as a developer in the United States and not notice you get paid a lot more to do this work than people in other places?
To me earning nowhere at level as these folks, still it embarasses me to whine about pay/promotion when so many hard working folks doing important work in society are paid pittance.
First, for those that don't know, new grads get hired at L3, PhDs at L4 (which IMHO is actually a mistake but that's another issue) and there is an expectation of getting promoted to L5 (Senior Software Engineer). There's no set time frame for this. I've known people who stayed L4 for many years and were quite happy. L6+ start to require increasingly extraordinary influence and technical contribution.
> It's hard to get promoted beyond L5 for open source work
I'll clue you in on a dirty little secret: it's hard to get promoted to L6 for anything. This is by design. It's how the company controls costs and maintain retention (by dangling that L6 promotion, possibly for years).
One of the things that Ruth Porat did when she became CFO is lowered the promotion target percentage. This meant less people got promoted at each cycle.
How promotions work is a committee of higher-level engineers (eg L7s consider promotions to L6) and will have 10-15 packets to assess. These will get stack ranked by the committee. If you're above the line you'll get promoted. If you're not, you won't. Ruth's change just made that line a little higher.
As for the pay cut, this requires some context. By the time you reach L5+ the majority of your total compensation comes from equity, both your initial grant (for the first 4 years) and annual refreshes and discretionary grants you get along the way. So less than 50% of your income comes from salary plus bonus.
For those employees who go permanent remote, there is a location-based pay adjustment. SF and NYC are at 100% rate. Other areas at 85-95% of that.
That only applies to the salary plus bonus (since bonus is derived from salary) part of your total compensation. So a 10% cut for L5+ is in reality <5%. You don't save on taxes by moving to San Diego but it is cheaper than the Bay Area. If you move to a no-state income tax state however your net pay can in fact be higher.
So, the argument for no pay cut is you're saving the company money by not having to pay for office space, a desk (etc), free food and so on, all while doing the same job. This seems to be the author's position and I'm certainly sympathetic.
The argument for a pay cut is that your compensation isn't really associated with your output at all and is entirely market-based. For many people not going into the office and being able to live somewhere that isn't the Bay Area is a huge plus so people are willing to give up something for that. Plus you could argue the company doesn't want people going remote who don't really want to by offering the same pay. By lowering your pay slightly it creates a psychological barrier such that only people who really want to do it do so. I'm sympathetic to that argument too.
If it weren't for the fact that Google makes level information public within the company, I doubt there would be quite so much emphasis on getting a promotion. Most people want to get L6 for the recognition and the fact that it elevates you above other engineers in terms of status and influence. When I worked at Apple, levels were private, so you had to treat everyone the same -- a person's influence was not dictated by what level they had on their company profile (there is no company profile at Apple). In my opinion this approach was much better, and significantly lessened the internal competition for promotions.
It's hard if you're on the wrong project (read: low impact and/or low visibility). There are different routes to L6 at Google, but by far the most successful was to become TLM or just M of a medium impact project. It's hard to make the case as an IC for L6, but colleagues did it multiple times. Large enough, long-running projects also reach a critical mass of L6+ people and then getting high-level support becomes much easier.
Having been through the process, seeing the process from an IC, TL, TLM, and promotion committee member, if you think that L6 is unachievable, there is either a problem with your project or your expectations.
Lots of managers are also not good at talent management (and not just at Google). Which is sad. So they tell people it's a promo committee's fault, or .. Realistically, it's also the manager's fault. If they don't have scope/work that can help someone grow to L6, the right move is to help the person find a place that does, rather than string them along. Stringing them along ends up with them leaving or unhappy or ... Helping them grow elsewhere ends up with people who will likely want to come back to your org at some point when you have the need/scope/role for them.
Another argument is that if tech paid everyone the same, everywhere, it would greatly exacerbate income equality issues in a lot of places.
Tech is certainly not altruistic, as you point out, and generally wants to pay market rate rather than output rate or whatever. But it doesn't make less true that it would worsen a whole bunch of social problems by paying people the same everywhere.
Some businesses do earn more due to ease of access to additional capital, and hence can pay employees more, but the root of the income/wealth divide is certainly not employers paying employees more. It is certain employers (capital owners) getting disproportionately more in the first place.
Tech employees are simply in sufficiently high demand relative to supply that they can demand a piece of the pie. But there is no point in trying to address a problem by addressing its symptoms rather than causes.
Specifically, in this case, paying Alphabet employees less in the name of helping the income/wealth divide only helps other owners of Alphabet stock be even richer.
Uh, what? No, it's about where the money is concentrated and how that concentration changes (or doesn't) over time. It's true that other forms of earning have a bad effect on this, but i'n not sure why that's particularly relevant.
To whit - tech folks, paid in SF dollars, but living in various cheap ares of the US, are in the 0.1-1%. Easily.
The fact that they got there by being paid rather than some other form of wealth accumulation, is irrelevant. They will stay there just the same as anyone else.
Why would it be any less unequal because someone is starting in the 1% by getting paid a ridiculous salary on a regular basis rather than earning money through the stock market on a regular basis? Why would one not transform into the other? It's rhetorical of course, since that is what will happen. In fact, it's what the tech folks moving want to happen. They want more money to buy a large house and invest and retire and be richer than they can be in SF.
" But there is no point in trying to address a problem by addressing its symptoms rather than causes."
You haven't, at all, explained why putting more people in a seriously unequal position makes anything better, or why it's "pointless" to avoid doing that.
It's not pointless. It avoids more inequality. Does it avoid all of it? Of course not. But again, the other way demonstrably makes things worse.
Do you have a concrete argument as to why it makes sense to keep doing that?
Because your entire comment feels precisely like the rest of the discussions around this - "it's not my fault, i shouldn't earn less money, it's the other people who are at fault. Particularly the ones who have 10x/100x what i do".
> How promotions work is a committee of higher-level engineers (eg L7s consider promotions to L6) and will have 10-15 packets to assess. These will get stack ranked by the committee. If you're above the line you'll get promoted. If you're not, you won't. Ruth's change just made that line a little higher.
FWIW this is no longer true for a lot of orgs, and will likely soon be untrue for all orgs. Also fairly sure that stack ranking within a single promo committee was never how it worked.
> That only applies to the salary plus bonus (since bonus is derived from salary)
Currently, however management is on record stating that this will change in the future, since I don't know exactly how, I'm not going to speculate, but the intent is for equity to reflect the compensation regions in the US eventually.
Managers don't get promoted for growing teams. I've watched lots and lots of people who write "grew team from x to y" get feedback on their promo packet that this isn't, by itself, a valuable thing.
Other than back pain these symptoms match mine exactly, except I hadn't worked full time for the past 2 years and I wouldn't say I'm stressed or anything. I'm not sure what it is - maybe cabin fever? Yesterday I nearly lost consciousness when I got up too quickly. I'm also losing weight (12kg so far, which would be great if I knew _why_ I'm losing weight). Did a blood test about a month ago - everything is fine. I did wonder if these are vaccine side effects, but that seems very implausible - the second dose was in May. But I digress.
I totally get what Jay is saying in his writeup. I largely felt the same way except in the opposite direction in one aspect - the number and shrillness of "activists" has become overbearing to the point where it was severely impeding work and morale. Seeing that he has pronouns in his twitter bio he might have been more sympathetic, but I bet this stuff distracted even him.
Contrary to belief popular on the outside, Google is indeed a fairly stressful and thankless place unless you're skilled at self promotion, which I'm not, or you don't care about working on cool things and getting promoted. This is why every time their recruiters ping me I tell them I'm not interested "at this time". No matter how much they pay me, I can't imagine subjecting myself to such treatment again. And I was pretty successful there - high profile projects, wrote lots of code, shipped impressive stuff, and I still felt like shit most of the time. I can only imagine what less "forceful" folks feel if I felt like a gnat on this elephant's ass.
Contrary to belief popular inside Google, life is great on the outside. Freedom is a thing folks, and without moving around you aren't experiencing it. I know when you're on the inside it feels like you're "changing the world", but of all Google products nowadays I only use Gmail and YouTube. If everything else disappeared completely I wouldn't even notice. Heck, if Gmail disappeared I'd switch to Proton Mail in a day, and if YouTube disappeared there's BitChute and Rumble which are modest, but adequate. So whatever you're "changing" there impacts me very little, and mostly in negative ways.
I certainly do not regret leaving. If anything I should have left much sooner than I did.
Brain fog and headache are also one of the most common symptoms of long covid. Losing consciousness when getting up sounds like POTS[1] and is also common in long covid. Research is showing that people who are asymptomatic during infection can also develop long covid[2].
In general things like brain fog and headache are also symptoms of burnout and probably lots of other things, so I think it would be pretty difficult to clearly distinguish between them. There also isn't a test for it and it won't show up in standard blood tests. And of course it's also possible to have both. Some form of long covid, even if it is just "light" compared to other people who have long covid, could easily push someone who is already on the brink of burnout over the edge.
[1] https://en.wikipedia.org/wiki/Postural_orthostatic_tachycard... [2] https://www.pharmacytimes.com/view/study-many-long-haul-covi...
1) So did you. E.g. the commenter who was at Google for 9 years. Do you not think you changed? You changed. It reminds me of right wing commentators who say "everything was so great in the 50s!". Sure it was, because you were a child!
2) Selection bias. You left. Of course if you take the people leaving, they'll be less happy with Google than the people who stay.
Oh, and the "Of course, when you leave Google you have to write some kind of letter or rant". Ugh. So childish. No, you do not need an exit rant. And joke or not, this was an exit rant.
> A 10% cut is pretty damn unfavorable, considering I was doing the same work on the same team
So were all your colleagues working in offices outside the bay area. That was literally your "bay area bonus". You're being super spoiled and disrespectful.