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 overall interview process was well organized and gave me a good opportunity to demonstrate both my technical skills and my experience with AI engineering. I felt that I did especially well when discussing Python, machine learning, LLMs, RAG, APIs, and how I approach debugging and solving technical problems. I was also comfortable explaining projects I had worked on and the decisions I made during development. The more challenging part was answering some of the deeper technical questions under time pressure. There were a few questions where I knew the concept but could have explained my thought process more clearly or provided a stronger example. Overall, though, the experience was positive and helped me identify a few technical areas I want to continue strengthening. ”

“I have completed the first stage so far, the recruiter screen, so this covers that plus what she laid out about the rest of the loop. The screen was 25 minutes, audio only with camera off, and she said video is expected from the next round onward. What went well: she was unusually transparent. She walked through the entire process unprompted, both phases and all seven steps, and covered the full compensation structure without me asking, saying she wanted no surprises later. She also explained that Stripe runs a general product loop, so clearing the phase one interviews makes you eligible for any product opening, but you need a team match before you can enter phase two. What did not go as well was on my side. One of her questions had four parts and I answered only the first three. And she never asked whether I had questions, so there was no natural moment to ask about the role or the team. The full loop as she described it: recruiter screen, product sense interview with a PM, hiring manager interview, then phase two with a take-home assignment and three more interviews, then the hiring decision.”

“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 overall interview process was well organized and gave me a good understanding of the role and team. The recruiter was communicative throughout and provided helpful guidance on what to expect. The interviews were challenging but fair, and I appreciated the opportunity to speak with people across different functions. Some questions required more detailed examples and quicker thinking than I expected, but overall it was a positive experience.”

“This was an online phychometry test so not real depth tested. More of behavioral traits and you have to choose and say which of the 2 options you more closely associate with.”

“the technical round was that difficult but the behavioral round would need more focus on, especially the star methods”

“My biggest issue was the machine learning round that I wasn't aware. I was told we would have a CodeSignal interview but it turned out to be a Google Collab interview. Had I known I was going to do some data analysis I would've brushed up on these skills.”

“Fairly straightforward process. Why did you leave your last job? Are you interested in this role? That kind of thing. Just double-checking fit. ”

“Process was rigorous but enjoyable. Recruiters were a joy to work with, although final onsite was tough.”
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.”
