Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
- 1,334 experiences
- 316 companies
- 37 roles
- +147 added this month
GoogleBusiness Analyst · L3“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”
GoogleSite Reliability Engineer · L3“It was smooth I had a python coding interview and then Googlyness questions which were based on projects I have worked so far”
GoogleForward Deployed Engineer · L4“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.”
GoogleAI Engineer · L5“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.”
GoogleSoftware Engineer · Intern“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.”
GoogleProgram Manager · L4“The overall interview process was smooth and well-organized, moving from the initial recruiter reach-out to the technical and behavioral rounds within three weeks. Communication throughout was prompt, and the interviewers provided clear context on what each stage would cover.”
GoogleSoftware Engineer · L3“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.”
GoogleSoftware Engineer“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”
GoogleTechnical Program Manager · L5“The recruiter round was for 30mins. Recruiter explained about the role and asked questions regarding my background”
GoogleProduct Manager · L6“The overall interview process consisted of four stages: an initial recruiter screen, two domain-specific technical rounds, and a final behavioral interview with the leadership team. What went well Communication from the recruiting team was proactive and transparent. Expectations for each round were clearly outlined in advance, and the interviewers were highly engaged. The case study round was a standout experience; it felt less like a rigid assessment and more like a collaborative whiteboard session, allowing for a genuine exchange of ideas and a clear view into the team's working dynamics. What didn’t go well There were noticeable scheduling bottlenecks between the technical rounds and the final leadership interview, stretching the total timeline by an unexpected two weeks. Additionally, during the technical presentation, the primary video conferencing platform experienced severe connectivity drops. This disrupted the flow of the discussion and required us to switch to an audio-only fallback, making it difficult to present visual data effectively.”
Preview full access of other recent interview experiences
AnthropicSoftware Engineer, Safeguards · L5“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.”
NetflixEngineering Manager, Tooling“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.”