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.
“I’d never had to do vibe coding live before. In the product design interview, they gave me 10 to 15 minutes to actually build a rough prototype, and most of what they were probing on was how I prompted and reprompted the tool.”
“Google’s online assessment took me like 5 minutes and it was supposed to be 90, and that’s when I realized they really prioritize your interactions with the interviewer. You absolutely are not going to run any of your code, so if you don’t understand that landscape, you’re going to fail.”
“The process was smooth. First round was a mix of product solutioning and code evaluation. Recruiter screen was easy too , had to walk through the resume basically.”
“The interview was challenging and required me to think deeply about my product decisions and experiences. I enjoyed the level of detail and the directness of the conversation. I felt well prepared by the recruiting team, and the interview gave me a good opportunity to discuss real product problems and the reasoning behind my decisions.”
“The process on start is very easy ( online assessment , phone screen) but coding is very difficult - LEETCODE MEDIUM”
“Overall, the interview process went well. The questions were clear and gave me an opportunity to explain my skills, experience, and interest in the position. I felt comfortable communicating with the interviewer and appreciated the professional and respectful approach. One area that could have gone better was that I was a little nervous at the beginning, but I became more confident as the interview continued. Overall, it was a positive and useful experience. ”
“Overall, the interview process was well structured and the communication from the recruiting team was helpful. I appreciated receiving preparation materials in advance and having clarity on what to expect from the different interview stages. The technical interview was challenging and gave me an opportunity to demonstrate my problem-solving approach. I felt the discussion was engaging, although I would have benefited from having more clarity around the expectations for the specific problem and additional time to explore and optimize my initial solution. The Googleyness and Leadership portion allowed me to reflect on my experiences with collaboration, leadership, and working through ambiguity. Overall, I found the process valuable and appreciated the opportunity to learn from the experience. ”
“I only gave one SQL interview for an analyst role in strategy and operations. I did not go past that round. ”
“The process goes very quickly. At the beginning I introduce myself and the project expercinece. Then the interviewer gives a question of system design about LLM models, you must tell him all the steps and at the meantime he ask me some technical questions. After that also some troubleshooting questions.”
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.”
