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 was hard. Two medium leet code in 45 minutes and you're alright. System Design needs lots of practice and quick explanations.”
“The interview process was straightforward not focused on any particular tech stack mostly DSA and projects.”
“The process was tedious but having some patience helps. Ask questions first solve later. Understand what is being asked. ”
“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”
“The process felt extremely fast and kind of rushed. It went from a short call to being flown out the next day to an on-site interview. The interview itself was decent. They asked about the hardest problems I've solved, and the technical question was reasonably straightforward. Given the timeline and rush, I didn't really feel like I had the space to make a clear-headed decision. There was also a two-week trial period they told me about, where you need to prove yourself and also see if the intensity is something you want.”
“Coding round went fine. Need to get to a working solution fast before polishing or optimizing approach. For the system design need to cover both frontend and backend pieces. Focusing on just one piece might not help your case. ”
“The interview process was well-structured and fairly rigorous compared to others I’ve experienced. I appreciated that the recruiter clearly communicated expectations upfront, which helped me prepare in the right direction. The technical rounds were challenging but relevant to the role, and the interviewers were professional and engaging.”
“It was a pretty standard interview. Didn’t have a single behavioral and everything was based on the technical, didn’t do perfectly, but still got the offer”
“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.”
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.”
