Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
- 1,323 experiences
- 313 companies
- 37 roles
- +204 added this month
GoogleEngineering Manager · L6“Recruiter call and 1st round scheduled in March 2025 which was people management. Next round System Design and scheduled in March 2025. Cleared both and next round schedule in in May. which was again System Design. Post that code review round was scheduled in June and finally Googlyness in July. IN Augst got result that all rounds were positive, still waiting for team matching.”
GoogleSoftware Engineer · L3“Asked to code the pre order traversal of a tree. Later asked determine if pre order traversals of two trees are same or not.”
GoogleSolutions Architect · L3“If you are interviewing for a cloud role, reviewing topics from the PCA was helpful. That is the base, everything stems from there. ”
GoogleSoftware Engineer · L3“The process focused on data structures, algorithms, and problem-solving. The interviewers were professional, and I was able to explain my approach. I could have managed time better when optimizing solutions.”
GoogleSoftware Engineer“The process was tedious but having some patience helps. Ask questions first solve later. Understand what is being asked. ”
GoogleProduct Manager · L5“The interview process moved very quickly overall, which I appreciated because it kept momentum high and reduced uncertainty between stages. Communication from the recruiting team was generally responsive, and scheduling was efficient despite the number of rounds involved.”
GoogleTechnical Program Manager · L4“The recruiter was helpful. The team itself is focused on supporting data management initiatives. But the questions were not all related to it. One of the questions was to code a palindrome- coding is not something I have done for decades. I have handled massive initiatives, reporting out to CIO and CFO of a large telecom, I understand technology , but to expect coding - IMHO a bit much. ”
GoogleTechnical Program Manager · Intern“It was quite a lengthy process. The TAT was quite long and slow as well. Didn't receive a lot of feedback to prepare better for the next rounds, but overall was a great learning experience.”
GoogleSoftware Engineer · L3“The interview process was well-structured and focused on both coding and system/infrastructure knowledge. The interviewers were professional and gave me enough time to explain my thought process. I was ultimately rejected because my coding experience, particularly with data structures and algorithms, was not strong enough. In hindsight, I could have communicated my approach more clearly and solved the coding problems more efficiently. Compared to other interviews I've done, this one placed a stronger emphasis on coding fundamentals while also evaluating infrastructure concepts.”
GoogleData Scientist“Started off with recruiter screening with light technical questions, and walked me through all the rounds. Next, I had several rounds. Very light coding, mostly case studies and stats knowledge. Very theory/application focused.”
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.”