Live data from Hacker News

I took a job at Amazon, only to leave after 10 months

benadam.me

511–520 of 706 posts

Re: I took a job at Amazon, only to leave after 10 months

#511

Earlier quoted context omitted.

> I bag on Amazon a lot on here (which if I were to review with my therapist is likely because I had an absolutely HORRENDOUS experience in an interview loop with them my first step out of college that still makes me nervous in interviews, even 15 years later). Hey, I had a similar experience with Google! It was my first technical interview for my first job out of college. The interviewer laughed at my code, and then…

I had a similar experience in a college physics class. I was reviewing my solution to a problem (maybe angular momentum?) with the TA, and they said, “I know you got the right answer, but I don’t see how I can give you credit for this when I don’t understand your solution.” And I replied, “Is it even remotely possible I came up with the correct answer by chance?” They agreed not. “Then why should it be my problem tha…

Seems pretty reasonable to me.

Re: I took a job at Amazon, only to leave after 10 months

#513

Earlier quoted context omitted.

Now imagine if instead of coding exercises we had the interview process from other industries that weighs degree and past experience more heavily in the absence of any other sort of testing. What would it look like to break in then? Completing a BS in your spare time? EDIT: Most ideas I've seen about replacement for live coding - like take home projects or contract-to-hire - are not really any more friendly to people…

The craziest part of tech interviews for me is the way its just accepted that you do it this way regardless of how long someone has been in the industry. If companies were grilling people new to the career trying to figure out if they could FizzBuzz their way out of wet paper bag (I realize some can't) it would be one thing. Without a track record you don't have much to go on, but the fact that you can work in the in…

I don't think that FizzBuzz/similar gotcha-type questions like that are useful, especially since most of them are all over interview prep sites, so I don't use them. But I've definitely interviewed people with impressive-looking resumes who straightforwardly didn't seem to be able to code; they couldn't respond to simple questions ("You mentioned you used Language Y in this project; what do you like and dislike about that language?") or were clearly bullshitting their responses. I've felt insulted at times when I get FizzBuzz in an interview, but I kinda get it.

All that said, this is a systematic issue that gets blamed on individual interviewers when the blame should fall on the company. I'm a decade into my career, worked at companies of all sizes, and I've never had or heard of anyone getting trained in interviewing. Outside of informal efforts with coworkers, I've never had a job provide me with a rubric for what I should be interviewing for (shit, I usually find out I'm interviewing someone day-of or day-before). If companies gave a damn about interviewing, I think the process wouldn't be so slapdash, and fewer interviewers would fall back on crap like FizzBuzz.

Re: I took a job at Amazon, only to leave after 10 months

#514

Hey congrats on making it 10 months! "Urgent to not block progress, but also ironic that they are asking a person who has no clue what they are doing to deliver critical work" Friend of mine started a role there (this was 4-5 years ago) and was fired (sorry... more or less asked to leave, being told he could keep his signing bonus if he just left) within about six weeks because he wasn't immediately delivering on som…

> I bag on Amazon a lot on here (which if I were to review with my therapist is likely because I had an absolutely HORRENDOUS experience in an interview loop with them my first step out of college that still makes me nervous in interviews, even 15 years later). Hey, I had a similar experience with Google! It was my first technical interview for my first job out of college. The interviewer laughed at my code, and then…

This isn't a new interview style. I interviewed with Microsoft in 1997 and encountered the haughtiest person I've ever met.

Re: I took a job at Amazon, only to leave after 10 months

#515
post #273

Earlier quoted context omitted.

No. An interview process can be very selective without really requiring prep beyond studying up on the company somewhat--and maybe not really even that to the degree you're already familiar with the company. Not a developer (though was an engineer) but I've never studied for an interview beyond maybe spending an evening reading up on a company. But, to be honest, the (few) jobs I've had over the past 20 years or so h…

Some people use algorithms daily, or went to school for them, and don’t need to study for leetcode. Likewise, some people do architecture or frontend apps all day and don’t need to study for those . No matter what a company asks, some people will find it unreasonable, at the end of the day the charitable interpretation is that the company is choosing interview challenges that they feel are a proxy for the skills need…

You're assuming that a company has to interview all candidates the same way regardless of what job they're actually interviewing for. A frequent complaint, voiced all over this thread, is that interviewing like that makes no sense. If the job uses 100-level algos all the time, then sure, let's talk algos (also, kinda weird, but I'm sure there's something out there like this). But if you're bringing me in as an SRE and we spend a bunch of time on LC questions and much less time on my experience with AWS, Terraform, and CI/CD work, the interview is bad for me (because I don't work with low-level algos and probably won't know that stuff, _unless_ I've been grinding LC) and bad for you (because you don't have much signal about whether I can do the SRE stuff).

