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 process was tough. It was very very tough. Should have prepared earlier. Various type of python and sql questions were asked.”
“It was a pretty standard interview. Didn’t have a single behavioral and everything was based on the technical, didn’t do perfectly, but still got the offer”
“The process was technically rigorous and focused heavily on ML systems fundamentals rather than generic LeetCode-style interviewing. The conversations went deep into large-scale training, distributed systems, performance bottlenecks, and reasoning about how computation and communication interact across GPUs. I thought the strongest part of the process was that I could connect several questions back to practical GPU and systems work I had done before. The harder parts were questions that required quickly reasoning through unfamiliar distributed-training scenarios and communicating the tradeoffs clearly while working through them.”
“The overall process was pretty straightforward, and makes sense given its an internship. 2 interviews back to back and that's it for interns! Definitely not technically challenging, and they're gauging your thought process and unfamiliar environment skills moreso.”
“Practice. Technical python. You explain your thought process clearly, especially when walking through grid problems or autonomy architecture. You sound like an engineer who has actually built systems”
“Smooth process overall but did take a while after the final to hear back about the offer (over a month) potentially due to headcount being still figured out at the time. Questions were easy - medium LC questions.”
“I was interviewing for the UberSTAR sophomore internship, so the technical interview was easier than the regular SWE internship. I secured the offer and a return offer to be a regular SWE intern the following summer.”
“Interview was difficult, especially on the Beast team. It included IQ test, System design, coding a binary problem on blockchain, and behavioral, and going over a technical project i worked on. Each interview had to go really well or I wasn't gonna get the offer.”
“The technical rounds were generally well structured and covered both coding and system design. I performed well in most of the technical discussions, but I found the system design round more challenging. Overall, the process was professional and gave me a clear understanding of the technical expectations.”
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.”
