12 ms·
9 years @ Google, and I too came from a company acquired by Google. (In my case, Google did not keep our product or tech stack around, so.) And yes, I can say m
by cmrdporcupine 6y ago
9 years @ Google, and I too came from a company acquired by Google. (In my case, Google did not keep our product or tech stack around, so.) And yes, I can say many Googlers are entitled. It's a fair descriptor. And the pace of work is slower than a startup. In general.
And I too have many criticisms of Google. But.
Google has entirely different revenue constraints. It can afford an entirely different way of working. That pace allows a more sustainable cadence of development. It can be a more humane place to work, in general.
Google can on the whole accomplish its revenue goals without being a meat grinder. So why be one? I think there is a bit of a problem with this guy's POV where he's come to fetishize the actual process of the making of the sausage versus the sausage itself.
Projects need not be run under insane stress if there's a steady supply of talent and money to make things happen. Google can afford that. Pace will be slower. Perhaps less competitive. But the core business continues to do excellently.
For many of us Google is not an "exciting" place to work. But it's a pretty good job to have and it pays well and gives access to both great benefits and to interesting technology. And that compensation in _most_ people does yield a sense of responsibility for delivery. But maybe not the survival-of-the-fittest-meat-grinder panic that this guy somehow seems to love.
- 627467 6y agoIsn't there a place for this kind of fetish? It doesn't need to be in today's Google (but maybe in 5 year old Google). > Google can on the whole accomplish its revenue goals without being a meat grinder. So why be one? I too hope Google can prove that this state can be maintained after certain quasi-monopolies it holds start to vanish...
- titanomachy 6y agoI agree that there's a place (probably not Google) for this attitude, and my impression is that this is the realization that the author eventually arrived at: he wouldn't change Google, or change his nature, so he had to leave. Even though his frustration was clear, the message that came through for me was not simply "Google is bad" but more "Google and I are too different to work together". A lot of what he dislikes about Google is true of any large company. Although, he was very critical of Googlers' entitlement in particular. This is a real issue, especially among those who have never worked elsewhere, but IME people are more self-aware about it than he implies.
- Aeolun 6y ago> A lot of what he dislikes about Google is true of any large company. Lol, yeah. A lot of what he said made me nod along :)
- JMTQp8lwXL 6y agoA lack of any real time pressure may lead to unusual or unjustifiable architecture decisions, or needless complexity. It's true that not every place needs to be a meat grinder, but you should timebox your projects.
- hanniabu 6y agoThere's a difference between time pressure and burning out your employees. I believe the present is referring to the latter.
- fossuser 6y agoMy take would be Google can afford it for now because they have a web ad monopoly and don’t have to compete. If they ever lose that, the culture they’ve built will cause them to be destroyed and irrelevant in not that much time. For now, it’s summer.
- lhorie 6y agoI recall watching a news report as a teen about how things used to be pretty chill at Microsoft at its heyday. These days it doesn't seem to have a monopoly on much of anything, but it can still crank out interesting projects. It doesn't have to be a black-and-white do-or-die.
- fossuser 6y agoMicrosoft became almost irrelevant under Ballmer or was at least trending that way. Nadella’s turn around is almost miraculous and is itself probably an interesting story. I wouldn’t bet on that as the norm. I’d expect the norm to be more like IBM, RIM, or Nokia. I agree with most of the article, but one line stuck out to me as particularly wrong: >”After the acquisition, we have an extremely long project that consumed many of our best engineers to align our data retention policies and tools to Google. I am not saying this is not important BUT this had zero value to our users.” Good retention policy does provide value to users. -- > "When COVID hit and we moved to work from home - a huge amount of complaints began around why cant employees expense food since they are not in the office. While most "real" people were worried about keeping their jobs or finding one, many employees were complaining about expensing their food on top of their salaries/stocks/bonuses." +1 on this - I find this behavior really irritating, it makes me roll my eyes to see some of the most coddled employees in human history whining about this kind of thing. The most charitable interpretation is its just a normal way for people to bond over some shared thing by complaining about it, but a lot of the complaining feels like more than that. > "We had lunch in the cafeteria and a Googler online ahead of us was overheard saying “What? Sushi again???” which became our inside joke around entitlement."
- ghaff 6y ago
- deleted 6y ago[deleted]
- dmayle 6y ago*This I came here to say something similar. I'm a founder, I've been a manager and a software engineer, I did 5 years @ Google. When I hear someone in "upper management / founder / in a position of power over employee's lives" say that what they really needed for their own success was a way to threaten/risk the livelihood of their employees so that they would work harder, it just makes me sad for anyone affected by them. Yes, sometimes employees need to be fired... but sometimes management also needs restructuring. The truth of the matter is that at a company the size of Google, it gets harder and harder for an individual employee to directly influence success. I think that's mostly because of the policies in place to make sure that employees don't directly *damage* success either. This means that you have to work within the system you have. An employment contract is two-sided, you're offering something that the employee wants, and they're offering something that you want. If your first reaction when there's a problem is to cut their pay or fire them, then you're the one with the problem, not them. Yes, there are times you need to fire someone (and I have), but that should be reserved for one of two cases: 1) they are actively damaging the business (e.g. destroying company property, morale, hurting business prospects), or 2) despite your best efforts, they are unable/unwilling to fulfill their side of the contract. Just realize that firing someone has a cost for your company and team as well as for the employee. I'd rather part ways amicably, finding them something that works for them if possible, and I think what Noam said about managers recommending great employees is unfair both to the managers and the employees. I've had employees who were hard-working and passionate, just not passionate about the project they were working on. When that happens, the best thing you can do for both of you is to find them the fit that works. Can you build a large company that doesn't get mired down in things like management and governance and legal and policy? I hope to someday get large enough to find out, because I've got some ideas... (Like separating those functions out in the same way there are engineering teams dedicated to software tooling.) But it requires a will and effort from the top down, and the people who get excited about building billion dollar businesses don't seem to get excited about maintaining them once they get that size.
- apohn 6y agoI wish I could give you more than one upvote for this. I work for a huge company. For every person I've worked with who I thought needed to go, there at at least 10 (probably more) who have become ineffective because of management,politics, and bureaucracy. I had a very different view of "who should be fired" when I joined this company, but I think I've grown up a bit.
- chubot 6y agoThe problem is that it can hurt your career, especially if you've never worked anywhere else. (random guess: somewhere between 15% and 30% of the workforce falls in that category) You can learn the wrong lessons: you learn how to go up for promotion rather than build things that work for users. In the last 10 years it's become extremely common at Google do work that is simply thrown away (because of issues above your pay grade). You could work at Google for 5 years and nothing you worked on ever sees the light of day. That is a problem. You don't learn what works when your work gets thrown away. You can still get promoted anyway. So why do the work? Just pretend you did it. (It's usually not as black-and-white as that; employees are usually well intentioned but then are surprised when the work that was hyped up by management gets suddenly thrown away.) I'd say that if you want to have a good career as an engineer, you should focus exclusively on building things from 22 to 26 (or whatever your first 4 years are). If you miss a year or 2 of that because of corporate politics, then you missed a lot of learning, and you may be unqualified for future jobs. There is legitimately a lot to learn about writing software on the job -- IMO it's more than the equivalent of another 4 year CS degree. ---- This is probably the best description of it that I've read (after working there myself for over a decade and seeing the change in values): https://mtlynch.io/why-i-quit-google/ https://mtlynch.io/why-i-quit-google/ https://news.ycombinator.com/item?id=16483241 https://news.ycombinator.com/item?id=16483241 I heard someone describe grad school as "17th grade" for some people with the wrong attitude. Google might be "21st grade" for others. That is, you're following metrics set up by an organization -- getting "graded" -- rather than building things for "the world". The way some Google employees speak about "the world" highlights that disconnect. (e.g. the wearables thing on the front page yesterday was mocked) To be fair, this is how things work at most jobs. If you work at a big bank or insurance company, you don't really care about "customers" either -- they are too far away from you. You care about what your boss thinks and his or her boss. This is sort of the "default" configuration of society.
- cmrdporcupine 6y agoYes, well, I agree with all those criticisms. It's been 9 years of frustration for me, here at Google. But that's not what my comment was about. I took issue with his griping that he couldn't hire and fire and drive a meat grinder. To me that's an entirely other kind of dysfunction... Perf at Google is broken. But I think it's endemic to large companies, probably. I only worked at smaller ones before. I worked for some that were meat grinders, and others that were better.
- g9yuayon 6y agoWhat the author said was a typical challenge in big enough company. Big companies over hire as time goes by, and the number of teams eventually outgrows the quantity of work. As a result, you have meetings all day to align, to coordinate, and to drive. The bigger an organization is, the more you hear about such phrases, and the more time you spend in meetings. BTW, I dare you to take away those meetings - so many people need those meetings to "assert influence", to get visibility, and to be promoted. In a large organization, people focus on Produktionsverhältnisse, aka relation of production, instead of production itself. This is also why the Bay Area is a truly great place to live in. So many small companies are there for us to choose. They move fast yet have reasonable work-life balance. They offer great financial perspective too, which can be far better than big companies if one's lucky. Of course, I'm not saying big companies are all bad. Indeed, some people are great at navigating company dynamics. They build solid relationship in a complex environment. They make things happen despite bureaucracy. They lead multiple teams to achieve impossibles. They cut through red tapes like hot knife cutting through butter. They build a company to last. So, the real question one should ask is: which type of person am I?
- kenjackson 6y ago> Big companies over hire as time goes by, and the number of teams eventually outgrows the quantity of work. As a result, you have meetings all day to align, to coordinate, and to drive. The bigger an organization is, the more you hear about such phrases, and the more time you spend in meetings. BTW, I dare you to take away those meetings - so many people need those meetings to "assert influence", to get visibility, and to be promoted. I think this is overly cynical. Big companies are typically further along the complexity curve. Complexity in engineering, but also sales, marketing, support, and growth opportunities (that is, growing revenue 25% is typically easier when you're revenue is $100K versus $100M). That said, they are real differences. A lot of people aren't going to enjoy that type of work, and will opt-out of it. But a lot of the lower-risk, better pay will be in this space (a startup is high-risk, potentially incredible payout).
- nixish 6y agoGreat dissection and incision of the OP's "fetishizing of the actual process of the making of the sausage vs the sausage itself." Creativity requires space. Space between work and space to think, be it on a yoga mat at 12 PM or a 4 PM refresher.
- jeffbee 6y agoI've worked at 8 different companies and none of them could even hold a candle to Google's pace of work. Everything just works. The quota system works, the identity and authorization system works, observability works, the build and release system works. You can be a productive engineer at Google on day 2 if you read the codelabs on day 1. Nobody at Google has ever needed to have their manager email the Jira admin to get them added to the right group to edit tickets. Nobody at Google has a need to raise a ticket with some ops group in Bengaluru to partition a Kafka topic, renew a certificate, bridge two VPCs, or any of that type of thing. It's almost frictionless. I don't get people who say that Google's pace is slow. I've definitely worked in startups where some kid thought they were ultra-productive with their late-night merges of 20000 lines of untested code, but on longer time scales those startups inevitably ground to a complete standstill under the weight of that debt.
- gresrun 6y ago5+ yrs @ Google, Google is my 5th company. Google has all the building blocks for great backend services and front-end development and, if you know where to look and have some experience with them, you can build a rock-solid product in <6mos, also assuming you have a team that can execute and the political will to ship it. Politics/consensus building is where the real roadblocks lie in Google, and presumably other large companies. Trying to make high-level product & technical decisions when you have 10 stakeholders with 3 VPs, all in different orgs, is serious exercise in patience; months of emails & meetings await you.
- cobookman 6y agoConsensus Building really sums up the issue. There's no clear decision maker at Google. There is no Tim Cook or Jeff Bezos. Instead it is a collection of teams in a department. It is like a democracy, but differs in that you need every single team leader onboard to get anything done vs say 51% of the "vote".
- joshuamorton 6y agoThis is far less true than you make it seem, I think. I can think of executives who are very clear decision makers in particular contexts. But for most engineers, most of the time, you're working well below the level of those executives, and especially if you're engaging with shared infrastructure, the executive who is the final decision maker is Sundar. For example, I am involved in an issue where 3 ICs whose levels are between 4 and 6 (really this is a simplification), are engaged in dealing with solving a problem. These three ICs are in 3 different PAs, reporting indirectly to 3 different SVPs, who join up at Sundar. It isn't worth it to have the CEO spend time refereeing this decision. Ultimately this was resolved at the director level, by consensus building, because it would reflect badly on every one of those directors if they failed to resolve it and had to escalate to SVPs or CEOs about something that is, on the company scale, trivial (to be clear this is still a thing that is multiple engineer-years of work, but it's still Google-trivial). I expect the same is true at Amazon or Apple. Cook and Bezos aren't making every decision. VPs and Directors deal with small potatoes, and most things are small potatoes. The difference may be organizationally that those companies are more siloed and so leaves from different trees interact less often. But this friction also is often intentional and has value (SRE explicitly not reporting up through normal product eng ladders, for example).
- ryandrake 6y ago> Google can on the whole accomplish its revenue goals without being a meat grinder. So why be one? This is a great take. I've worked in a place where the revenue was astronomical, to the point where the entire company could probably do nothing for 100 years and still be viable, yet it was run like a meat grinder, where everyone did insane hours and you always worried that it wouldn't be enough and you would be stack ranked out of a job. Truly awful, because it was so unnecessary. On the other hand, I've worked for a start-up with a visibly short runway, where it was obvious to everyone that if everyone didn't bust their asses, the company would fail. At least there you have an actual reason to be a meat grinder. I think a lot of companies could succeed yearly and make Wall Street happy and still not be a meat grinder, but some sick, stubborn cultural norm makes "meat grinder" the default mode of operation.