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 process felt well-organized overall. The recruiter was responsive and scheduling was quick. The technical round was the toughest part — I felt slightly underprepared for the depth of follow-up questions. Communication after the final round was a bit slow.”
“The interviews were more of conversations where they stimulate you to think of an issue related to their business. Eg: Auth. People were nice and smart.”
“It went well. Recruiter's communication was clear and the interview was friendly, they emphasized willingness to learn more than anything.”
“Technical interview was enjoyable since it was less so rigorous LeetCode-style problems, and more practical coding to implement particular features. Prioritize a working solution over an unfinished, optimized code.”
“- everyone was super nice - questions were like leet code but with a twist - time complexity always asked”
“Not a lot of time, have to solve 2 questions in an hour. Needed to budget my time wisely and make sure I can get both questions done.”
“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.”
“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.”
