Live data from Hacker News

Amazon Pip Horror Story

linkedin.com

51–60 of 771 posts

Re: Amazon Pip Horror Story

#51
post #9

>I submited 51k lines of code in January that is well beyond real.

Who tracks that?

IBM and Microsoft used to do that a little bit more than a decade ago. Not surprisingly it turnes out that counting LOC leads to shitty spaghettincode and copy paste all over the place and complete ignore of DRY principle

Re: Amazon Pip Horror Story

#52

People say that working for Amazon for a year is enough “training” to serve as a resume badge. However, I’d like to provide a counter to that: when I see Amazon on a resume, I actually discount the candidate. In my opinion, the branding has suffered tremendously and I view the candidate as a compensation maximizer beyond all costs- why else would you join Amazon despite the well known horror stories, as well as their…

I wouldn't be so quick to judge.

Big companies are actually like a conglomeration of small companies under an umbrella company. The culture is 20% upper management, 80% local management, and so your experience will differ greatly from department to department.

Bad managers exist in most companies. They can and do target people for personal reasons, and usually the targeted person doesn't have the protection or political clout to defend themselves, so they're killed off and life goes on.

I had a similar experience at Canonical of all places, which was a real drag because they were one of the few fully remote companies at the time, and I like the company.

Re: Amazon Pip Horror Story

#53
post #9

>I submited 51k lines of code in January that is well beyond real.

My first thought when I read that was yikes, that's a lot of bugs for the rest of the team to fix.

Unless this is generated boilerplate, it just isn't possible to create that much code, that quickly, and have it be correct.

Re: Amazon Pip Horror Story

#54
As much as I feel sorry for this person and their experience, it seems to me this wasn't the best way to handle this situation.

It would have been more pragmatic to fire up leetcode, take a few interviews, and leave the job professionally. This probably would have come with a small pay bump, even with this persons limited professional experience.

Maybe I'm just lucky and I've never had a bad experience like this, but I couldn't see myself posting something like this professionally.

Re: Amazon Pip Horror Story

#55

As much as I feel sorry for this person and their experience, it seems to me this wasn't the best way to handle this situation. It would have been more pragmatic to fire up leetcode, take a few interviews, and leave the job professionally. This probably would have come with a small pay bump, even with this persons limited professional experience. Maybe I'm just lucky and I've never had a bad experience like this, but…

100% agree. Everyone knows Amazon is toxic but I sure as hell wouldn't hire someone who posted this

Re: Amazon Pip Horror Story

#56

Earlier quoted context omitted.

The problem is that society doesn’t really stand behind whistleblowers. We claim to, but at the end of the day want someone else to do the standing behind them while we go back to our lives. And we don’t want whistleblowers around as we fear that we will be their next target. Whistleblowers, in their effort to restore trust, become automatically untrusted by large swaths of society. Naming makes you persona non grata…

There should be a way to name these people anonymously. Maybe drop the ass holes name on blind or make a "shitbosses.com" where we name these jackasses and vote. Heck I'll stand behind my words. If you ever apply to a company called Anduril. Watch out for a childish manager named Calvin Hareng. This MF: https://www.zoominfo.com/p/Calvin-Hareng/-1964480350 Anduril is hiring and if you're coming on board watch out if h…

We could create a developer filibuster. Create lists of terrible teams and tell people that they are good for interview practice, but little else.

Re: Amazon Pip Horror Story

#57

Why are people who do this never named? They should be named. This type of behavior perpetuates because despite this employee revealing a company issue.. the individual perpetrator can still hide behind anonymity. CALL these ass holes out.

See comments like these. Even this post is too much for some people.

https://news.ycombinator.com/item?id=30204121

Re: Amazon Pip Horror Story

#58

As much as I feel sorry for this person and their experience, it seems to me this wasn't the best way to handle this situation. It would have been more pragmatic to fire up leetcode, take a few interviews, and leave the job professionally. This probably would have come with a small pay bump, even with this persons limited professional experience. Maybe I'm just lucky and I've never had a bad experience like this, but…

100% agree. Everyone knows Amazon is toxic but I sure as hell wouldn't hire someone who posted this

100% disagree. I mean, working for some of the FAANGs is already a red flag of moral character, speaking up at least redeems them somewhat.

But seriously, I'd rather have a coworker that speaks up when they feel things are wrong. Nothing unprofessional about that.

Re: Amazon Pip Horror Story

#59
post #21

How it started - https://i.imgur.com/7Cyia1U.jpeg How it is going - https://archive.fo/pdYHy#selection-525.105-525.423

The second post in your second link is shocking too:

> One night, when I was a dev manager at Amazon, another dev manager in Seattle sent me a 20-page design document at 11:30 pm and told me that he wanted me to get him feedback by 5:30 am the next day.

How fucking rude is that? It’s indicative of an absolutely staggering level of toxicity.

Honestly, what a waste. Imagine how much better Amazon could be if they didn’t treat their staff like cattle.

Re: Amazon Pip Horror Story

#60
I feel for the guy—taking the post at face value, it sounds like he had a shitty team and a shitty manager. At the same time, this post does not make me want to hire him and in fact quite the opposite. He seems to be fairly junior, but even at that level I cringe at measuring ones self in terms of lines of code written (though lines of code deleted is a metric I can get behind).
Post reply on HN