The process took 1 day. I interviewed at Amazon (Bengaluru) in Jan 2011
Interview
I was surprised to see that written test is conducted for persons with more than 10years of experience...for those who applied for a manager position also.
the test consisted of descriptive type questions, asking to write programs, to write test scenarios etc.
Given the more experience, it will be obvious that we write more from a manager's perspective.
Not sure what they actually expected, but i was rejected in the written test. I doubt if they understood what all i have answered.
Overall, i feel they better have direct interview for senior employees, than conducting a meaning less written exam. Or the the answer sheet evaluators should be experienced enough to comprehend the information given at a high level.
Interview questions [1]
Question 1
Asking to write test scenarios for the "copying a file from one system to other using a wireless connection"
Process was relatively straight forward, I didn’t make it to the loop. What I can tell you is the recruiter will be overly excited about you as they are with all candidates. They’ll tell you, you can expect to hear back in two days for feedback. Truth is, if they reject you then you will not hear back within 2 days it will be more like a week. Silence means you aren’t getting the job, they’re very binary.
Interview questions [1]
Question 1
When did you make a choice no one asked you for? Why?
I applied through an employee referral. I interviewed at Amazon (Luxemburgo)
Interview
Good interview, reached the marathon loop of interviews. It was intense and quite focused on STAR stories obviously. Got some nice feedbacks as well to improve in case I managed to get another interview in a few months
Interview questions [1]
Question 1
How did you manage a conflicting situation with a peer ?
I applied through a recruiter. I interviewed at Amazon (Seattle, WA) in May 2026
Interview
a quick recruiter call and a 45-min phone screen with a PM that was surprisingly heavy on behavioral questions and metrics. also had to submit a 2-page writing sample (kind of like a mini PR/FAQ) before moving forward. the onsite was a 5 round loop: product strategy, execution, analytical, technical, and the notorious bar raiser round. the bar raiser is the absolute filter imo - they pick one project and drill incredibly deep to see if you actually owned the results or just coasted along. every single round is heavily anchored to their leadership principles (LPs). overall, it felt very intense and data-driven; it’s way less about brainstorming flashy features and more about how you ruthlessly prioritize, handle blockers, and dive deep into metrics. for prep, i focused on mapping my past projects to multiple LPs and practicing data teardowns. i did a mock on Prepfully w amazon PM specifically for the bar raiser round and that honestly saved me. it helped me catch a major blind spot -was staying way too high-level with my impact instead of clearly explaining the exact data points, technical constraints, and tradeoffs i owned end to end
Interview questions [1]
Question 1
Describe the time when you suggested a counterintuitive approach to a dilemma and how you realized it necessitated a new mindset.