The interviewer’s style was very different from others. Discussion started as follows -
- Tell me about yourself
- Tell me your best project from resume
- What did you do in this
- How is it different from any other similar project
- How did you assure code quality in your project
- How do you define code quality
- How did you test your code
- Did you write test cases for your code
- Write down test case for this code ( he gave a code )
He took each point very seriously, and did counter arguments for some of these.
- Then he asked me which app do I use for music.
- Lets design a database for an app.
- So I wrote a basic schema. He then picked up on the details. A bit of discussion.
- Then we moved to a specific table.
- Why is this table like this
- Do you think that app uses it like this
- Do you think its scalable
- What can you do to make it scalable
- What should you do to make it scalable
- Think about more use cases, develop a generic db structure which can accommodate some of future changes.
- A little discussion about development methodologies - ( plan a lot of use cases and then make database schema ) or ( deliver fast and re-iterate ).
Tip 1 : Stay calm under the pressure. It's okay to not know the correct solution to every question.
Top Amazon Software Developer interview questions & answers
Popular interview questions of Software Developer
Top HR questions asked in Amazon Software Developer
Reviews
Interviews
Salaries
Users/Month