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.
“There were a lot of probing questions that followed after each question. One good thing was that the hiring manager was pasting each question she asked on the chat, so that I could follow through.”
“The process was pretty rigorous, mainly because the bar at E6 felt more about scope and judgement than just solving the questions. Recruiter was clear and helpful. The coding rounds went ok, but I spent too long explaining some edge cases. Design was probably the strongest part, good back-and-forth and tradeoffs. Behavioral was fine, though I could’ve been more specific with impact numbers. Overall, a solid process but definitely tiring.”
“traditional interviews for MLE. coding rounds are AI-enabled meaning you can use claude or codex to write the code.”
“The role is a TPM under Alexa, but seems really like a project manager role- review privacy features. HM round was very basic, one PM loop asked a product design question, however the interviewer always cutting off the answer after 2-3 sentences; the most strange part was the tech lead round- a pure system design question which didn't mentioned in prep call at all. Wend very deep around 45 mins.”
“The interview lasted about four hours and was divided into several sections. One section focused on behavioral questions, where I was asked about my past experiences, how I handle different situations, and examples of teamwork, leadership, and problem-solving. Another section assessed my math skills through quantitative and analytical questions. The final section was technical and conceptual, testing my understanding of fundamental technical concepts, my reasoning process, and how I approached solving technical problems rather than simply recalling facts.”
“The process was very well structured with no surprises. They will let you know what exactly they are looking for and test you on that which I found nice.”
“Fairly standard interview process, recruiters are very helpful in giving general direction of how to prepare for each interview”
“Overall process is good, recruiter moves fast, interviewer is collaborative. The expectation for coding round is high - aim for optimal and bug-free solution. ”
“Overall, the interview went well, especially considering that it was my first real technical interview. I was able to answer most of the personal and technical questions confidently, and I explained my previous internship experience and my motivation for learning backend development. However, I found some parts challenging, especially the problem-solving question. I also felt a little nervous at the beginning, which made it harder to organize some of my answers. Looking back, I think I needed a little more time to prepare, especially for technical and problem-solving questions. Overall, it was a valuable experience, and I learned a lot from it.”
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.”
