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.
“The overall interview process was incredibly smooth, straightforward, and well-organized from start to finish. The recruiter was exceptionally friendly, responsive, and did a fantastic job of setting clear expectations for each stage. There weren't any significant downsides, as the scheduling was efficient and the communication remained consistent throughout.”
“I definitely had good preparation on LP question which is one of the most important area because company focuses on this a lot”
“My interview panel was for a specific team and not a general hiring pipeline. 3 rounds technical + behavioral. First 20 mins behavioral then technical. Last round was bar raiser. Everything went good for me, few questions were new like "experience with gen ai", rest everything was traditional LC + LP based behavioral.”
“The OA is quite long and has multiple parts. Other than the technical coding questions, there are behavioral questions based on the LP and work style simulation (choosing between email replies)”
“Overall, I’d rate the process as smooth and structured, with four rounds in total: two technical rounds focused on SQL and DSA, one system/design round, and one hiring manager discussion. The expectations were clear in advance, interviewers were punctual, and the questions were well aligned with the role. What went well was the depth and relevance of the SQL and design problems, which gave me a fair chance to showcase my experience with data pipelines and large-scale systems. What could have been better was more clarity on the evaluation criteria and faster post-interview communication, as the waiting period between rounds felt a bit long”
“The recruiter was quite helpful and shared details on the structure of the loops and how to prepare for it. The rounds in the loops were almost entirely behavioural focused on "Tell me about a time when" type of questions. There was probing for details as you walk through examples. Time was kept strictly in the discussions and you had to ensure you're able to control the cadence of the conversation.”
“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.”
“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”
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.”
