[thinkharderdev]

I interviewed with Amazon a few years back. The whole thing turned me off. A recruiter reached out and I was interested (it was late 2020 and the money was tempting). But before the first phone screen I had to have a call with the recruiter again, where she gave me a list of things I needed to "study" and was told that "successfully candidates usually spend 5-10 hours preparing for the interview". The study list was the usual list of CS101 topics. I didn't bother preparing and it was a good thing because on the phone screen the guy just asked me some a fairly mundane coding question and then some more general stuff (it was actually a very reasonable interview). Based on that they wanted to proceed to a final interview which was an all-day affair (on zoom of course because this was during the pandemic). But first I had to do ANOTHER 1h call with the recruiter where she gave me ANOTHER list of things I needed to "study" and reminded me that I should spend 5-10h preparing. That was too much for me and I politely declined the opportunity.

[gedy]

I refuse on principle any interviews that expect you to study or "prepare" for an interview. I'm sure I've missed out on some money, but they've also missed out on a pretty good engineer and teammate :-)

[bluGill]

You should prepare for an interview. However 5 hours seems like a lot and I question if CS101 is worth preparing for. (If I know you will ask about a red-black tree I can look it up - but like most engineers I never think about it because my standard library has it implemented for me - unless the job is implementing the standard library I would not expect you to ask that question)

You might be asked to write something like fizz-buzz in an interview - but the point is there isn't a good answer to that. (there are a few possible solutions, but all of them have something you should not like - which makes it a simple yet real world like problem and thus something you should be able to figure out in less than an hour without study)

What you should prepare is figure out how they interview and thus what questions they might ask. (nobody will tell you what questions will be asked, but they may tell you the style) Practice the answers. Practice stories of how you worked in the past so you can twist the story to answer the question (the above is how you should prepare for the STARS interview my company does). If you were in prison or something then be prepared to talk about why they should believe you are reformed, but most people don't have such a thing in their past that they should find.

[4ggr0]

every job process i went through so far has been applying -> if they like me a call with the usual job interview questions -> if both want to proceed a meet-and-greet with the actual team -> if both still are interested, sign a contract.

crazy how much time is wasted in US/VC tech.

[JustExAWS]

I am absolutely sure that the money you missed out on had a bigger affect on you than them missing out on hiring you.

Every large tech company or any tech company that pays decent money requires preparing for coding interviews *if you are trying to get hired as a developer*.

I personally didn’t do much prep for my Amazon loop accept practice answering behavioral questions in STAR format. But I also had to thread the needle of having experience to get into the Professional Services department as someone who knew cloud, how to talk to people, architecture and leading projects.

If I came out of college post 2012 instead of 1996 with path dependencies in 2012, you damn well better believe I would have been “grinding leetcode” to make BigTech money.

[bee_rider]

I think the idea is they want to inconvenience you to filter out people who aren’t desperate and willing to deal with their bullshit. But, expecting you to cram for an interview just makes it seem like they value metrics over actual merit.