Except when your team wanted to initially onboard with GOOPS and your request sat in Buganizer for 2 weeks waiting for someone to triage. Uh oh — we're turning down this service next quarter, you will need to go start this onboarding process again with its replacement.
Or when you needed quota in a cell where your product area didn't have Flex. Maybe you can set up a VC with your PARM? Does next week work for your launch plan? Hopefully they can do something for you!
Or when your logs access request sat in GUTS for a month because both of the approvers were on vacation and no, there's not an escalation path.
Or when you needed to change a firewall rule for a project your team inherited which for some reason runs on GCE. Make sure you bring your Ariane link when you open your request. Have ISE reviewed your code? No? ISE currently have a quarter-long backlog, so we're not sure we can grant your firewall exception.
None of these examples are contrived; the weight of the operational bureaucracy is staggering. It may well be that this stuff is felt more on the SRE/Security side around production launches than on the SWE side for experimentation or iterative development, but I struggle with the idea that Google is nimble.
Most of what you described i felt as well _sometimes_ for security related stuff, like dedicated machines in that one cluster or an ISE review on short notice--but security related is also somewhat out of the norm and considering that is, Google does a great job.
For "normal" services what you described does not match my experience at all. Even for medium sized infrastructure services mostly everything just works (IME).
Never had a GUTS ticket that was not answered within a business day, but obviously just n=1 sample--imo support staff is mostly amazing.
The need to run in a particular cell is unusual.
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.
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".
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).
Next up is the documentation. That requires the doc team's approval. Oh they require IL8n, lets go to that team and see where in their queue we are <Doc team has power to delay your launch>.
This same flow occurs across all supporting teams. And it can get complex with Service A depends on Service B, which depends on Service C...and Service C can reject the quota increase delaying your launch...etc.
> I expect the same is true at Amazon or Apple
At amazon you would connect to who everyone reports up to, or whoever has clear decision making authority. You would then provide a written document going over the facts and suggested decisions, and ask they make the call. After that its "disagree and commit".
I don't see how this is distinct from what I said, except perhaps that for many teams, the GFE team reports up to a different SVP than you, so the person who you'd connect up via is the CEO, which like I said, doesn't scale for every launch.
If you want to try and escalate your launch up to the CEO, nothing is stopping you, except perhaps your director or VP. But that is itself a signal that perhaps this isn't worth escalating about and that the status quo is acceptable.
Emphasis on single product as they tend to have 5 apps that do the same thing until they kill off the popular ones.
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.
Even if sometimes people need to get fired, I’d say it is more important to make a good hire upfront and normally these people should be very capable and adapt to these dynamic environments. Just firing on the quickest difficulty says something about beeing rather a bad manager or not knowing how to hire / what to look for.
I’ve seen many incompetent managers firing their tech leader or program leaders just because it did not meet the set arbitrary delivery goals. By firing them it only reinforced the managing-by-fear way of working and lead to a cover-you-a* mentality that things just became even slower...
Thanks for your comment and I wish there were more managers like you!
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.
Don’t get the asymmetry. Why no firing for mgmt?
Yes, sometimes management needs firing as well, but in the context of my comment above, we were talking about a case where one employee's performance doesn't match up with the expectations of their manager.
To put it in the context of software engineering, if you have an engineer responsible for ten features in a year, and nine of them are coming along just fine, but the tenth was completely bungled, it would be incredibly rare to think that it was time to fire the engineer over the tenth. You're more likely to restructure things so that the engineer has less of a workload, or has help on the tenth, or maybe even just give them a bad review and make it clear that their performance needs to improve.
Firing a manager has an even greater cost for a company and team than firing an employee because the manager is a representative of the relationship between their employees and the company, so firing a manager also damages that relationship for each of their employees.
This is not exclusive to managers. Other roles like engineering team leads and senior architects also have a greater cost, because they're the employees whose roles have a connection to more people than just themselves.
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.
It doesn't have to be a black-and-white do-or-die.
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."
I'm not Ballmer's biggest fan, but I think he's often sold short (to Nadella's benefit), you'd almost believe Microsoft was tanking, but it grew a lot under Ballmer (mobile failures notwithstanding).
As far as I can tell, Nadella just reprioritized projects that Ballmer launched or shepherded in his boring-but-efficient way: what new tech or project did Satya launch that you can attribute MS's "turnaround" to? IMHO, it's mostly PR/hearts-and-minds stuff, but I quit MS tech a long time ago and haven't been following closely.
In retrospect, I think the Win mobile failures were overblown, the zeitgeist then was mobile would replace desktop/laptop computers, therefore failing on mobile could be fatal to Microsoft, and remained as a stain on Ballmers name. The "post-pc" world suggested by Apple/Jobs never materialized.
(MS employee; I work in Azure, but didn't become an MS employee until 2019.)
I think that article gets most of it. There's some MSFT narrative that comes up here a lot where people say Ballmer was doing great and Nadella just continued his plans, I don't buy it.
MSFT had a lot of strategic failures as well as product failures under Ballmer. Nadella shifted strategy and made them a serious competitor again.
Then it should be easy to say which green-field projects Nadella launched then. I can't think of any, but I'm open to learning.
They were making money hand over fist, massive growth in revenues almost ever year under Ballmer. [1]
Which part of that massive money train is 'not serious competitor'?
[1] https://www.statista.com/statistics/267805/microsofts-global...
Revenue growth isn't the whole story. If you're extracting rents from legacy locked-in products or enterprise deals that doesn't necessarily mean you're a competitor on the new paradigms (phone, cloud, web).
At the time Windows phone was a failure and they missed that entire platform because of Ballmer (there's hints of your argument in this video, "we're making money with windows mobile"): https://www.youtube.com/watch?v=eywi0h_Y5_U
MSFT cloud wasn't doing well and was overly focused on .NET
They were too focused on Windows rather than recognizing the strategic value they could provide outside of it: https://stratechery.com/2018/the-end-of-windows/
Today I'd make a similar argument for Intel. Intel doubled down on old style fabs and is not competitive with TSMC. They failed to compete on mobile. They're ignoring the end of x86 and mocking Apple: https://hardware.slashdot.org/story/21/02/08/2221233/intel-b...
Increasing revenue is a good sign, but it matters how. If you're making short-term decisions to extract money from legacy stuff at the expense of new products - that's bad for your long-term future. It can take a while to catch up to you, but it eventually will. Then you'll just limp a long as a dinosaur that makes enough money to survive but nobody really wants to work there and you're done doing interesting projects. That's basically what I mean by irrelevant.
Ballmer didn't 'make money from extracting rents and screw everything else up'.
Ballmer entrenched and expanded MS core products i.e. Office to the Cloud and along with that massively expanded revenues, which continue to this day, long after his departure, with no signs of slowing down.
He completely screwed up Search and Mobile, but those were risky new things, that's to be expected. Frankly he should have had 1 of 2 ...
But he also established XBox and Cloud; the former is a very successful play into a very difficult space (though maybe not as nice in terms of profits) - remember, Google just completely failed at this. The later, is now a hugely successful and growing business, and frankly, over the long haul has a shot at actually going toe-to-toe with Amazon.
Microsoft has 10's of thousands of sales people and direct access to every single CTO in the world if companies with > 1000 emoloyees. Much the same way they are going to stomp Slack, they have that kind of advantage (though not the same leverage) against AWS. Point being - he started a massive business.
Azure now has revenues of more than Windows did when Ballmer started, and it's growing by 40% YoY.
So yes 'revenue' is not the 'whole story' if someone is bilking a cache cow and running everything else into the ground ... but that's now what happened.
Ballmer 'grew and entrenched the cash cows' and made some other huge bets, some of them working out to the point where they are now also, big growing foundational aspects of the business.
'The Market' took a long time to recognize this, but all the historical sales numbers are there for everyone to see.
I believe that once Analysts realized that 1) Windows and Office is 'here to stay' and 2) due to AWS, Azure is going to be huge ... that they revised their view on MSFT from a 'old company' to a 'well run growth company'.
Satya seems great and has made some good moves, but nothing of the magnitude that Ballmer did. At least not yet.
Satya's changes have been positive but most of the money he is making is due to Gates + Ballmer.
I think he's good but we'll have to wait to see the full picture.
Clearly, it was in Apple's interest to emphasize the ascendance of mobile where they were strong vs. the PC where Microsoft was. I doubt Jobs thought desktops/laptops were going away, just that they'd become a less important part of the landscape--and that's almost certainly true among consumers as a whole.
I think if you could measure the man hours spent using iDevices and Android devices, as a percentage of general computing hours, you'd find that it would dwarf anything. Everyone has a smartphone now. And tablet sales alone outnumber PCs.
I am sure someone inside Microsoft saw this early, and figured that Azure could be a platform-agnostic backend to mobile apps and browser-based apps, without having to completing with Apple since they lack core-competences there. Pivotally, tablets failed to replace desktops in the enterprise market, as was initially predicted (and feared by Microsoft).
Office/Word Online (2010)
Azure (2008/2010)
WSL (Can't find info. Looks like it started before 2014 under Project Astoria)
.Net Core (Happened in 2014 - not sure who "started it")
This is a very US/EU centric evaluation of computing. It might not even be accurate for Gen Z, overall.
...but someone has to write the code first, before some of it can be deleted by a great engineer ;)
MSFT revenue has NEVER stopped growing: https://www.macrotrends.net/stocks/charts/MSFT/microsoft/rev...
That said, in general, at least for the well-paid workers at these companies, complaints about insufficient expense reimbursement like that come across as pretty whiny.
It’s not to feed you in your own home.
Of course, for many employees, the elimination of commuting makes remote work a significant win financially. But others never intended to do much more than sleep in their apartments and the current situation is therefore a net negative, even just financially.
"Oh no! I make hundreds of thousands of dollars a year, and I have to live in my tiny apartment, buy food, and I might have to get a bigger apartment."
vs
"Oh no! I don't have a job, and I'm about to lose my apartment because I can't pay rent."
Really nobody has a right to ask for anything, ever, because there's always someone who has it worse, right? The only legitimate rung of the ladder is the bottom one, and we just keep finding lower rungs to use to shame anyone higher?
Sure, there are people who live charmed lives and just don't understand what the big deal is because nothing has ever gone wrong for them. They sure as heck aren't me. But let's all just stop with the tone policing. It's 100% unproductive, and won't change anything about anybody's situation, good or bad.
vs
"I live in a tent encampment."
vs
"I live in a shantytown in a third-world country."
vs
"I am on death row."
vs
"I am on death row for a crime I didn't commit."
vs...
It's important to try to maintain perspective about our own good fortunes. But it's also human nature to feel our own pain as relative to our previous experience. Someone's always got it worse than you but that doesn't mean it's fair to expect everyone else to wander around farting rainbows with grins plastered to their faces.
All of the Googlers I know are well aware of the many ways in which we're fortunate and privileged. But we're also, you know, human, and occasionally whining about stuff is just part of the human experience.
Thank you for really getting to the point of this article.
But I would add...
I left my job etc, but now I going to stand on soap box and write an article about and make myself sound so self righteous.
People here give MS too little credit. Their reach is MASSIVE. No american company has the world wide reach that MS has. Practically every enterprise in the world is their customer.
Look at Apple before the return of Jobs (though at that point, they were having profit issues too - but what lead to that was arguably short-term thinking).
Today, I'd argue Intel has made similar decisions that put them on a bad long term path.
MS would have stayed alive for a while, but been a shadow of their former self.
Obviously, it's hard to prove a counterfactual like this - but this is how I model it.
MS can take all the good ideas, implement them and sell them worldwide before a startup can get out of silicon valley. Case in point: slack vs. teams.
You're right though - 'irrelevant' is too provocative and strongly worded.
I'm more focused on future bets and trends. I think that trend shifted at Microsoft from trending towards future irrelevance back in the other direction, to being a competitive threat again.
I find it interesting that Apple has money, hardware, OS, many apps, web presence. And now ARM CPU knowhow.
Why aren't they forcibly pushing into Corporate?
Sure, they'd have to develop corporate fleet management stuff but at this stage they could buy a few companies and be 80% of the way there. Or build it right from the start for only a handful of their hundreds of billions.
How many iphone toting CTOs in your average non-silicon valley companies would jump for Apple "Just Works" in their business?
Either they see something they don't like or a Gates/Jobs handshake said no.
Enterprise means people in suits doing sales calls. It’s a patient, one-on-one, handholding process, and it’s just not in Apple’s DNA.
Far better for them to come up with some new consumer widget that also leverages their strength in supply chain. That’s what they’re good at, and it’s extraordinarily profitable.
Microsoft obviously has large corporate presence, but also Xbox for example.
I just see so many already operational/technical/financial/branding assets in Apples favour compared to incumbents that I'm not sure how they'd fail to make money. OTOH, someone smarter than me in the company clearly thinks otherwise. I just wish I knew what they knew.
Maybe it is as you say, "just not Apple's DNA."
Not to mention most of Ballmer's misses were more Bill said no.
The charitable interpretation is that total compensation has just dropped, while the work hasn't. It's Loss Aversion[1], losing something hurts more than gaining the equivalent thing. Google isn't suffering from people staying at home using the internet more, it's not like Google cut manager salaries by 50% to keep the factory lights on and the orphans fed. Google's share price is up at least 50% since Jan 2020, and they've taken away some thousands of dollars of remuneration from staff and saved money on not having to run kitchens, and are demanding that staff feel grateful about this by handwaving at suffering people elsewhere.
> ">”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.”"
Calling legal and privacy efforts "a waste of resources" and saying they provide "zero value" /is/ saying they are not important.
Could that be just someone not liking sushi? As someone who doesn't like sushi and rather eat hotdog form gas station, I could see myself saying that.
Who the hell wants to deal with concur for every lunch?!
Then again, if your only goal is to extract as much money as possible from the corporate machine, it might work.
this system worked pretty nice imo, lunch wasn't anything fancy but it was healthy, cheap and having lunch with coworkers from other departments helped massively in regards to culture.
This is surprisingly not specific to Google. I've heard of other instances of this in other bay area companies, including mine. For us, it had to be put to rest at a company-wide all-hands meeting, along with other overly entitled complaints like "comp is not competitive", when in reality levels.fyi ranks it higher than even FAANG.
Greed sometimes defies logic.
This is definitely not true.
Ballmer increased revenues massively, and launched a slew of new products (XBox, MS Live, cloud etc.) and realigned the company. Have a look [1]
Nadella has done nothing approaching that level of importance yet, so far, he is riding the wave that was handed to him.
Now the stock price - this is a different thing. It sagged under Ballmer even as MSFT was massively growing revenues, around Naella's time investors realized that MS 'was not fading' and all that extra EPS was like a share price slingshot.
Ballmer was as transformative and important as Gates.
Nadella's early transformations were around culture, but that's just PR.
[1] https://www.statista.com/statistics/267805/microsofts-global...
The fact that it sagged under Ballmer and is now up under Nadella aligns with how I'm framing things. I suppose you could argue that's entirely PR, but I don't think that's the case.
People thought MSFT under Ballmer was trending down, now they think it's trending up. I'd argue that's due to strategic shifts that happened once Ballmer left.
I've mentioned in other comments that revenue (while good) isn't the whole story.
Sure, the stock price is always a prediction of future success. But it can change overnight, and when it does, it's not because reality or the "facts on the ground" changed overnight (usually) it's because perception changed. Often if not always because a catalyst made people aware of something that was building for a fair amount of time.
>strategic shifts that happened once Ballmer left.
I'm not saying this is wrong, but I don't think it's appropriate to treat the stock price as evidence of it.
I believe if Ballmer had of hung on for a few more years, that change would have happened eventually.
Investors eventually would realize 'This is not just Windows and Office'.
I think Ballmer couldn’t have done it, he was too tied up personally in windows.
Some of the examples you mention under Ballmer are more examples of strategic failure under his watch. Xbox is the easiest example, the Xbox One’s launch was awful and focus on cable boxes was bad.
I don’t think it took a while for investors to realize, I think investors had an accurate model of what was going on. When Ballmer left things improved.
1) He reconstituted Windows and Office distribution, sales, put office on the cloud.
2) He launched XBox and more notable Azure.
So if you think 'Desktop is dying' (desktop sales were plateauing) then 1 seems like it's going away and cloud isn't a huge business then 2 doesn't matter.
But the prediction was wrong:
A) Even with flatlining desktop sales, Win + Office continued to thrive. Even to this day. It's not a 'legacy business' it's a 'healthy ongoing business.
B) XBox, in particular Azure are huge. Azure makes more money today than Windows generated in revenue when Ballmer took over Microsoft.
Ballmer's failures were mostly Search and Mobile ... both of which were sad, but also they were up against Google Search and iPhone, the best products of our era. XBox and Azure are in very difficult areas, and are doing well.
In hindsight, Ballmer did quite well, there's not a lot to debate unless someone things that Search/Mobile success should have been imminent, but I don't think that's true.
He massively grew and adapted the baseline businesses, and started a few new, huge businesses. Glorious profits all around.
Satya hasn't yet quite made the kind of decisions that will have the lasting impact Ballmer has had, in his defence, he's in an era were the 'new fields of competition' are less obvious.
Windows + Office is a legacy product line. It makes money, but it's not the future. They need it obviously, but over-focusing on that at the expense of other things was a mistake.
The Xbox launched in 2001 - was the original one even Ballmer? I think Gates left in 2000? I'm not sure that counts. Xbox One launch/strategy was bad.
I'm not trying to say he did nothing right, but I think we just disagree on this.
What comes to mind most recently? See Slack.
I gotta say, all those Unices fucking sucked. The userland tools were abysmal, with missing flags or bugs in their getopts, the compilers and their sockets libraries were extremely finicky, and their man pages were anemic.
GNU/Linux won because if something sucked, somebody somewhere would fix it. By the early 2000s, and especially after Linux 2.6, it was obvious closed-source UNIX was both worse and overpriced.
Even now it seems like the best part of the closed source MacOS Unix stack is the open source homebrew/macports stuff.
Apropos of the "curated App Store" or "free-for-all" discussion currently active, I remember talking to a colleague in the early 2000s that Apple with its curated BSD-derivative OS was exactly what open sourced OSes needed. Users don't want to do more work than necessary; in retrospect, the selling point that users can do anything+everything with *nix OS was the wrong message.
You didn't mention package management and network booting to be pain points. They were nightmares, which Linux eventually solved. I think that's where the race was lost.
There is always some drops fear trying to find a way up my limbic system whispering to me that one day this will be over. One day, I will have to work for real again and I will have to pass tough interviews and have new, possibly demanding bosses. But this has been going for more than 4 splendid years, very long-termism tend to make one's life pretty dull, and my dream is to open a bicycle shop anyway.
As a famous ad campaign used to suggest: "Think different".
You wrote: "Compensation for a job is about more than money. It's about where you end up as a person when the job is over.". It sounds good in theory, but in practice? Should I switch job, maybe/likely accepting less money and more stress in the coal train now because when the luxury train stops I will be in a better place (I am exaggerating for conversation purposes)? I have my doubts. This is specific to my situation and I don't want to explain too much (and that's why I use a throwaway account), but outside of the US that would sound bizarre. Switching from a cushy well-payed job to a demanding, paying-less job because in a few months/years it will be over? Yes, maybe I will get rusty here and there, but I can move to Tulum for 3 months and get ready for interviews, no?
EDIT: typo
- Look for opportunities to contribute more at your job. Don't wait for a manager to tell you what to do. Rewrite some code. Propose a new feature. Improve the documentation. Write more tests.
- Teach yourself new skills. Don't just skim books on new languages/technologies. Develop a personal project and pretend like you're being paid to work on it.
- Take practice coding tests. Stay up to date with relevent skills.
Enjoy the job you have now, but keep yourself ready for the day when that job goes away. I had a very easy job for about 6 years. I automated most of my job and effectively did not have a boss. I made great money and spent most of my time working on hobbies, hiking, or working on my house. When the job ended I suddenly realized all of my skills were rusty. I regret wasting all of that time, and wish I would have used it to better myself.
As I like to say: there is no second life, the only one that was build was virtual and "failed".
> when the tide turns, it is not that they are looking at some code review you did or improved documentation you wrote to keep you onboard.
I mostly disagree, but it depends on your employer. As a senior engineer, I very much have the opportunity to differentiate myself and protect my position longer than others. I lost my easy job to lower paid, lower skilled engineer because I chose not to put in the work which would have defined my role as a more difficult one. It was easy to replace me when the time came because I allowed the scope of my role to shrink to menial tasks which did not require much thought.
I've worked with plenty of sysadmins who suddenly had no choice but to become software engineers. That learning is brutal for some of them–years long process, maybe never. 3 months may not be enough if you coast for long enough.
Where? How do I find jobs like this?
I get what the sister comment points out about long-term stagnation, but at the same time, I could desperately use a few years without a resume gap, but without a perpetual dagger hanging over my head.
Panic attacks are brutal and getting employees to the point of having panic attacks is part of what is wrong in the tech world. And it happens, in big corps, because some people want to advance at the expense of others.
Would you say that any particular background and skill set or credentials/laurels (publishing? writing? speaking? management? management at a certain level?) sets you up most appropriately for getting this sort of role? Basically, how do I take any actionable steps to find those positions or move in that direction.
As to how to find those positions, my recommendation would be to look for (1) high-revenue, big companies (they have the money and they have the space), (2) going through some sort of transformation (moving to the cloud, opening a new business area), and (3) need prestige, both internally and externally.
You can find those jobs in job ads, but you need to look at the ad written most of the time by a semi-clueless recruiter through the lens of points (1-3) above.
You get little more than a pat on the back.
Either public sector companies, or banks & insurance whose business model can't be disrupted that easily because of regulatory pressures.
Giant IT companies from the valley that successfully built a way to lock down users are the other example.
Isn't that why so many people flocked there to work in the first place?
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.
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?
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).
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://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.
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.
> 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...
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.
Lol, yeah. A lot of what he said made me nod along :)
Creativity requires space. Space between work and space to think, be it on a yoga mat at 12 PM or a 4 PM refresher.
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.