Re: I took a job at Amazon, only to leave after 10 months

#516
post #423

Earlier quoted context omitted.

> do you think google's making the world a better place? Silicon Valley, season 1 episode 1: "But most importantly we're making the world a better place. Through constructing elegant hierarchies for maximum code reuse and extensibility." Mike Judge is a genius.

> Mike Judge is a genius. He really is. Any one of his properties would prove that by itself. Having such keen insights into disparate facets of humanity tells me that he just gets humans on a level not many other people do. Hopefully that doesn’t sound too flowery and pretentious.

I think he nails satire and weirdness of humans well, similar to apatow, but I think he falls flat on the more emotional or positive aspects of humanity.

Not to say he’s not a master of his craft, and king of the hill especially had tender moments, but maybe that’s just not what he’s interested in

Re: I took a job at Amazon, only to leave after 10 months

#517
post #425

Earlier quoted context omitted.

> I bag on Amazon a lot on here (which if I were to review with my therapist is likely because I had an absolutely HORRENDOUS experience in an interview loop with them my first step out of college that still makes me nervous in interviews, even 15 years later). Hey, I had a similar experience with Google! It was my first technical interview for my first job out of college. The interviewer laughed at my code, and then…

Just in general this is extremely rude to do as an interviewer. I remember interviewing at Google a few years ago and the interviewer laughed at me when I asked her if they used Kotlin in the mobile app that they were hiring for. Kotlin was pretty standard at the time in most 3rd party apps and nowadays Google never shuts up about it in their dev talks, but back then I guess it was so unlikely that Google itself woul…

There are several reasons that might be funny. Assuming that funny question = stupid question is going to result in you being offended quite frequently. It's google, the interviewer probably thought it was funny because what you just asked would be logical, but because of insert crazy bureaucratic reason here they can't.

Most interviewers are nice people. Assuming good intent when they laugh is going to be the right assumption most of the time.

Re: I took a job at Amazon, only to leave after 10 months

#518

Earlier quoted context omitted.

The company who ordered people back to the floor when a hurricane was coming causing their death when the building partially collapsed, has people pissing in bottles to meet insane work quotas, stack ranks employees, flys drones over delivery trucks to surveil drivers to ensure efficiency, repeatedly busts union efforts, might run through literally every available American because the churn at it's distribution cente…

> The company who ordered people back to the floor when a hurricane was coming causing their death when the building partially collapsed Question about this specifically. Was it ever revealed if that order was to get people indoors to a reinforced building that happened to collapse? I remember SMS screenshots of a delivery driver who was killed, and to have sent him on the road would have been a death sentence.

If the rest of the parent's comment wasn't already true beforehand, then maybe we could assume good faith.

Re: I took a job at Amazon, only to leave after 10 months

#519

Ex-Amazon. Lasted 2 years. I'll just repeat the comment I posted the other day: There are only two instances when you're happy at Amazon - when you start and when you quit. Doing the latter was the best decision I made, perhaps, in my entire career. I can honestly tell that those RSUs and bonuses weren't worth it. Avoid at all costs. You've been warned.

[deleted]

Re: I took a job at Amazon, only to leave after 10 months

#520
post #461

Earlier quoted context omitted.

I’ve been doing technical interviews for decades and have gotten good feedback from candidates about my technique. I have a small number of questions that are nearly impossible to have prepared for - one for instance is finding the median in a large dataset using map reduce. The question is open enough there’s a lot of solutions that are expensive, a lot that are dead ends, and one that’s pretty clever. The key is I…

I’ve experienced interviews that could be described this way. Nearly impossible problems where the interviewer hints at the right (or preferred) solution and I’m stuck doing a guessing game that’s highly unrepresentative of real life software engineering (since no one in actual work drops hints while holding back their knowledge unless they’re jerks). It’s a terrible experience. I assume you do a much better job give…

I completely agree and see red flags in how the parent describes their interview technique.

Interview questions with one solution "that’s pretty clever" are IMO, bad. Even cliche "easy" fizzbuzz. Ok...so you know modulo.

Rationing out hints towards that "one weird trick" sounds slightly like a cat toying with a struggling mouse.

Post reply on HN