I applied through a recruiter. The process took 2 weeks. I interviewed at Amazon
Interview
Got email from recruiter informing me that the hiring manager was very interested with my resume. Scheduled a phone interview with the hiring manager. Interview was pretty straight forward and included questions about my prior experience and Product Management knowledge.
Followed up another phone interview with a different Product Manager from a completely different team
Interview questions [1]
Question 1
Why do you want to move from software engineering to product management?
Pick and product that you like/dislike. Why? How would go about making it better?
Current roles and responsibilities.
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.