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 recruiter organized the flow well. My first round was 1 hour interview. When I qualified that round I was scheduled for the final round with 5 interview rounds scheduled on the same day. There was no delay from the recruiting team on informing the status and next steps through out the process. ”
“OA was extremely rigourous and took about 3-4hrs at a stretch. 2 coding ques 1) DP Hard 2) Springboot framelwork 6 errors. had to solve using AI assisted bot through a repository”
“The difficulty level was medium, interviewer was very interested in understanding the different approaches rather then looking on a particular solution”
“It was good experience overall Went well Recruiter really put efforts in prepping me for HM Didn’t go well HM round was not clear enough There were no direct LP questions asked so they gave another Screening round”
“The overall process looks structured as of now. My answers were structured but I think I should have asked for more time to think for the clarifying questions and to ideate the solutions. ”
“This was an online phychometry test so not real depth tested. More of behavioral traits and you have to choose and say which of the 2 options you more closely associate with.”
“Till now it went well. Let me see feedback. All the rounds were very much aligned to leadership principles. Prepare answers in STAR format and try not to tell any details where you have not worked in depth. ”
“What went well: The technical evaluation was refreshingly practical and closely mirrored real-world software engineering rather than abstract competitive programming puzzles. The coding sessions focused heavily on clean code architecture, defensive programming, edge-case handling, and reasoning through system performance trade-offs. The interviewers actively engaged as collaborative peers, providing helpful hints when exploring complex design decisions. What didn’t go well: Time management during the system design/ML infrastructure round was tight. Spending too much time in the opening minutes clarifying deep architectural assumptions meant rushing through the observability, rate-limiting, and fault-tolerance sections near the end.”
“this was mostly about understanding your process and how u act in different situations and how well do u understand things ”
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.”
