3 ms·

I heard many times Amazon is a pretty bad place to work at. I wonder what percentage of people will decide to leave because of this. As someone who has been 100

I heard many times Amazon is a pretty bad place to work at. I wonder what percentage of people will decide to leave because of this. As someone who has been 100% remote for 6 years I can say with confidence, there are people that work best remote, and there are these that work best in the office. It is also a function of your seniority level (I'd much prefer to be on site as a trainee/junior). But forcing a one size fits all solution is the worst solution there is.

deleted 3y ago
[deleted]
CoastalCoder 3y ago
One anecdotal data point: I was contacted last week by an Amazon recruiter. Although I'm unemployed, I didn't pursue that opening because of Amazon's overall reputation. If they still allowed mostly remote work, I would have just told her that I wasn't interested at this time. I.e., if I'm still unemployed in a month, I might suck it up and apply. But the non-WFH policy was the final nail in the coffin. I asked her to never contact me about Amazon openings, even in the future.
- BitwiseFool 3y ago
  I've heard a lot of developers know that Amazon is a terrible company to work for, but having Amazon on your resume is a career booster. So they'll work there for a year or two just to enhance their future job prospects. Is this still true?
  - CoastalCoder 3y ago
    My personal bias is that someone who joined Amazon in the past few years was probably desperate or naive. But maybe it's just me, not sure.
gaoshan 3y ago
I have a friend there that was hired into a mid level developer role and he hates it for many reasons (from management style to the personality of teammates to how code gets reviewed and pushed and more). Just biding his time to get enough years under his belt for his next move but he ranks it last in places he's worked (but first in pay, which is why he is sticking it out).
wkat4242 3y ago
Not just a bad company to work for, but also a bad company to work with as a client IMO. I stay very far away from them just as with Oracle though the latter is worse as a client (they don't seem to be bad to work for I hear)

deleted 3y ago

[deleted]

CoastalCoder 3y ago

One anecdotal data point: I was contacted last week by an Amazon recruiter. Although I'm unemployed, I didn't pursue that opening because of Amazon's overall reputation. If they still allowed mostly remote work, I would have just told her that I wasn't interested at this time. I.e., if I'm still unemployed in a month, I might suck it up and apply. But the non-WFH policy was the final nail in the coffin. I asked her to never contact me about Amazon openings, even in the future.

BitwiseFool 3y ago
I've heard a lot of developers know that Amazon is a terrible company to work for, but having Amazon on your resume is a career booster. So they'll work there for a year or two just to enhance their future job prospects. Is this still true?
- CoastalCoder 3y ago
  My personal bias is that someone who joined Amazon in the past few years was probably desperate or naive. But maybe it's just me, not sure.

gaoshan 3y ago

I have a friend there that was hired into a mid level developer role and he hates it for many reasons (from management style to the personality of teammates to how code gets reviewed and pushed and more). Just biding his time to get enough years under his belt for his next move but he ranks it last in places he's worked (but first in pay, which is why he is sticking it out).

wkat4242 3y ago

Not just a bad company to work for, but also a bad company to work with as a client IMO. I stay very far away from them just as with Oracle though the latter is worse as a client (they don't seem to be bad to work for I hear)