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.
“My overall Amazon New Grad SDE interview process was rigorous and fairly challenging. I had three rounds covering coding, Leadership Principles, and low-level design. The coding questions were not just about getting to a solution, but also about understanding long problem statements, handling edge cases, and explaining my thought process clearly. What went well was that I was able to work through the problems, respond to hints, and connect my past experiences to Amazon’s Leadership Principles with specific examples. The LP discussions were also very detailed, with multiple follow-ups that pushed me to explain tradeoffs, ownership, business impact, and how I handled feedback. What did not go as smoothly was the scheduling and communication. All three interviews were initially planned for the same day, but the third round was rescheduled on the day itself and happened around 15 days later. I also was not introduced to the interviewers beforehand, and the process felt mostly automated, so it required a lot of independent preparation”
“Smooth process overall but did take a while after the final to hear back about the offer (over a month) potentially due to headcount being still figured out at the time. Questions were easy - medium LC questions.”
“Phone screen was an hour long followed by 5 member loop. I also had to do a presentation as well.The focus are on technical breadth, technical depth and then leadership principles like learn and be curious, disagree and commit, Bias for action, ownership”
“Process was quick, team was professional, and had a diverse set of interviews. Recommendation to split the loop into two days.”
“Interviewer were all really nice. Technical portion requires to be thorough in explaining thought process”
“The recruiter was exceptionally transparent and provided an accurate roadmap of what to expect. Their preparation tips were spot-on, which is a rare find in high-stakes tech recruiting. What didnt go well? The process was significantly more demanding than other major tech companies, leading to a bit of "interview fatigue" by the final stage.”
“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.”
“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.”
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.”
