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.
“What went well: The live coding and system architecture rounds went smoothly. I was able to articulate my design choices clearly, especially around API design, database strategy, and maintaining high availability for microservices. What didn’t go well: The initial behavioral portion felt slightly rushed because we spent extra time discussing specific cross-functional project dynamics from my previous roles. How does this interview compare to other interviews you've done? It was significantly more interactive. Rather than giving static answers, the interviewers actively challenged my assumptions and asked "what if" scenarios, making the evaluation feel comprehensive and realistic to day-to-day work.”
“It didn't go as expected. I did not have as many interviews as expected, and overall, the process wasn't great as the recruiter changed midway.”
“The process was quick with all interview rounds initially scheduled in the same week. The technical interviews were adapted to real world code implementations and didn't directly relate to Leetcode style problems. The system design round was very open-ended with no definite question and highly ambiguous requirements.”
“Screen plus three loop rounds, all four back to back in one day. Coding problems were standard stuff, nothing exotic. What got me was that every single one had a follow-up that killed my first answer. Bounded the input range on the median problem, pushed hard on edge cases in the editor. If you only have one approach ready you'll stall. What went well: recruiter was clear about the format, no surprises on logistics. Rounds started on time. What didn't: I underestimated how draining four in a day is. By the calculator round I was slower than I should have been on something I've done plenty of times. The behavioral questions were also mixed into the coding rounds instead of getting their own slot, so I was context switching the whole time.”
“Though I hold good amount of working experience in building AI products from 0 to 1. However, I lack in explaining them in layman term.”
“The process is straight forward. Getting interviews as an external candidate is difficult. The interviewers are very friendly and accommodating. ”
“assessment went well, two medium LC questions, loop had 3 rounds, two rounds were medium LC, one round was CS fundamentals.”
“It was really interesting to me since Microsoft PM interviews are known to test heavily (sometimes only) on behavioural as opposed to PM frameworks. However, my experience was mostly PM frameworks with an AI twist on them, which tripped me up a little bit. ”
“The process was smooth, the interviewers were helpful. I messed implmenting LRU cache as I had never seen that question before.”
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.”
