4 ms·
This isn't all. Sometimes, even when you're not a _fire-worthy employee_ (for lack of a better term), just to fuck you up, the manager could choose to mark you
by ignoramous 8y ago
This isn't all. Sometimes, even when you're not a _fire-worthy employee_ (for lack of a better term), just to fuck you up, the manager could choose to mark you as "least effective" in the year-end / mid-year review and not really put you up for a PIP... Now... even though you performed good enough, there's no jury to appeal to. What happens next is that the manager could then systematically deprive you of quality work and come year-end / mid-year review, s/he has a solid case to PIP you and throw you out. Note that, being marked "least effective" essentially means that one can't transfer internally to other teams unless someone wayy higher up the management chain approves of the transfer.
I'd be lying if I said I didn't see this seemingly happen with multiple people across multiple Amazon development centers.
This place is toxic and puts way too much power in the hands of the managers, and the net result is that the managers have their favourites, and that the engineers are nothing but puppets, and that engineers are busy back-biting each other, and the managers enjoy the shit show from the sidelines. Despite not having any moral high-ground, all managers in an org review every reportee in that org with absolutely zero fairness, there's no integrity whatsoever, from what I've heard.
And I'd be lying if I said this _thinking_ didn't take it roots right at the very top of the management hierarchy (...according to employees I've spoken to).
- throwaway2048 8y ago>Note that, being marked "least effective" essentially means that one can't transfer internally to other teams unless someone wayy higher up the management chain approves of the transfer. What a hilariously counterproductive policy, obviously people that just barely exceed the incompetent-enough-to-fire low water mark are going to be given glowing reviews, then pawned off on some other team.
- paulsutter 8y agoWhy do you stay? > I'd be lying if I said I didn't see this seemingly happen with multiple people across multiple Amazon development centers.
- StudentStuff 8y agoI've asked this question to multiple Amazonians who have worked there for 4 years or more, and I've yet to hear a decent answer. There are many companies that have sub-40hr work weeks that will pay you as much as Amazon (plus stock grants), but yet most won't make the time for an interview. All the people I know at Amazon in Seattle consistently get home after 7pm most nights, and a handful of those people come in on the weekends for 10 to 12hrs to fix mundane bugs that aren't in need of immediate fixing. Amazon's high pressure work culture encourages this terrible practice of burning the candle from both ends, but Amazon definitely doesn't create quality products on the first try in part due to this.
- natalyarostova 8y agoI've noticed across education and work systems, there are some areas that have an extremely high barrier to entry, and treat you well if you make it, and others where the barrier to entry isn't as high, and getting in doesn't mean you've made it. I've always had an atypical (read: not traditionally competitive) background, both for schools and jobs. As a result, I've found universities and firms that are willing to take a chance on me the best. They are great for me because the tacit agreement is "I know I don't meet the traditional standards, but I'll work hard to prove I'm worth it. And if I'm not, I know you'll fire me." No one ever says it, but it's the strategic system that underlies this. In short, Amazon offered me a job and a salary no other tech company would have. Not even close. I've had to work nights and weekends not on Amazon, but just on teaching myself the tech to do my job (I'm a data scientist who could barely code when I started). And I'm not doing bad. I'm not a genius, but I'm valuable enough. Once I get all my stock and a promotion, I might look at a 40-hour type company. On the other hand, my team is pretty fun, so I don't know.
- chibg10 8y ago>All the people I know at Amazon in Seattle consistently get home after 7pm most nights, and a handful of those people come in on the weekends for 10 to 12hrs to fix mundane bugs that aren't in need of immediate fixing. I can't speak on everyone at the company, but the campus is basically empty at the times I leave at 7-8 (which isn't often and usually happens when I show up at 11-12). My own building is 95% cleared out by 6pm on a daily basis. Not saying what you hear isn't true, but it's definitely appears to be the exception rather than the rule from my experience.
- shitlord 8y agoOne of the biggest problems at Amazon is the lack of accountability for managers. Someone who consistently works their direct reports 60 hours/week but meets deadlines has no incentivize to change. 4 years later, everyone has quit and there's a mountain of tech debt. This becomes the next manager's problem, who is likely more clueless than his/her predecessor.