Amazon Software Engineer interview questions

I applied through a friend (which you should totally do if it's an option). I had 2 phone interviews which were pretty basic for the most part. One was dynamic programming and the second question just had to do with designing a DB. The second interview required no code. It was just a little bit of pseudo code and some OO questions. The main problem was keeping calm but if you practice problems a lot you should be able to get past these fairly easily. Then I was flown out to Seattle for several in-person interviews. I got an HR interview, 2 technical interviews (roughly the same difficulty of before but I was even more nervous), a lunch interview with the manager. I advise getting something easy to chew because you'll be talking the entire time. It can be very awkward if you're not prepared (which I really wasn't). Then I had 2 more technical interviews which I found to be easier because I was getting better feedback.

Applied online through as a new Graduate. They called and asked to set up an interview. First interview was lots of questions based on material like what are the 5 Principals of Object Oriented Programming. They ask lots of questions about your former work (if you only have school projects they ask you to talk about what you did). They will then ask you questions about those projects such as what programming designs you used (Singleton for example) and ask what characteristics that design has. The last 15 minutes of the interview is a programming question. My question was to write a method that sorts 2 Array's into one. You write this code quickly and tell them over the phone how you wrote it (including parentheses commas, ect). He asks you clarifying questions like if you wanted this to run faster how might you right it, and assuming we wanted duplicates how would you need to modify the code. The second interview was much more programming based. 20 minutes was general questions followed by a programming question which was done online on a website where both the interviewer and the interviewee could both see and work on the code. I forget what this code was but its a fairly simple method to write. At the end of the interview I was asked to write a method for StringToDouble in the next hour (following the end of the interview) and then to email it to the interviewer. This method had to include thorough error checking and a method to test various cases (invalid characters, double too large, ect).