I think given the role level here - much of what 'mattered' wasn't specifically asked. For example, these interviews were largely open ended - conversational actually. It was incumbent upon me to research and know who I was interviewing with, connect the role I was interviewing to - to their respective roles, and lead a discussion on how I could make a difference.
Questions relate to their Operating Principles like this one: tell me about a time when you operated at depth and used data to make a decision.
Based on a list of when buses entered & left for the day, design an algorithm for the bus depot manager to determine the resourcing requirements for tomorrow.
all of them were pretty focused on the leadership qualities. The only unexpected one was asking me a few times about a technology I had not experience with.
Design a similar website as Book my show
Asked to develop products/Apps
Some questions focused on technical architecture, but most were focused on management, particularly how I manage managers, and how I make my direct reports into better managers.
Tell me about a time... (must tie back to the leadership principles.)
What is the most difficult projects you have worked? How did you handle conflict there? What are the lessons learned and how can you ensure not to repeat that in future? Any questions you have about Amazon? How can you perform better?
How would you build out an empty warehouse for fulfillment operations--what are all the technical specs you would implement from beginning to end with only 4 walls. I was told to bear in mind that all the warehouses are different, there is no blueprint, roadmap or legacy information on how this is done because they move so quickly and there is little time to document processes.
Viewing 411 - 420 interview questions