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 interview process moved very quickly overall, which I appreciated because it kept momentum high and reduced uncertainty between stages. Communication from the recruiting team was generally responsive, and scheduling was efficient despite the number of rounds involved.”
“The process felt extremely fast and kind of rushed. It went from a short call to being flown out the next day to an on-site interview. The interview itself was decent. They asked about the hardest problems I've solved, and the technical question was reasonably straightforward. Given the timeline and rush, I didn't really feel like I had the space to make a clear-headed decision. There was also a two-week trial period they told me about, where you need to prove yourself and also see if the intensity is something you want.”
“Coding round went fine. Need to get to a working solution fast before polishing or optimizing approach. For the system design need to cover both frontend and backend pieces. Focusing on just one piece might not help your case. ”
“The interview process was well-structured and fairly rigorous compared to others I’ve experienced. I appreciated that the recruiter clearly communicated expectations upfront, which helped me prepare in the right direction. The technical rounds were challenging but relevant to the role, and the interviewers were professional and engaging.”
“The process was relatively straightforward. The hiring manager was very conversational and introduced himself. It felt like we were just having a chat. I was an internal hire so I might have had it easier than someone who would have interviewed from outside.”
“Pretty tough, long, and drawn out.”
“The interview was highly rigorous but followed a format: four interviews and then five rounds of on-site. The preparation material provided by the recruiter did really help. It's always better to understand from the recruiter what is expected and then prepare accordingly.”
“It was a pretty standard interview. Didn’t have a single behavioral and everything was based on the technical, didn’t do perfectly, but still got the offer”
“It was as expected. SQL: First define the metrics and then code them Product sense: How do you measure the success of a product/feature type questions with follow-ups Probability and statistics with text book style problems and experimentation based questions ”
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.”
