That "CYA" response really doesn't feel like "us" to me, at least not the AWS side. I can't speak to the experiences on the store side, nor on the devices side. Over in AWS, we practice the "blameless postmortem" model you'll read about from time to time, and it is very rare to see any professional or personal consequences beyond some light joking come about from "breaking prod"
To that point, I know personally the engineers who triggered several of the AWS outages you will have read about in the news over the last decade and more. Some of them are still with us, some have been promoted since then.
Depends on the team. In my team in AWS, if something was your fault, the manager would call you out in front of the entire team. Then they wondered why attrition was so high.
Your experience also matches mine from my time in the advertising org. There's no benefit to placing blame, just figure out what went wrong, how to fix it, and how to prevent something like it from happening again. In fact it was one of the few parts of the culture that I tried to take with me after leaving.
Reminds me of that classic parable about the CEO and the worker who just made a $100,000 error. The worker says, "I assume you'll be firing me now" and the CEO says, "Fire you?! I just spent $100,000 training you!"
I’m agreeing with the “it’s not us” vibe.
I work on a team that has some planet wide scale software pipelines.
I broke it, hard. I’m not a software engineer so I had no idea how to undo what I had done.
People from 3 different teams, two of them experts from other teams who heard my call for help hopped on a call and spent all day helping me fix the issue I made and then some. This was a hard stop on a cortical package pipeline for 24 hours and at no point did I feel like my job was at stake despite it clearly being my fault, and due to me running a command I know I shouldn’t have and cutting corners.
Current (long tenured, moderately senior) AWS engineer here. I've been at the company long enough it's pretty clear that I'm a "good culture fit", so take what I'm saying with that in mind.
While I absolutely believe that there are pockets of the company that work this way, more because of sheer scale than anything systemic, I have sat in the annual ratings meeting for engineers enough times, in enough organizations within the company, that I am pretty confident that this experience isn't universal.
It sucks that this author had this experience, and I wish they had said which team that was, so that I could use what social cachet I have to steer people clear of it from inside. Nobody should have that experience.
It’s a thing. The author was not unlucky. It’s actually a thing (I worked in AWS, I have heard this from several managers, some which actually had trouble struggling with how stupid the system is).
You have a team of X engineers and you want to grow. You hire a couple more. The current engineers have 0 incentives to help the new ones. Most people don’t have the chops (technical or emotional) to go up against a whole team.
Come review time, what do you think is going to happen? As a boss will you let go someone who’s been there for 5 years and knows the service inside out or the new guy who seems to be struggling.
Not all people are jerks, and there are good pockets (but mostly the deck is stacked against you when you join).
Also, IMHO Amazon is going to have a really hard time hiring people with the reputation they created for themselves.
> Also, IMHO Amazon is going to have a really hard time hiring people with the reputation they created for themselves.
The majority cares about money and convenience. If people really cared about reputation then Riot Games, Microsoft, Tesla, Facebook, that big ride sharing company whose name slipped my mind, Shell, and lots of other companies, would be struggling to hire.
Microsoft really only pays comparatively at each end of the spectrum, so for new grads out of college and people who have Wikipedia articles.
For the majority of people in their career (the Seniors and Principals/Staffs) MS pays significantly worse than other FAANG-type companies, often being well under half in terms of stock compensation for example.
The company is well aware of this as it's constantly brought up in all-hands (both within individual departments as well as at the all-company level), and they always respond with "we've done research and we believe we actually do pay comparatively in this market segment".
the 'poorly paid' employees can definitely afford a lawsuit. here's the thing though: if you know what the situation is and continue to work there who is to blame?
also, most stories I've heard is that the sub-optimal comp comes bundled with pretty good WLB. So maybe if you were to double the number of hours worked and double the comp M$ would blow other BigTech out of the water. Maybe this is the play (half the money for half the effort) and everyone knows it.
Do you base affordability on what? The type of lawyer average employee can afford will be easily crushed by a top law firm with virtually unlimited funds.
The fact that one can change job shouldn't enable companies to continue like this.
People have no choice if all companies are doing same thing.
The minimum wage should be tied to company revenue to reflect the value workers generate. I mean revenue, not profit, because those companies are masters at hiding profits to avoid tax.
if the compensation is artificially kept low yes, this should be (and is?) illegal. the fact that there are other places nearby that pay really well tells me that, at a minimum, people have options.
Does Tesla give out heavily subsidized (or even free) cars to employees?
Had a friend who worked at Mercedes Benz corporate and he could pretty much pick any non-AMG car in rotating 6-month leases. The monthly lease payment for him to lease a SL550 (a six figure convertible) was about the same as leasing a Honda Civic.
Seems other car companies do similar programs for their employees.
>The current engineers have 0 incentives to help the new ones. Most people don’t have the chops (technical or emotional) to go up against a whole team.
This is why companies want to hire rockstars who can be productive in a couple of months without being helped by colleagues. One can't get such rockstars just by leetcode. Maybe, these companies should pay $1M per annum for such rockstars.
you know. being a rockstar is not a solo thing. It’s a team thing. Usually rockstars teams are born out of high functioning teams where everyone is making everyone better.
Like I said, I don't doubt that they happen, but given that you've also left the company and seem to have hit one of these areas of toxicity yourself, I'm not surprised you'd think so. Who was your last manager? I'm curious if it's anybody I know?
> seem to have hit one of these areas of toxicity yourself
Have you considered that the original poster's experience is actually the norm and that your experience is the one that is the anomaly? I was 1 for 2 in organizations with shitty leadership, and the organization that was run properly had zero open headcount. Everywhere people are hiring into is not one of the "good ones".
Check out the old-fart tool, 85% of the company has been at Amazon for 3 years or less. Do you think that if the normal/average organization/team was a great place to be, that there would be so much attrition?
But hasn't Amazon expanded massively in the last 3 years? I'm not sure how meaningful those numbers are unless the employee count is relatively static.
I have considered it. I don't see the pattern widely, and I'm watching for it. I've seen teams implode because of it, and other toxic patterns, so it's not that they're not there... they just seem to be in the minority. There are teams I won't send friends to work for, for sure.
I've been doing software development for nearly a decade now and I've seen 0 teams implode. Nothing I would call a "toxic pattern" springs to mind either. If you've seen multiple occurrences of both at Amazon and think it's an ok place to work then I think you've just normalized the dysfunction.
> It sucks that this author had this experience, and I wish they had said which team that was, so that I could use what social cachet I have to steer people clear of it from inside. Nobody should have that experience.
No, far from it; I'm not HR, nowhere close, but I am senior enough that people sometimes listen to me. I'd like to make things better for people if I can, and part of that is "knowing where the problems are". Believe me or don't, it's no skin off my ass, but that's the opposite of my goal.
This isn't the first time I've read about Amazon's 30% mandatory turnover rate, how it effects new hires mentally when they can't help but think they might be fired at any moment, and how it effects the ones who actually did get fired. This sounds like the definition of a systemic problem.
What's really needed here is a way to maintain super-scale in a way that is, shall we say, "eventually morally consistent". Applying selection theory, if you create a pocket of badness wrapped in a function that reliably extracts all the good out of it... well all you'll be left with is a local maximum of even more suffering. Yeow.
Of course, designing and maintaining such social structures seems close to P=NP in complexity...
I didn't reveal my team to maintain some form of anonymity. If you're an L8 or above then you may have some power to do what you said. Otherwise I don't think it'll make a difference.
translation of the first two paragraphs is "I've decided what I think already and if you say you work at Amazon now and are happy it's prima facie evidence that you can't be trusted to be objective about it"
If it's a liability to say nasty stuff about the employer and most of the ex-ones throw some heat the nearest possible conclusion is that the truth tends to bow to statements that are observed as outdated and controversial by present employees.
It just can't be a smear campaign against just that one company.
Yeah, I work adjacent to the Apollo org (and have worked near Pfrheak, too. Hi!). I would love to see a HackerNews commenter's idea of what it would take to re-implement Apollo. I'll bring popcorn.
Oh, wow, what an amazing take. You owe me a new keyboard.