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.
“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”
“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.”
“A lot of focus spent in every round on LP questions. Make sure to have sufficient stories, sometimes they plan to ask two, but end up asking a third one.”
“The process wasn't too difficult. DSA/Leetcode wasn't heavily emphasized. It was a general programming type interview where you go through a code block and show your understanding of data structures”
“There is not that much interaction with a recruiter. I was lucky in the coding question was not hard but they have a bank essentially similar to leetcode mediums. The bar raiser round you should prepare stories for each one”
“The interview process was well-structured and focused on both coding and system/infrastructure knowledge. The interviewers were professional and gave me enough time to explain my thought process. I was ultimately rejected because my coding experience, particularly with data structures and algorithms, was not strong enough. In hindsight, I could have communicated my approach more clearly and solved the coding problems more efficiently. Compared to other interviews I've done, this one placed a stronger emphasis on coding fundamentals while also evaluating infrastructure concepts.”
“Too much bureaucratic process. Be prepared for ghosting. They expedite after onsites. Negotiation can take few rounds. Be patient, they do not throw away strong candidates.”
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.”
