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.
“Both core rounds went okay-ish so far. The DSA round was strangely fixated on trees (weird) —the one topic I had not really prepared in-depth for Amazon—and was too focused on DP, strings, sliding window, LCS, and the type of stuff Amazon usually focuses on.”
“The questions weren't too difficult, and the interviewers were friendly enough.”
“The questions were concentrated to product sense and analytical thinking, but there were a lot of follow-up questions for each case.”
“OA was easy, interview was 2, 1 hour rounds with 30m behavioral and 30m technical. Asking mostly about how you use AI and technicals were typical LC style questions with one being a bit more vague”
“It went well and answered all questions. and did both leetcode questions asked one in each interview”
“Overall, I found the interview process to be quite long and demanding, but ultimately very fair. What went well was the thoroughness of the evaluation, which allowed me to showcase my skills while giving me a clear picture of the company's high standards. On the other hand, the multiple stages and assessments made the journey quite exhausting and lengthy. However, I understand that such a rigorous approach is necessary to ensure a great fit for both sides.”
“Good. Communication needs to be good and technically sound you need to be.Overall, the interview process was well structured and gave me a good opportunity to understand both the role and the team. I particularly enjoyed the technical discussions, as they were practical and allowed me to explain my thought process rather than just arrive at a final answer. The interviewers were engaging, and the conversations gave me a clearer picture of the kind of problems the team works on. What went well was the quality of the discussions and the opportunity to interact with people from different parts of the team. I also appreciated that the interviews covered both technical depth and broader problem-solving. The main area that could have been better was the scheduling and communication around the different stages. At times, there was some uncertainty around timelines and next steps. More visibility into the overall process and expected timelines would have made the experience smoother. Overall, though, I found the process positive and enjoyed meeting the team.”
“Preparation: I had a solid understanding of the role and prepared thoroughly with coding practice, system design concepts, and mock interviews. Confidence in Communication: I introduced myself clearly, asked clarifying questions when needed, and explained my thought process step by step. Problem-Solving Approach: Even when I didn’t immediately know the answer, I broke problems down logically, discussed possible approaches, and showed adaptability. Technical Strengths: I performed well in areas I had practiced extensively, such as data structures, algorithms, and SQL queries.”
“The interviewers were prepared, were all very nice except for one of them. I think by the last round during the onsite they probably made up their mind on not to hire me, I got the feeling. If they had decided that, I think it's better to not waster both their time and mine. ”
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.”
