Real Interview Experiences
Learn what to expect, directly from candidates and interviewers who've been through it.
Interviewed recently? Share your experience to help others prepare and unlock full access
“I’d never had to do vibe coding live before. In the product design interview, they gave me 10 to 15 minutes to actually build a rough prototype, and most of what they were probing on was how I prompted and reprompted the tool.”
“Google’s online assessment took me like 5 minutes and it was supposed to be 90, and that’s when I realized they really prioritize your interactions with the interviewer. You absolutely are not going to run any of your code, so if you don’t understand that landscape, you’re going to fail.”
“The main thing is that Anthropic had a very small question bank. When I was interviewing, I already knew the system design question, and the coding questions were like five of them, which was kind of wild.”
“I passed the interviews and it was verbally confirmed, but when the process was finished they decided they only want to hire in SF. Even though I was open to moving, they saw some immigration risks that they didn’t want to continue.”
“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.”
“I ended up pitching this quantum ML architecture where we were training models on quantum hardware to do something as stupidly simple as predict whether a number was even or odd, and Harvey’s panel got weirdly fascinated by the remote coding environment I built for physicists.”
“The internal tooling and the data is incredible. When I was there last year, they had their own Meta AI wired into the most commonly used databases, so I could reference tables and column names and just prompt it to give me the query I needed.”
“They gave me all the behavioral questions ahead of time, so I almost relaxed a little, and then more than half of every interview was just follow-up questions. It felt like they didn’t really care about the initial question itself.”
“They showed me this intentionally vague architecture with Kafka, Jupyter, and an experiment dashboard, and the whole prompt was basically just, "it’s slow." Then they pivoted to a custom system training LLMs across 500 nodes and kept drilling into failure modes and latency.”
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.”
