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.
“Both core rounds went okay-ish so far. The DSA round was strangely fixated on trees (weird) —the one topic I had not really prepared in-depth for Amazon—and was too focused on DP, strings, sliding window, LCS, and the type of stuff Amazon usually focuses on.”
“OA was easy, interview was 2, 1 hour rounds with 30m behavioral and 30m technical. Asking mostly about how you use AI and technicals were typical LC style questions with one being a bit more vague”
“It went well and answered all questions. and did both leetcode questions asked one in each interview”
“Overall, I found the interview process to be quite long and demanding, but ultimately very fair. What went well was the thoroughness of the evaluation, which allowed me to showcase my skills while giving me a clear picture of the company's high standards. On the other hand, the multiple stages and assessments made the journey quite exhausting and lengthy. However, I understand that such a rigorous approach is necessary to ensure a great fit for both sides.”
“Preparation: I had a solid understanding of the role and prepared thoroughly with coding practice, system design concepts, and mock interviews. Confidence in Communication: I introduced myself clearly, asked clarifying questions when needed, and explained my thought process step by step. Problem-Solving Approach: Even when I didn’t immediately know the answer, I broke problems down logically, discussed possible approaches, and showed adaptability. Technical Strengths: I performed well in areas I had practiced extensively, such as data structures, algorithms, and SQL queries.”
“1. Recruiter reached me out on LinkedIn 2. OA - you don't have to be perfect 3. Technical Screen (fail) 4. loop interview ”
“The overall interview process consisted of a recruiter screen, a technical call with the hiring manager, a written narrative exercise, and a 5-round virtual loop focusing on System Design, People Management, Operational Excellence, Cross-Functional Leadership, and a Bar Raiser round, with each module heavily testing Amazon’s Leadership Principles using the STAR method. What went well was my ability to deliver structured, data-driven answers that dedicated most of the time to my direct actions as a leader while anchoring results in concrete business metrics. I successfully demonstrated core Leadership Principles like Customer Obsession and Hire and Develop the Best through explicit examples of team growth, performance management, and architecture trade-offs, effectively balancing high-level business strategy with technical depth during system design discussions. What didn’t go as well was my initial tendency to credit the team using "we" instead of "I," which required interviewers to interrupt and probe for my specific individual contributions. Additionally, I mismanaged pacing in one round by spending too much backstory time setting up an operational failure scenario, which left little time for long-term preventative fixes, and I initially got bogged down optimizing a single database schema during system design rather than outlining the full end-to-end architecture first”
“I'm able to communicate while solving problem but unable to code the problem interviwers are very supportive and friendly they give hints when i stuck at last i was only able to provide pseudo code.”
“The OA was more challenging than I expected, the questions were more aligned with Competitive programming style. Recruiter was really supportive and informative. Still waiting on the next steps, which is the final round.”
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.”
