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 process was straightforward, recruiter call followed by online assessment. Depending on the assessment, you are invited for a virtual on-site, with coding and system design. If you succeed, then there is a deep dive project round and finally behavioral. Interview is split into stages.”
“The process was smooth. The coding assessment(SQL) section needs serious preparation before any attempt. The case study section was as per expecations and followed the generic pattern.”
“It was a good interview overall, I was just not prepared for it. Because it was a researcher role, i was first ask an my experience doing AI/ML research then we moved on to the technical problem, that I completely flunked because of nervousness and totally forgoing reviewing DS and Algorithms”
“The process was fairly quick. Recruiter gets back very fast. Good experience. All interviews completed within a week.”
“The overall process was rigorous and comprehensive, more challenging than many interviews I have done with other large technology companies. However, the recruiter’s guidance was accurate and genuinely helpful, which I really appreciated. The interviewers were professional and respectful, and I felt the process was designed to evaluate both technical depth and practical problem-solving ability. What went well was that the process gave me opportunities to discuss my experience, research background, and approach to problem solving. What did not go as well was that a few questions caught me off guard, especially where I needed to connect fundamentals, implementation details, and communication under time pressure. Even though I was not able to answer every question as well as I wanted, the experience helped me understand which areas I should strengthen further.”
“The overall process was rigorous and comprehensive, more challenging than many interviews I have done with other large technology companies. However, the recruiter’s guidance was accurate and genuinely helpful, which I really appreciated. The interviewers were professional and respectful, and I felt the process was designed to evaluate both technical depth and practical problem-solving ability. What went well was that the process gave me opportunities to discuss my experience, research background, and approach to problem solving. What did not go as well was that a few questions caught me off guard, especially where I needed to connect fundamentals, implementation details, and communication under time pressure. Even though I was not able to answer every question as well as I wanted, the experience helped me understand which areas I should strengthen further.”
“Went well overall - The recruiter was really responsive and helpful. Everyone i talked to was really nice”
“It was a smooth experience and gave an overview at the phone interview round of what would be expected at the onsite interview. ”
“The interview process consisted of two technical rounds and lasted around 5.5 hours in total. The interview started with basic questions and gradually became more challenging. The interviewers focused heavily on problem-solving ability, C++ fundamentals, data structures, memory management, and operating system concepts. For coding questions, they often started with a straightforward version of a problem and then continuously modified constraints, expecting more optimized solutions. What went well was explaining my thought process, discussing trade-offs, and solving the initial versions of the problems. What didn't go well was some of the deeper follow-up discussions around low-level system concepts and advanced optimizations, where the interviewers kept pushing for further improvements.”
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.”
