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.
“One of the technical rounds was ridiculous, a LC hard (LC3548) ML Systems Design was pretty standard - design a recommender system Behavioral round fairly standard”
“I had an initial interview with a recruiter and then progressed to the first technical stage, which I didn’t pass. It involved an OOP-based task where I had to design a system similar to VS Code that tracks when function are opened and closed”
“It had 1 Phone screen with 2 leetcode style questions the loop had: 1 behavioral 2 leetcode style rounds 1 ml system design (with 1 more follow up)”
“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. ”
“The process was quite rigorous. I went through 7 rounds in total. The interviewers were experienced and helpful and dropped sufficient hints. The feedback was great but I felt like hiring bar was very high and nitpicky.”
“The process was very straightforward. The recruiters are very good. Most of the questions you can find online for coding and they are relatively easy. For the design round, if you practice the ranking questions well, it should cover most of the questions”
“The process was very nice, interviewed by people that would not be in my next team, but everybody was exceptionally nice. The questions in the ML system design round were not very deep and were more systems-oriented. ”
“The overall interview process was fairly structured. It started with a recruiter screening to discuss my background, experience, motivation for the role, and general logistics. This was followed by technical interviews that covered a combination of coding, machine learning fundamentals, and discussion of previous projects. There were also questions related to applying machine learning to Trust & Safety problems. What went well was the discussion around my previous machine learning work and how I approached real-world modeling problems. I also found the interviewers professional and the questions generally relevant to the role. The more challenging part was the coding portion, especially solving algorithmic problems under time pressure while also clearly explaining the approach and complexity.”
“Friendly interviewers, open ended questions. Wanted to go through the full arc of gathering data, figuring out sensors and deisgning the ML model”
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.”
