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 recruiter was great. The process went by quite quickly, and they were quite flexible with the scheduling. Overall, I'd say the interview process itself was not the most difficult, and definitely work through all of the materials that the recruiter shares with you beforehand. ”

“The process was pretty straightforward. However, the technical round was a frontend system design instead of a live coding round, which I was promised. I was caught off guard, but it worked out. For the finals, there were total of 5 rounds, 2 cultural and 3 technical. Two coding rounds among the technical rounds and an opinionated round where you discuss your opinions on different parts of engineering decisions, such as styling, state management, and so on.”

“The process was very precise. They are interviewing multiple students at the same college all at once and on the same day. You get feedback by the next day. Then you had to go in person to the offices for the final round interviews which takes 1 whole day”

“I went through 5 rounds for a Senior PM role: a recruiter screen, a hiring manager call, then three virtual on-sites covering Product Sense, Analytical/Metrics, and Googleyness/Leadership, followed by a cross-functional interview with an engineering partner. The whole process took about 5 weeks from initial outreach to offer. What went well: The recruiter was communicative throughout and gave clear prep guidance before each round, which helped me calibrate expectations. The Product Sense interview felt collaborative — the interviewer built on my ideas rather than just grading me, and I appreciated that the analytical round used a real, de-identified product problem rather than an abstract puzzle. What didn't go well: Scheduling took longer than expected between the hiring manager call and the on-site loop (about 10 days), which created some uncertainty. I also found the case interview time pressure tight — 45 minutes wasn't quite enough to fully structure and solve the prompt, so I'd have appreciated a few extra minutes to synthesize a recommendation at the end.”

“My process started with a talent screen with the recruiter and quickly moved to a hiring manager interview. They then scheduled me for a full loop on a tight timeline as I was far along with another offer. I had 4 interviews in the full loop and after those 4 rounds I was notified by the recruiter that I'd passed and was going for review with a hiring committee, a week later I was told I was going to get the offer. ”

“Process was smooth but recruiter was very slow. Loop was only kept after 3 weeks of coding screening. Overall interview was centred around past project and spark optimisation”

“Went well, the interview process was pretty easy. If you do your research and study up you should have no problem”

“Pretty standard big tech intern interviews. One technical was on the medium/hard side. Interviewer seemed rather uninterested and just wanted to solution rather than any collaboration. The second was a more straight forward and easy problem with an interviewer that was more engaged and collaborative. ”

“Practice leetcode fundamentals (graph, tree), practice system design fundamentals, speaking/thinking out loud, being able to explain full flow of what happens from when user/request is received to processed to returned (ensure components are disconnected/missing a flow path)”
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.”
