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 interview process was fast-paced and heavily practical. It consisted of an initial recruiter screening, a past project deep dive, a live technical case study focusing on customer scenarios, and a leadership/behavioral session. What went well was the technical depth—the interviewers gave constructive feedback in real time and let me talk through complex architectural trade-offs without unnecessary micromanagement. What didn't go as well was the time management during the open-ended case study; having to balance high-level client communication with granular technical scoping in a short time frame felt rushed.”
“The recruiter was very accurate on the whole process. The interviews are very structured. learn the frameworks for the questions and cases.”
“The process was very straightforward. The recruiters are very good. Most of the questions you can find online for coding and they are relatively easy. For the design round, if you practice the ranking questions well, it should cover most of the questions”
“The process was overall good, recruiter provided lots of advice and pointers for what to study. The biggest challenege is the pressure and time crunch on making sure you can answer everything but maintaining accuracy.”
“Leetcode was doable based on the LC premium curated list, questions were similar. Culture round required thorough prep of examples for similar questions”
“The process was very nice, interviewed by people that would not be in my next team, but everybody was exceptionally nice. The questions in the ML system design round were not very deep and were more systems-oriented. ”
“My interview process started with a CodeSignal GCF online assessment that had four sections with increasing difficulty. The earlier sections were more straightforward and focused on implementation speed and correctness, while the later sections required more problem-solving depth and handling more complex constraints under time pressure. After that, I had a technical interview consisting of two LeetCode-style medium questions in a 45-minute session. The focus was on both arriving at efficient solutions and clearly communicating my thought process while working through each problem. What went well was my ability to understand the problems quickly and stay consistent across different difficulty levels. What didn’t go as well was pacing, especially in balancing correctness and optimization within the time limits. ”
“Practice leetcode fundamentals (graph, tree), practice system design fundamentals, speaking/thinking out loud, being able to explain full flow of what happens from when user/request is received to processed to returned (ensure components are disconnected/missing a flow path)”
“It went pretty well. The interviewers were very nice, so it was easy to talk through my behavioral stories without putting on a super professional act. Coding challenges were mostly medium leetcode questions.”
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.”
