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.
“Technical questions move fast, dont trip on edge cases. 2 questions in 60 min slot, with multiple followups. Code quickly. With 10 min of intro and questions theres not much time.”
“Interviewers were very helpful throughout. They expect you to communicate your thought process throughout”
“They give you a study guide. I'd recommend reading it. It's your classic data structure and algorithms interviews.”
“It was an extremely smooth process, though team matching was rough. Questions didn't need to be 100% right interestingly, as one of the rounds I didn't finish.”
“This was a really weird process. My expectation was to do DSA problems during the superday but they were asking a lot of questions about some of my projects and going over design decisions that I have made.”
“Everything went well. What didn't go well was that I had a location preference, and the interview did not like it. ”
“What went well: Structure up front, moving quickly despite holidays in between What didn't go well: After last interview didn't hear back for quite some time”
“Along the interview process, I think the recruiter reached out and she was very friendly. Things were smooth. I think I had multiple rounds and overall the interview process was great.”
“Intro and Most critically challanging past project (around 10-15 minutes) Design a configuration service which is responsible for updating configurations existing on n number of microservices existing in our architecture - High level System design discussion (arond 25-30 minutes)”
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.”
