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.”
“still in progress but just leetcode prep. Studied some dsa and system design. Also dynamic programming helps.”
“The round was easy - I had to go over my current responsibilities and my work. I was asked a coding question as well so prepare DSA well”
“Overall positive experience – people very friendly and sharp. Mostly behavioral interviews, with deep dive on prior work. There was 1+ week of silence after final round. Think it was because the recruiter got reassigned. ”
“The process started with a recruiter reaching out on LinkedIn, followed by a 30-minute phone screen focused on my background, motivation, and logistics. It was conversational and low-pressure — the recruiter walked me through what the role involved and what the loop would look like, which helped me prepare. From there it moved to a hiring manager conversation and then a virtual loop covering behavioral questions, analytical skills (SQL, data visualization, requirements gathering), and a case-style discussion on turning data into business recommendations. What went well: The recruiter was personable, transparent, and responsive early on, and set clear expectations. The interviewers were engaged and the questions were fair — grounded in real business-analyst work rather than trick questions. The behavioral portion gave me room to show impact using concrete, quantified examples. What didn't go well: The pace between stages was uneven — there were noticeable gaps of silence (a couple of weeks at one point) with little proactive follow-up, which made it hard to gauge where I stood. Scheduling the loop took longer than expected, and communication was less consistent once it moved past the initial recruiter screen. A bit more visibility into timeline and next steps would have improved the experience.”
“The engineer was good, worked with you to solve the problem. I confused between LRU and LFU which I think was the major problem.”
“ The process was rigorous and well structured across screening and three rounds covering product thinking, AI experience, and technical depth with business strategy. Interviewers were highly conversational and went deep on my AI personalisation work at Amex, which I felt confident navigating. The case study in the final round was my weakest area — I took too long to land on sharp specific insights rather than leading with them. Overall a strong learning experience that pushed my product thinking significantly.”
“Directly applied on their portal, Recruiter reached out to me directly on LinkedIn as well and I got interviewed by Microsoft or a Senior Software engineer role in March end and here's the experience”
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.”
