Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
Interviewed recently? Share your experience to try it free, or become a member for full access.
“The so-called system design round totally threw me off. He was like, "let's code it out," and wanted me to build a file system with four use cases in 45 minutes, and then the recruiter just ghosted me for a month.”
“I thought I was walking into a normal product sense round, and instead she said, “Open your calendar and walk me through your week of college, then translate all of that to how you’d be a product manager.” I had to explain office hours, class projects, even how I ask professors for help, all on the spot.”
“It didn't go as expected. I did not have as many interviews as expected, and overall, the process wasn't great as the recruiter changed midway.”
“The process was quick with all interview rounds initially scheduled in the same week. The technical interviews were adapted to real world code implementations and didn't directly relate to Leetcode style problems. The system design round was very open-ended with no definite question and highly ambiguous requirements.”
“It was really interesting to me since Microsoft PM interviews are known to test heavily (sometimes only) on behavioural as opposed to PM frameworks. However, my experience was mostly PM frameworks with an AI twist on them, which tripped me up a little bit. ”
“The main technical and System design Interview was with the panel. It was a very long interview that took about 2 hours. All of the interviewers seemed very satisfied with my explanations and reasoning. I kept on engaging them during the session, my system design explanations were also very accurate, and pinpointed. I had another session, also about an hour long; he mostly focused on my previous projects and my overall experience in the market. During my second interview, that single interviewer (who was absent in the first one) kept on rehearsing that they needed someone with hands-on experience on Azure, which was very confusing for me, and maybe in the end, that became the reason for my being rejected.”
“The process was quick with all interview rounds initially scheduled in the same week. The technical interviews were adapted to real world code implementations and didn't directly relate to Leetcode style problems. The system design round was very open-ended with no definite question and highly ambiguous requirements.”
Preview full access of other recent interview experiences
“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.”
“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.”
