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 overall interview process went smoothly. My recruiter was friendly and communicative, and flexible with my schedule (I was traveling and had to split up my interviews). I received feedback relatively quickly after each round (within a few days - I often had to wait longer with other companies). No surprises, the recruiter clearly described the type of interview for each round.”
“Behavioral and Technical rounds were very friendly and relaxed. The last round was very intense and a technical deep dive into software engineering fundamentals like design patterns, code quality evaluation, etc.”
“The hiring manager provided an overview of the team's structure, mission, and the open PM role. I shared my background and drew relevant connections to the team's focus area. The conversation included a brief informal problem-solving discussion around product success metrics and go-to-market strategy for an open-source developer platform. The call concluded with alignment on next steps, including onsites. ”
“I had prepared well with product sense, and had a good understanding of how ML algo's work, that instilled a lot of confidence in me. Having a clear structure and a lot of clarification questions helped with articulating my thoughts.”
“The OA was more challenging than I expected, the questions were more aligned with Competitive programming style. Recruiter was really supportive and informative. Still waiting on the next steps, which is the final round.”
“In the phone screen the interviewer is very technical, supposedly should be AWS LP, behavioural and some technical questions. The interviewer says casual conversation but wants me to design the system but doesn't want me to draw diagram but keeps upgrading function or non-functional requirements and expects me to answer asap. And also as detailed as the formula for certain evaluation metrics.”
“Started with background discussion. Interviewer asked about a specific project i mentioned on the resume and dug into details. As for the coding challenge, I was given an existing package which contained an API for reading 4 bytes of data at a type from a file. To read 10 bytes, we had to call this underlying API 3 times to get 12 bytes, respond back with the requested 10 bytes, and keep the extra 2 bytes of data in memory for future calls. I solved this with a queue-based implementation, handling edge cases around reaching the end of the file. Got follow-up questions related to handling API call failures, retries, and streaming the output.”
“Some of the interviews are very formulaic. When they ask about management experience they first start by asking what is the largest org you've managed, and then all following questions are about that org. The largest org I had managed was at a bank which doesn't have the greatest parallels to draw from. If I had better understood the format I would have answered with the bank, but explicitly stated that it's not a good analogy lets talk about this slightly smaller org because it's closer to you guys. Instead, this conversation happened at the end.”
“Friendly recruiter screening (looking for good communication) and senior PM (mini-case). Mini-case was easy. Power day is ahead (final), and reportedly has much lower low pass rate. Calculators allowed, so evaluation is focused more on thinking and communication. ”
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.”
