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.
“My interview process included a recruiter screen, technical coding interviews, and a final behavioral and problem-solving round. What went well was that the interviewers were clear, collaborative, and gave me opportunities to explain my thinking. I also felt strong when discussing tradeoffs and working through ambiguous problems. What did not go as well was my time management on one coding question—I spent too long refining my first approach instead of moving quickly to a working solution. Overall, the process was challenging but positive, and it helped me identify areas to improve.”
“The process was well organized and the interviewers were collaborative. I did well when thinking aloud and adapting to new information. I could have managed time better during the unfamiliar-codebase round.”
“Friendly recruiter, easy going but clearly wants to understand why you have applied for this position”
“Phone screen and first coding technical was easy, the hardest part for me was the SQL learning, I've never used SQL prior”
“Overall, the process was clear, well-structured, and moved at a great pace. What went well: The technical and case-study discussions felt very collaborative and directly relevant to the role. I appreciated that the interviewers asked targeted, high-level questions around data architecture, metrics frameworks, and product trade-offs, allowing me to showcase my quantitative background and practical analytics management experience naturally. What didn’t go well: On a couple of occasion-specific technical deep dives, I spent a bit too much time laying out preliminary context before getting to the core recommendation. Once I caught myself, I recalibrated to state my main thesis up front, but it was a good reminder to keep complex explanations even tighter under time constraints.”
“Technical interview was enjoyable since it was less so rigorous LeetCode-style problems, and more practical coding to implement particular features. Prioritize a working solution over an unfinished, optimized code.”
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.”
