Amazon Software Development Engineer interview questions

There was an initial phone screen that was almost entirely technical questions. There were two programming questions that I typed into a shared editor and a few more general questions about data structures and algorithms. The interviewer was a little disinterested. After the phone screen I was invited for a full day of 6 interviews. Since I had applied to two teams there were two manager interviews and 4 technical interviews. They really hammered me with behavioral questions ("Tell me about a time when..."). I could see this getting exhausting if I wasn't expecting it. I definitely recommend jotting down more than one example for each of the Amazon leadership principles. They didn't ask about them directly but most questions were probing in the direction of one or more. Even the technical interviewers ask these kinds of questions. They are definitely looking to see if I would fit in with the Amazon culture as much as whether I was technically qualified. Everyone was extremely nice and obviously competent making the experience much less stressful than it could have been. I got the offer the next day via a recruiter e-mail and phone call. Over the next couple weeks the hiring managers and recruiters kept in constant contact. I met with the managers again in a less formal setting. They were very approachable and honest and willing to answer any questions I had. I felt a little pressure, but they were professional and reasonably patient as long as I kept them in the loop.

One phone screen then four back to back 1:1 behavioural/coding interviews. Each interview (including the phone screen) basically follwed the format of behavioural question (or two) then one or two coding questions. The coding questions usually weren't inherently difficult but the interviewer would ask how it scaled, how you might test it and generally get you to talk about your solution. It seemed like implementing a non-optimal solution was OK as long as you were doing it for simplicity, you understood why it was non-optimal and could explain how you might improve your solution. One note is that they called me back with decision the next morning. I was impressed with the speed of this part of the process.