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 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.”
“Process was very well made with good questions and open ended scenarios. Technical question was unexpected threat modelling. ”
“The overall interview process was straightforward and well organized. Communication was clear, and the interviewers were professional and respectful throughout. I had a positive experience overall, but I ultimately decided to move forward with a different offer that was a better fit for my current goals.”
“One of the interviewers showed up 30 min late to a 45 min interview and we ended up finishing around the same time anyways. ”
“The interview process was well structured and covered a good mix of DSA, ML theory, and ML system design. The problem-solving and technical discussions went well, and the questions were relevant to the role. I felt I could have prepared more thoroughly for some of the system design and deeper ML theory questions. ”
“Straight forward, easy behavior, one system design. Overall similar to how Amazon interviews. HM was bit tough, I couldn't read if she is interested or if she is forced to interview me. But Skip, and everyone else were super nice. ”
“There were 2 rounds. 1 30 min interview and one the final interview with 4 different people. They were all very friendly”
“It was very straightforward and wasn’t too bad, although it depends on the interviewer. For the intern roles, they aren’t expecting as much from the candidate and want to hear your thinking out loud. ”
“The overall interview process was well-structured and organized. The interviewers were professional, friendly, and gave me sufficient time to think through problems and discuss my approach. I appreciated that the rounds covered a good mix of coding, design, and behavioral topics, allowing me to demonstrate both technical depth and problem-solving skills. What went well was the technical discussion around system design and real-world engineering challenges. The interviewers encouraged clarifying questions and were interested in understanding my thought process, trade-off analysis, and experience operating large-scale systems. The coding problems were relevant and allowed for meaningful follow-up discussions around optimization and scalability. One area that could have gone better was time management during some of the coding rounds. While I arrived at correct solutions, I spent more time than expected discussing edge cases and alternative approaches, which left less time for implementation refinements and testing. In hindsight, I could have balanced exploration and execution more effectively. Overall, it was a positive experience. The process felt fair, technically challenging, and reflective of the engineering problems one would encounter in the role. I also enjoyed interacting with the interviewers and learning more about the team's work and technical challenges.”
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.”
