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 pretty straightforward, no AI assisted programming, just needed basic fundamentals for the coding portion had have some STAR stories for the behavioral portion.”
“The process was pretty straight forward. The recruiter gave good guidance and gave a list of concepts to prep from. Pretty generic. ”
“The process was pretty straight forward just know how to do leetcode very well. I messed up the intervals question in which i was to merge intervals but build a new list on it which i could not really comprehend ”
“What went well: The live coding and system architecture rounds went smoothly. I was able to articulate my design choices clearly, especially around API design, database strategy, and maintaining high availability for microservices. What didn’t go well: The initial behavioral portion felt slightly rushed because we spent extra time discussing specific cross-functional project dynamics from my previous roles. How does this interview compare to other interviews you've done? It was significantly more interactive. Rather than giving static answers, the interviewers actively challenged my assumptions and asked "what if" scenarios, making the evaluation feel comprehensive and realistic to day-to-day work.”
“It was a very disciplined and clear process. Preparing for the behavioral questions took a long time. One of the interviewers decided to change the standard questions and the ones she created on the spot were very unclear. That made it difficult.”
“Overall, this was one of the more rigorous interview processes I've been through, but also one of the most organized. The recruiter was transparent about the interview stages, what each round would focus on, and even shared preparation resources ahead of time, which I really appreciated. Their guidance ended up being quite accurate, so I felt I knew what to expect at a high level. What went well was that every interviewer seemed genuinely interested in understanding how I think rather than just looking for the "right" answer. Most of the conversations felt collaborative, and when I explained my assumptions or reasoning, interviewers often engaged with them instead of immediately moving on. I also appreciated that several interviewers shared context about the team, their own work, and how the role contributes to the business, which made the conversations feel more balanced.”
“The recruiter was very nice and all the interview went very smoothly. I think I was rejected because some of my answer showed unexperienced.”
“The interview process was very simple. Unlike other software companies there were little technical deep-dives. There were no coding rounds, however there were 2 system designs, 1 behavioral and 1 cross-functional round. Questions were nothing out of the ordinary. Interviews went very well that I landed an offer.”
“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”
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.”
