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.
“Pretty standard interview, technical part was more a talk through concepts than actual coding or system design. Discussed approach and trade offs. Behavioral bit talked about hardest project. Interviewer didn't pace too well, rambled quite a bit.”
“The process was very practical and not leetcodey at all, though knowing the fundamentals like different types of traversals, rate limiting primitives, scheduling policies did help. The interview process is a bit long, lots of wait between rounds but overall, it's smooth. ”
“Overall, the process was pretty smooth: application, online assessment, then two virtual interviews. The OA and coding rounds went well because the questions were standard DSA and I was comfortable explaining my approach and complexity. The behavioral portions also felt solid once I got into my STAR examples. The hardest part was handling follow-up questions and changing constraints in real time, especially when I had to rethink an approach while still communicating clearly.”
“The interview went smoothly overall. 1 round of phone screen followed by the full loop of 4 rounds packed in a day. 2 coding 1 behavior 1 system design.”
“Process was good. wish it was a bit quicker though it lasted a long time. try to get through final round as quick as possible since it takes a while afterwards to hear back”
“The process was well organized and the interviewers were collaborative. I did well when thinking aloud and adapting to new information. I could have managed time better during the unfamiliar-codebase round.”
“My case recruiter was unresponsive and they simply ignored me throughout the whole interview process and I still ghosted on the status.”
“The process was smooth, general interview skills, prepare well to discuss you solution before coding / jumping to the optimized solution”
“The “design a runtime system” problem felt quite broad and somewhat vague at the beginning. It wasn’t immediately clear what level of detail or which aspects of the runtime system the interviewer wanted me to focus on. A little more context around the expected scope, constraints, or key requirements would have made the problem easier to approach and helped keep the discussion more focused. ”
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.”
