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.
“Had a recrutier screen followed by a phone interview which was sytem design. designed the systme well but was not enough to clear the interview”
“It went well it was clear on what to expect and the recruiters do prime you well from the start. They will let you know what to expect and prep required per stage. Usually there was enough time and you just need to think about it well rather than rushing to an answer.”
“Overall, the interview process was well-structured and professionally organized. It consisted of an initial phone screening, followed by a panel interview with the team lead and two senior members.”
“I thought it was very efficient. Within a few days I had my verbal offer and written letter. I interviewed with random people at Amazon so I never met the people on my team.”
“It was a same day interview process from start to finish - it was great experience overall to go in the morning and walk with offer at the end of the day. English proficiency was tested as well as part of separate round. ”
“The interview process was well structured and covered a good mix of DSA, ML theory, and ML system design. The problem-solving and technical discussions went well, and the questions were relevant to the role. I felt I could have prepared more thoroughly for some of the system design and deeper ML theory questions. ”
“The interview process was fast-paced and heavily practical. It consisted of an initial recruiter screening, a past project deep dive, a live technical case study focusing on customer scenarios, and a leadership/behavioral session. What went well was the technical depth—the interviewers gave constructive feedback in real time and let me talk through complex architectural trade-offs without unnecessary micromanagement. What didn't go as well was the time management during the open-ended case study; having to balance high-level client communication with granular technical scoping in a short time frame felt rushed.”
“The recruiter was very accurate on the whole process. The interviews are very structured. learn the frameworks for the questions and cases.”
“I interviewed for an Amazon Software Development Engineer internship in February 2025. The process was three rounds over about three weeks: a recruiter screen, a HackerRank assessment, and a final technical conversation that also included behavioral questions. The recruiter screen was straightforward and helpful for setting expectations. The HackerRank portion was the most time-sensitive part, so it rewarded being comfortable turning an approach into working code without spending too long on setup. The final interviewer was genuinely nice and the conversation felt collaborative. The coding problem was to reverse a linked list. I started by explaining the iterative solution and the pointer changes before coding, then walked through edge cases such as an empty list and a single-node list. The behavioral questions were folded into the same conversation, so I tried to make my answers concise and connect them to how I approach problem-solving and teamwork. Overall, it felt like a fair intern process: not designed to be tricky, but it did require clear communication and clean implementation under time pressure.”
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.”
