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

“The process wasn’t as long as I expected. My onsite was supposed to be four rounds, but they cut it to just two, and one of them was a time-based key value store with delete at a specific timestamp given in the full spec up front.”

“There’s a new AI coding section I haven’t seen before. They still want to test my coding skill, so I first implement by myself, then use AI as a code reviewer for readability and missing test cases.”

“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.”

“By the time I got to OpenAI, I’d interviewed with 11 or 12 companies, so my behavioral was very well rehearsed. I kept openings in my answers so if they followed up, they’d go where I wanted them to go.”

“What stood out most was the interviewer straight up told me the culture at Scale is “pretty like 996,” which you usually never hear that openly. And the rounds were super speed focused, like two interval-style problems in one hour.”

“In the age of AI, I could feel the interviewer adding little follow-up questions just to make sure I actually understood the problem, because if you were using AI tools, there’d be a lag. Even clearing the onsite doesn’t mean you’ll find a team quickly.”

“I had done really poorly on the easy coding question, but I still got through to the next round, which was really surprising. Then in behavioral, the interviewer said, "that does not sound like a conflict," and I had to change my story on the spot.”

“The interview process was smooth, very fast, and they always kept me in the loop every step of the way. After the online test, I had multiple in-person rounds where I had to implement the development of a new API.”

“They literally moved my final to their hackathon and I ended up interviewing at 1:00 a.m. at the office. It was supposed to be collaborative, but instead I got dropped into this huge unfamiliar class and had to understand their code fast.”


