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.
“I went in expecting the usual behavioral-first format, but in my loop they flipped it and opened with the coding question. The behavioral part still mattered, they just used the follow-ups to see if I actually knew my own work in detail.”
“What surprised me is how open ended the questions are, but each interviewer is very likely probing a specific Amazon leadership principle, so generic answers actually hurt you because you need to tease out what they’re really testing.”
“It was very Amazon style with leadership principles, but layered on top of that they kept asking how I’ve used AI to bring about innovation and change, and then they really challenged the metrics behind my stories.”
“Trust me, Amazon’s interview process has a different bar altogether, and for internal roles I’d stick with the AIQB because the interviewers are trained on that. You can even steer the interview by putting a hook in your answer so everything stays under your control.”
“I said I deep dived on an AI project, and they immediately started asking what parameters I used to train the model and why I switched from one LLM to another. Even the behavioral round got super technical.”
“This was an online phychometry test so not real depth tested. More of behavioral traits and you have to choose and say which of the 2 options you more closely associate with.”
“What went well: The technical evaluation was refreshingly practical and closely mirrored real-world software engineering rather than abstract competitive programming puzzles. The coding sessions focused heavily on clean code architecture, defensive programming, edge-case handling, and reasoning through system performance trade-offs. The interviewers actively engaged as collaborative peers, providing helpful hints when exploring complex design decisions. What didn’t go well: Time management during the system design/ML infrastructure round was tight. Spending too much time in the opening minutes clarifying deep architectural assumptions meant rushing through the observability, rate-limiting, and fault-tolerance sections near the end.”
“this was mostly about understanding your process and how u act in different situations and how well do u understand things ”
“The overall interview process was more rigorous than anything I had experienced at other large companies. The recruiter was clear, responsive, and helpful in explaining what to expect, which allowed me to prepare effectively. The interviewers were professional, and the questions gave me a good opportunity to demonstrate my experience through real examples. However, some questions felt repetitive across the different rounds, and a few follow-up questions were more detailed than I expected. Overall, it was a challenging but well-structured and positive experience.”
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.”
