Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
- 1,323 experiences
- 313 companies
- 37 roles
- +204 added this month
AmazonProduct Manager · L5“All three rounds were leadership-principles based, and the part they kept circling back to was basically, tell me about the ambiguous project and how you pushed stakeholders when nobody was aligned.”
AmazonAssociate Vendor Manager · L3“It started as an on-campus process, and then suddenly I was in Seattle at HQ doing a live exercise on expanding category assortment after all the leadership-principles interviews.”
AmazonSoftware Development Engineer 1 (SDE-1) · L3“They asked about compensation right on the recruiter call, and I basically kicked that can down the road until I got to the hiring manager. The live coding itself was pretty classic data structures and started with building a queue.”
AmazonSenior Product Manager (AWS) · L5“I went in expecting standard PM questions, and then the AWS team started asking me about API design down to the request and response and whether it should be GET or POST. That definitely caught me a little off guard.”
AmazonSDE II · L4“The OA was much more difficult than others I have experienced in the past. I would say it landed on the hard side of Leetcode questions. I'd focus more on graphs and layering other algoritms on top like binary search.”
AmazonSoftware Engineer · L3“Very heavy emphasis on behavioral, wasn't prepared as well as I should have been. Coding was easy if you've done Leetcode and basic system design and OOPS-oriented coding. For behavioral, make sure to have at least 6 distinct experiences to talk about with solid metrics, reusing stories looks bad.”
AmazonSoftware Engineer · L3“The process seems to be getting more rigorous than the past, with multiple technical rounds. There is a large focus on the leadership principles.”
AmazonTechnical Program Manager · L6“Rigorous. People reading the questions and taking notes - barely making eye contacts. Had a bar raiser - asked strategic questions. All indian team, everyone seemed overworked, stressed.”
AmazonSoftware Engineer · L5“In DSA it was focusing on Design DSA style problem, then i have HLD and LLD interviews. Design DSA: Implement Trie for recent searches usecase LLD: Bookmyshow style ticket booking system HLD: Design Link preview feature, similar to what's found in Slack or Whatsapp”
AmazonProduct Manager · L6“The Amazon PM-T interview was one of the more structured and rigorous interview processes I've experienced. The process typically includes an initial recruiter screening, a 60-minute phone interview with a hiring manager or senior leader, a written assessment, and a final loop of five interviews lasting approximately 55 minutes each. What went well: I appreciated that the interviews focused on actual work experience rather than purely hypothetical scenarios. This gave me opportunities to discuss complex projects, technical trade-offs, cross-functional leadership, and real business outcomes. Most interviewers were professional, well-prepared, and genuinely interested in understanding how I approached difficult problems. What didn't go well: The process was mentally exhausting, particularly because similar Leadership Principles sometimes appeared across multiple interviews. A single project could be examined from several different angles, making the conversations feel repetitive. Some interviewers were also very persistent with follow-up questions, leaving limited time for candidates to ask about the actual team or role. I would have appreciated more transparency around the team's current challenges, the expectations for the position, and how the different interview rounds were evaluated.”
Preview full access of other recent interview experiences
AnthropicSoftware Engineer, Safeguards · L5“The weirdest Anthropic round was the company values interview. It was almost like a therapy session, and honestly if you went to a therapist at some point, you will pass that round much more easily.”
NetflixEngineering Manager, Tooling“What was very unusual is they didn’t give me any tooling to draw the system design, so I just sketched it on a piece of paper and talked them through it, then we got into this oddly deep debate about whether hover-over history should count as a recommendation signal.”