Hadn't practised systems interview enough (designing event logging system for large facebook game) - ask lots of questions, research possible architectures and trade offs in large distributed systems in advance. Be comfortable with back-of-envelope size/bandwidth/latency type questions.
Why are you leaving Amazon? Why did you choose Amazon instead of IBM? Why did you not accepted IBM offer?
How would you handle a client reporting an issue with an API integration that "returned errors" on your end but "looked fine" on theirs?
Tell me about yourself. How you would troubleshoot something given a situation.
Experience and basic qualifications/skills. Very informal.
They asked me my experience, which is pretty normal for all people. They asked couple of opinion based questions, which is great rather than tradition x equals y questions which are meant to test knowledge, not the ability. They also asked about my background.
Do you have previous experience working in a virtual position.
If you could solve any problem in the world what you choose to solve and why?
They mainly asked about when id be available to start,
Was a simple string parse and calculate problem from a JSON
Viewing 561 - 570 interview questions