There seems to be hot-spot groups that seem to originate a majority of the complaints, and they're not the tech teams we think about first when we're on HN reading these stories- a lot of the horrors happen on the 'non-tech' side.
With all that, I'd still never work there. It's generally a very tough place to work and I've heard of all kinds of funny ways those big bonuses have a way of disappearing/shrinking. As I tell the recruiters every two weeks when they inevitably call or email- I appreciate the tools they've built for me to run my company, I'm a Prime subscriber, and Alexa basically runs my house, but I want nothing to do with stepping foot in that campus as an employee.
Anyway, this guy was frank enough with me about that stuff, that I actually believe him when he said that all those bad articles about amazon's culture (which had just come out weeks prior at that point) were probably accurate for some parts of the company, but he had never encountered it.
I didn't end up getting an offer from them ( I wouldn't have hired me based on the tech interviews either. Every single applied programming problem was some form a tree traversal, which I don't use regularly anymore) and was a little relieved that I wouldn't end up working there.
Amazon is not very friendly towards open-source. When I was there, I believe their policy was that you needed to ask for permission to contribute to any open-source project. The policy was broad (covering things like code snippets on StackOverflow or /r/programming on Reddit) and strict (I heard they would not approve anything related to game development). There definitely were folks who contributed to open-source projects -- I think those people either didn't ask for permission or had friendly managers.
If you have something new you want to work on, you normally need to contact your company's legal or HR team and get signoff that you are allowed to work on it (and that you can maintain ownership of it).
https://www.quora.com/Can-a-company-claim-ownership-of-a-per...
The first time I assumed that it was just a freak thing, after the second time I asked around and got the vibe it was completely normal for a variety of reasons, often because a manager on the interview cycle with more clout decided they liked you and you were therefor going to be working for them.
I like a lot of things they build and believe there are some very talented people there, but at what cost am I willing to participate in that activity directly? Not that high, I'll just reap the fruits of their labor from the outside.
I've worked there myself and have a ton of friends who have spent time there. Some folks have even enjoyed working there. Overwhelmingly the evidence is that Amazon is a very bad place to work at, on average. You might get lucky and find a good team (amazon is incredibly federated as an organization) but you might also get unlucky and get an extra bad team. Also, unlike a lot of other tech companies of similar size (such as Microsoft or Amazon) there's basically no "love" at the corporate level for individual employees. At other companies reaching that "full-time employee" status level means something, and the company is willing to invest in you. You have the ability to move around to different teams, you have the ability to change your role. You have a wide range of options in terms of training to take. Working as an FTE at Amazon feels like working as a contractor anywhere else.
It's very dysfunctional, though there are enough devs who mostly know what they're doing who stick around for a long time to keep things running. Additionally, the service oriented architecture of the system makes it a lot easier to cycle through lots and lots of devs.
Of all of the folks I've known who have worked there most left after a short period of time because they hated it.
That said, I have generally positive things to say, but I've also witnessed an entire team of 6 SDEs quit under an especially bull-headed SDM. I've also seen managers making ridiculous promises to upper management without vetting them first.
Thankfully the bad SDM found another job, but he's still working in another department in the company.
Could you clarify? that's kind of what I expect when being on-call anywhere
Most importantly, unlike a typical Ops/DevOps job where being on-call is "your job" you are still expected to deliver on your "real" development job in addition to being on-call.
Amazon is an okay to great place to work if you have low standards and low self respect/esteem. Many engineers are this way without realizing it even. (Because we can see all the flaws in ourselves and our systems and don't realize that this isn't objective, so when we're mistreated we figure it's more legitimate than it is.)
Of the people at amazon who were happy there when I was there, it was mostly people with low requiremetns- they figured if they got their paycheck every month they were happy. They weren't bothered by their bosses abusing them verbally, or the other nonsense that others have talked about.
I like how you just make a blanket statement like "It is okay or great if you have low standards and low self respect/esteem". Way to play the superiority card. I know guys who went from Amazon to Google and say they liked Amazon way more.
Our experiences are obviously both anecdotal.. but only one of us is making condescending value judgments of others.
I wasn't being condescending. There are a lot of engineers who have low self esteem (that's not a value judgement- too high self esteem is bad, as is too low, but "low" means "Lower than their value as a person", eg: they under value themselves. I'm not devaluing them.) And there are a lot of people who just aren't too picky about their workplace. I think that many of them are people early in their careers who don't know that they're being mistreated as poorly as they are.
Before I worked at Amazon I heard many stories from people who worked there about how terrible it was. I foolishly discounted them, and went to work there anyway, in large part because I undervalued myself, (eg: low self esteem effectively) and I was not being as picky as I should have been.
Just because people made the same mistake I did and might have felt the company was ok, because thy didn't have the alternative experiences I did, doesn't mean I'm wrong.
I consider you to have turned my comments about the topic to the person, by making a condescending characterization of me that was unwarranted by my comments.
Contrast that with startups where the lack of resources and increasing growth makes it feel broken.
Also if you're growing headcount very quickly, culture doesn't always get transmitted and you can end up with factions fighting against each other.
"Life is pain. Anyone who says otherwise is trying to sell you something."
You do, however, get to pick your pain. Pain from growing too quickly feels much different from organizational disfunction.
In Amazon's case they might have both (!) because of how fast they grow and how big they are.
Sometimes, the people part of the bad ones wake up and start bitching, then you get this.
Google has great reviews, but it has its share of bad departments. It also has a lot of koolaid drinkers, so the people who work in those just bitch about it a lot to their friends and it never goes any further than that... Eventually someone will post a NYT article about it and make Google sounds totally horrible because of those localized issues, just like Amazon. Or maybe they'll just keep drinking the koolaid. Who knows!
I don't buy this as an excuse. There are too many stories about Amazon culture to write them all off as a loud minority. Either Amazon has more bad departments than other companies or the bad ones are just worse. Either way I don't care, I don't want to work in a toxic environment and am not going to coin-flip that I get put into one of the good ones.
Though I blame it more on their slightly looser hiring practices. A lot of people get hired there that have no business working as engineers on hard problems anywhere. Then Amazon does what most tech companies seem to have trouble doing: can them (they should not have hired them in the first place, but still). Then they write stories about it complaining about how great they were and were canned.
You're suggesting Amazon struggles not because of bad management (as almost every story suggests) but because their developers aren't skilled enough? That's a really strange claim on the face of it.
That said, they totally have bad management. Like the majority of tech companies minus a couple of shiny ones. What I'm saying is that, aside from the fact they are a pretty visible target among tech companies with shitty management, one of their main issues is that they have very lax entry requirements, so not only people bitch about the real issues, they ALSO bitch about non-issues because a large segment of their devs suck. Yes.
Silly of you to claim amazon has lax hiring standards.
I find this to be true of the megacorps I've worked for but the problem at amazon seems to be the entire culture starting with Bezos.
We are not talking about a single person here. There is a systemic issue it seems.
The Amazon issue isn't just that they are large. IT's their culture, which is employee hostile.
Companies have processes and policies, I don't buy the "bad department" excuse. Of course, some have it better than others, but often bad working conditions are the result of policies put in place by the upper management.
And the fact that Amazon is as big and healthy of a company as it is and the fact that it loses an entire point compared to Google and Facebook in ratings means that the culture must be really bad. And when you consider that the lowest of the companies in Glassdoor are not only shitty culture but businesses that are fundamentally swirling down the toilet bowl as well -- and Amazon for all its success can only eek out an 'Average' rating?
That means the culture must be pretty bad.
(And based on my working there for 5 years, I know the culture is pretty bad -- but if you asked me to rate it, I'd probably rate it a 3 overall -- good place to spend a year or two to learn some cutting edge technology to get on your resume, but then you should escape before you stay there too long...)
It's the same in that glassdoor thread you linked: even the people who are trying to recommend Amazon as a good place to work end up making its culture sound aggressive, cutthroat, and inflexible. Not my cup of tea.
1) I'm never going to work at Amazon
2) If you're judging a company based on the experiences of those who are dissatisfied, isn't that always going to be heavily biased?
At any large company, there will be many people who are unhappy and dissatisfied. If you go out looking for stories from such people, and compile them into a single digest, it's going to make any company look dysfunctional.
Using a glassdoor-esque rating system seems like the best way to judge a company. And Amazon's rating there is 3.4 (https://www.glassdoor.com/Reviews/Amazon-com-Reviews-E6036.h...). Which is nowhere near Google (4.4) or Facebook (4.5), but it isn't horrible either. It's even slightly above average (3.3) across all companies in Glassdoor.
Which does kind of make sense... no tech company can churn out great technology products over many years, if the work-culture is dysfunctional. Purely for that reason alone, I'm sure Bezos would put a lid on how bad the work culture at Amazon can possibly get.
All of which is to say... I get the feeling that Amazon is probably an okay place to work. It's not great. It's probably a little below-average for the tech industry. But it's probably not as dysfunctional as these reviews and horror stories seem to suggest.