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.
“HR is amazing. The first company in Australia I encountered that arrange a time for phone screen and confirmation beforehand but not random call candidates at any time.”
“Process was smooth. Interview details were shared beforehand and we were prompted to prepare a presentation/pitch”
“interviewer wasn't trying to get the perfect solution, but directed me to cover the most important bits by asking the right questions such as how to handle negative numbers ”
“Process was good and people were nice. I think it was rushed at times on back to back interview so better to break them. ”
“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”
“Went well, interviewers (panel of 3) were young engineers in their 20s. 5 technical questions basic GNC knowledge, 15-20 minute technical presentation on a topic and accomplishment of my choice, and also generic stuff like"tell me about yourself etc." ”
“The interview process was well-structured and included both technical and client interviews. The technical discussions focused on my experience with Power BI, data modeling, SQL, and real project scenarios. Overall, the interviewers were professional and gave me enough time to explain my approach. The only downside was that the feedback process took longer than expected, and communication between interview stages could have been more consistent.”
“Interview process went well. It was an internal job posting. Recruiter screen went well and then I spoke with the hiring manager. He then wanted to talk to my current manager at the time to ensure I would be a good fit. ”
“ The process was rigorous and well structured across screening and three rounds covering product thinking, AI experience, and technical depth with business strategy. Interviewers were highly conversational and went deep on my AI personalisation work at Amex, which I felt confident navigating. The case study in the final round was my weakest area — I took too long to land on sharp specific insights rather than leading with them. Overall a strong learning experience that pushed my product thinking significantly.”
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.”
