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 straight-forward, I also felt sick the day before the phone interview and they rescheduled it without any problem. The phone interview was quite "flat", I talked almost the whole time both at the technical and behavioural round and the interviewers basically always only agreed with what I was saying. The on-site was really cool, offices are great and my 2 interviewers were really kind persons that made me feel very comfortable.”
“It was a mix of behavioral and hypthetical questions. The behaviroal part I was good at I think, but the hypothetical part it took me too long to answer and I was probably not confident enough, also some answer I gave was not clear and straightforward”
“It was smooth I had a python coding interview and then Googlyness questions which were based on projects I have worked so far”
“The interviewer gave me a very abstract description of a system, I needed to design, intentionally to let me clarify it through the questions. Most likely because role success depends on how critical it is for you to bother other people with bombarding questions. After all the questions, I clearly understood the system I needed to design, but time was almost up, so I did not have a chance to finish it as I wanted, but maybe someone else will.”
“Our interview process is straightforward: an initial conversation, a technical interview, and a final discussion focused on experience, communication, and problem-solving. What went well was keeping the process practical and giving candidates a chance to explain how they approach real problems. What didn’t go well was that some interviews took longer than expected, so we’re working to make the process more consistent and efficient.”
“Throughout the process, I thought out loud, trying to take the interviewer along with me at every single step. He seemed pretty satisfied with my answers. At the end, we discussed the role of an intern at Google and the different teams within the company.”
“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.”
“I gave a high level design, came up with requirements both functional and non functional, designed api's, data modeling etc. The feedback I got was that I did not do a deep dive on certain components”
“The recruiter round was for 30mins. Recruiter explained about the role and asked questions regarding my background”
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.”
