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.
“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.”
“There were 2 interviews with a break of 30 minutes between them. Both the interviews were 45 mins long. The first interview was fairly easy, spent the first 20 minutes on behavioral questions and the next 20 on an easy Leetcode question-> Best time to buy and sell stocks. The second interview was quite difficult, it was about parsing a month's API data and outputting the peak API hours for each day given an operation”
“Interviewers put you under pressure. You have to quickly read provided code and try to make changes under some restrictions (only allowed to change certain components).”
“The interview process was good. The recruiter was very helpful. Mainly i focused on the design and debugging round. In debugging round there were test cases and a small piece of code. I had to debug the testcases which were failing”
“the technical round was that difficult but the behavioral round would need more focus on, especially the star methods”
“Fairly straightforward process. Why did you leave your last job? Are you interested in this role? That kind of thing. Just double-checking fit. ”
“Process was rigorous but enjoyable. Recruiters were a joy to work with, although final onsite was tough.”
“The recruiter was very clear and prompt about the expectations and the reply time for emails was generally great. The technical interviews were all DSA and had a story built around the underlying question that the candidate has to uncover to get to the actual algorithm. The Googliness interview for me particularly was all 'how would you' questions instead of 'tell me about a time' questions, which surprised me a little and I probably did not do as well as I should have. Clarity of thought and conciseness in response is incredibly important for these interviews. For the onsites, both my interviewers were helpful and communicated really well. The second interviewer went really deep into the time and space complexity of Djikstra's, a couple layers below the standard answers and the follow-ups became increasingly complicated to answer. In hindsight, my overall interview loop focused on depth of DSA knowledge over doing all sorts of obscure medium and hard leetcode questions.”
“Overall, I had a positive interview experience with MoveWorks. The process was well-structured, and the interviewers were professional, friendly, and approachable. I appreciated that the discussions covered both technical depth and problem-solving approach, rather than focusing only on getting to the right answer.”
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.”
