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 AI enabled round was actually pretty unique. I used bit mask first, then hit a collision because the input had letters and numbers, and the LLM started hallucinating new functions, so I had to debug both the codebase and the AI.”

“I got feedback that I performed well on the coding interviews even when I did not feel like I performed up to a requisite level, so I think the bar has more flexibility than we may give ourselves credit for.”

“It was an internship role, AI engineer. First was an online coding round on arrays and strings where I had to return a palindromic subsequence, and later they asked dynamic programming and a linked list hard question.”

“I was definitely caught off guard because I was expecting more of a LeetCode type of question, and instead they showed a diagram about obstacles colliding and wanted me to figure out which one was bigger and where the force would move.”

“The culture fit round was so deep it was almost like therapy for me. I talked about pushing back on executive pressure to launch on a timeline and raising it up to chief counsel to make sure the data was correct.”

“They gave me a simulation where I had to imagine deploying a conversational AI model that reasoned across sensitive topics, and during internal testing it started giving overly confident but factually wrong answers in high risk contexts.”

“The weirdest part was the final round: they dropped me into a Google Colab notebook with maybe 20 to 30 lines of skeleton Python and asked me to debug an actual LLM inference step, but you were explicitly not allowed to use an LLM.”

“I had some serious issues in my demo, and 10 minutes later the COO called and basically said, “Yeah, that demo did not go well, but we think you can do the job, so why don’t you try again next week?””

“The coding plus ML stats round was the hardest by far. They basically asked me to implement an all_gather on noisy nodes, derive how many rounds you’d need for a target error, then figure out a better algorithm using the fact you’re transmitting floats.”
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.”