Live data from Hacker News

My Interviews with Amazon

thesocietea.org

201–210 of 270 posts

Re: My Interviews with Amazon

#201

Earlier quoted context omitted.

Maybe that problem only impacts productivity significantly when attrition is high (suggesting that the problem might be with talent retention and not engineering effort spent on interviewing)?

Perhaps Amazon has an attrition problem - at the company I'm talking about, it's just extremely rapid growth.

The attrition problem is well known.

Re: My Interviews with Amazon

#202
post #122
post #114

Earlier quoted context omitted.

I'm pretty sure I had to sign NDAs regarding coding questions before any interviews happened (not Amazon, a different company).

What are they going to do? Take you to court for vaguely describing a coding question?

The status quo is that the company whose questions you leaked will never hire you again in the future, and other tech companies who find out about this while researching you as a possible hire might also decide to never hire you.

It's the difference between a polite "this offer doesn't work for me at the moment", and burning your bridges.

(However, this particular article doesn't seem to discuss any specifics of technical questions, so I don't see an issue here)

Re: My Interviews with Amazon

#203
I had a couple phone screens with them for an AWS role in Palo Alto. They not only forgot to call me for both of them (we rescheduled both times), but my interviewers could not have come across as less interested had they tried. I went through some basic algorithms with them and asked questions about how they wanted to handle errors and edge cases only to be brushed off "do whatever" or "that's fine"--and not in the friendly "don't worry about that" sense, more with a "why are you wasting my time?" tone. I asked about what they worked on and was told either very basic details that I knew as a user or "I can't talk about that."

/shrug A week after the second screen, I got sent a form letter "no" from my recruiter, which was just fine by me. I've accepted an offer from a rival of theirs and I can't wait to kick their asses.

Re: My Interviews with Amazon

#204

Earlier quoted context omitted.

I applied to amazon last month, they asked me to do interviewstreet coding for 2 hrs. After that Recruiter didn't even have the minimum courtesy to let me know what happened. He simply stopped all communications with me. Reflects their attitude of treating ppl as mere 'resources' , I would work for amazon if I have no self-respect.

Ex Amazon here: that's not supposed to happen.

okay

Re: My Interviews with Amazon

#205

Earlier quoted context omitted.

When I've seen this with people interviewing in Amazon, it's generally because they're tagged to a higher level position, and during the interview, they decide they're not a fit at that level, but possibly at the one below it. i.e., he might have originally been interviewing for an SDEII position, but they felt his skill-set was closer to what they look for in an SDEI, but still wanted to make him an offer to join th…

The comments in the original blog post suggests a gap of 60k with the offer. Your comment makes sense only if he was interviewing for a Principal Engineer position or something, but instead was offered an SDE-I position. Plus I'm pretty sure very few (if any) non-Principal SDEs at Amazon actually get 200K in the first year.

Yes. If you can be promoted directly from SDE-I to SDE-II, there should not be a ~60K gap between. I've had the described thing happen (start interview by assuming level 3, but hire at level 2), and the gap is more like 20K. In other words: they should have known better.

Re: My Interviews with Amazon

#206
post #52

Earlier quoted context omitted.

Bezos set a mandate to HR a few years ago that he wanted them to be able to hire a new grad without ever needing to speak to a human engineer. That is, he wants the entire interview process automated (specifically for new grads, at least for now). What you experienced is part of their experiment in figuring out how to make this work. They've got a number of variations of interviews going on right now. I believe this…

> without ever needing to speak to a human engineer That would be one way to remove bias from the process. I've often thought college admissions should be done in a blind manner. Applications go to a subcommittee that removes all race/gender clues from it, then the scrubbed applications go to the admissions committee.

Although I understand the desire to scrub race from applications, if a candidate has overcome some form of discrimination, that isn't something we should necessarily just write off or actively ignore. Acknowledging the unfair treatment they may have received in life helps level the playing field.

Re: My Interviews with Amazon

#207

I'm gonna ignore the fact that this is for Amazon, which has its own criticism. Anybody who is baffled by the author's insistence on $170-200k but the offer of low 6 figures needs to read up on negotiation. I recommend the various videos/books/posts by Ramit Sethi that are specific to salary negotiation. If you give the number first, you lose. They will only negotiate downward from there. You can deflect in a million…

That is the traditional advice, but I'm not sure how true it is. You should read up on the anchoring principle. Basically, all negotiations revolve around the first number given, so it is often in your best interest to throw out a large number.

Re: My Interviews with Amazon

#208

I'm gonna ignore the fact that this is for Amazon, which has its own criticism. Anybody who is baffled by the author's insistence on $170-200k but the offer of low 6 figures needs to read up on negotiation. I recommend the various videos/books/posts by Ramit Sethi that are specific to salary negotiation. If you give the number first, you lose. They will only negotiate downward from there. You can deflect in a million…

[deleted]

Re: My Interviews with Amazon

#209
post #136

Earlier quoted context omitted.

Interestingly, I opened the Amazon door as a new dev and found something very different than what this post describes. The first step - before speaking to anyone about my background or interest - was going to be an intensive, one-hour coding session. It looked like it would be more "independent proof of competence" than "friendly programming task to evaluate you". I was expected to be on webcam the entire time to ver…

My webcam doesn't work in Linux; and you won't find me programming in Windows under ordinary conditions. I guess I can't work at amazon?

I've had a few rounds of interviews with different parts of their company. None of them ever involved a camera (with the exception of a 2-way video conference with someone in a different office, during an on-site interview).
Post reply on HN