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.
“Pretty good. Interviewer is friendly and the problem is medium difficulty. It's a great experience to visit google campus. ”
“Recruiter call was quite okay. It was just basic level of asking if I had certain experiences, very surface level of asking, then just preparing me for what the rounds are. Followed up with an email with a list of interview topics that may be tested. Subsequently, I had interview in the technical phone interview round. I managed to answer ~50% of the theoretical questions, but the remaining 50% were very hands-on and experienced based which I did not have enough of, like specific commands to run and troubleshoot when things gone wrong. Interviewer did not ask me to self-intro, nor ask about any of my expereinces at all. We just dove right in to the questions. Out of the 5 topics that were asked of me to prepare, only dove deep into 1 - Linux.”
“The process was tedious but having some patience helps. Ask questions first solve later. Understand what is being asked. ”
“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.”
“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.”
“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.”
“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.”
“The overall process was spread across months making it challenging to keep up with constant preparation. I was able to ace the product design, analytics and execution questions. I could have done better in the cross functional round.”
“What went well was my effort and organization. What didn't go well was time management. Next time, I would start earlier and ask for help sooner if I needed it. What stands out to me is how well this role matches my background and goals. The interview has also given me a good sense of a professional and supportive team culture.”
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.”
