No, I've not worked there, but all of the evidence at my disposal (your comment included), leads me to believe your Amazon experience is highly dependent on where your work group sits in the Amazon network. To shrug off the stories as potential fabrications seems as intellectually dishonest as assuming the stories of extreme treatment are commonplace.
At the very least, how much a person is willing to question the hand that feeds them can reveal the strength of their character to others.
Careful! You are straying into fundamental attribution error territory. Those who bite the hand that feeds them may be in a better position to do so or feel more encouraged by the people they know.
Note, I believe that Noble does not always equal smart, where smart equals maximizing good, corporeal outcomes for one's self.
I believe that once the percentage and degree of complaints meet a certain threshold of systemic cruelty, then my strength of character argument might (might) apply.
I was treated well, and everyone who I had contact with over my 18 months was similarly treated well (with the exception of forcing client developers to go "on call" for server issues that our team knew NOTHING about...that was cruel and unusual, but even that didn't require 80 hour weeks, just the occasional 2am pager beep).
Our branch of the org chart was happier (according to internal surveys) than Amazon at large, but those internal surveys absolutely didn't paint a picture of tons of unhappy people.
That said, I'm sure there are bad managers at Amazon, just as I had an awesome manager. There are just too many people there for them all to be perfect. But the picture from where I stood was honestly as positive as I described.
So don't throw around aspersions of my character when you don't know my situation, or what I observed.
ASIDE from the fact that I DID leave Amazon and sold all of my stock, so it's more like "the hand that fed me for a while."
Anecdotal support for hypothesis: Have been told firsthand by several people that they lie on these types of surveys and don't think results are truly anonymous.
I'd love to see a broad study of this across companies, conducted by a third-party organization with no affiliation to any company studied.
In general, I'd estimate anything below 4 (on a 1-to-5 scale) on those surveys could indicate a problem. What if "3/neutral" really means, "This actually sucks but I'm not willing to tell you that because I don't trust you"?
I doubt there are many internal surveys showing "tons of unhappy people" unless employees a.) have no fear of company reprisal, for whatever reason; or b.) have entirely given up on the company and are in open rebellion.
Amazon employs roughly 150,000 people. It's pretty arrogant of you to assume that everyone else must be lying just because the bad things didn't happen within sight of your department.
I was based in Seattle, though I worked from remote. I was told I could have made Principal within a year if I were willing to move to Seattle. Which I wasn't.
Mind highlighting what those "hard-to-find" skills were?
Someone on my team actually quit without notice three days after he was first forced to go through an on-call week. So I don't want to sugar-coat it: It was everyone's least favorite activity.
Basically $60K (or whatever salary) isn't $60K everywhere, it's relative. It's a reason why some "put their time in" working in SV, then move to Nebraska or something for a comfortable living.
As someone who competes against them for talent, and having seen dozens of examples from different parts of their business, Amazon is an extremely competitive employer on the tech side for experienced employees. They typically pay nicely above market
I don't think you want this, either. The gravy train in Silicon Valley would halt instantly if the jobs were all remote and engineers in low-cost-of-living countries had an equal shot at them.
There is a value in having good people work in the same room. I think it's overvalued, but it's not zero.
And if companies want to hire a top engineer in the Bay Area, they're simply going to have to pay more than if they want to hire an engineer in Des Moines: Competition for good local employees is much higher, and higher competition for fewer resources means that the rate for those resources will go up.
If you're a senior developer in the Bay Area right now making less than $115k, you're not trying hard to get a raise. If you're in Des Moines making $115k, you're in the long tail; the 90th percentile is $108k. [1] The MEDIAN in San Francisco is $115k. [2]
And that doesn't even fully capture the state of the industry, because there are a few employers who go well beyond the median. Most senior engineers I know who are working at one of: Facebook, Google, Amazon, Microsoft, or Twitter, earn over $200k (total compensation, counting stock grants), and many earn closer to $500k.
Des Moines doesn't have major campuses of any of the above employers (correct me if I'm wrong), so the increased salary pressure from the high rolling Internet companies isn't affecting the local market.
Would love it if more big companies would hire remote workers; it would "spread the money" around the country more evenly, they could probably find developers for less, and it would reduce the amount of greenhouse gasses wasted on commuting.
But until they do, a significant fraction of the best developers will congregate in the Bay Area, where they can potentially pull in $500k/year instead of a pathetic $95k. Because good developers are worth that much in value to the company, and any good developer making less than $120k is being exploited.
Even in Des Moines.
[1] http://swz.salary.com/SalaryWizard/Software-Engineer-III-Sal...
[2] http://swz.salary.com/SalaryWizard/Software-Engineer-III-Sal...
Obviously there ARE still sections of Amazon that are broken. Others have suggested as much in comments as well.
Sorry your friends had such bad experiences. Hope they found a better employer.
I just spent a year and a half working for Amazon, and the recent reports about working conditions were, as far as I could tell, either fabrications, or things that hadn't happened for years.
Working there was great. Yes, I was in the AWS tree, but I also had contact with people in the Retail tree, and didn't perceive any differences there.
Low-wage jobs like fulfillment...I don't know. I'm a developer.
Oh, and did I mention the pay was great? Hard to complain, really.