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 process was new as there was a repository question. This round was AI assisted so you need to use AI quite well.”
“It was well, interviewer was helpful and was asking mostly standard questions from leetcode. I prepared from Strivers A2Z sheet so it was enough. I could have explained my thinking better”
“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.”
“After the online assessment, I got three rounds of interview back to back in one day. The technical question is a simplified version of a hard LeetCode question. The interviewer did not ask me to optimize my answer to use tries, which I believe is the most efficient solution. Instead, I completed the brute force DFS / BFS solution only and the interviewer was satisfied. I was asked to explain my code in depth though, talking through how recursion works and how iterative variations are usually more efficient since it does not include the function call stack overhead. I was grilled hard in the behavioral interview, where I was asked multiple questions. From my experience, the interviewer expected each answer to hit multiple leadership principles.”
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.”
