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.
“I got all the way to the end for an L6 EM role, and the must-pass round was a 200-plus-line code review in a Google Doc where I had to manually debug broken interval logic with no IDE and no tools.”
“In my binary tree round, I was not even leaning on BFS or DFS terminology, and they still liked my solution because I kept reasoning it out. That was the moment where Microsoft felt more about logical thinking than memorized interview patterns.”
“The recruiter told me comp was 'beyond competitive' and 'never a concern,' then immediately said they usually downlevel people by one or two levels. I'd never had any company say that out loud on the very first call.”
“My strongest Google round was with a senior interviewer who never opened a LeetCode prompt. He just asked what I knew about algorithms, pushed me into distributed merge sort from first principles, and apparently got more signal from that than a standard coding screen.”
“Not all interviewers may be able to adequately ask the right questions to go in depth, but they are absolutely looking for you to provide that depth by yourself. Your examples should not be surface level, but show you actually lived through the situation.”
“The most awkward part was they kept questioning my ability to analyze data, and I had actually initiated and been a big part of the migration from Microsoft to analyze data, so it felt really strange.”
“The interview is definitely hard, but achievable with preparation because the timing is very less. In the screening, you get five Python and five SQL in one hour, and you need to pass at least three SQL and three Python.”
“When they wrote that one column depends on another, I pretty much immediately jumped to cycle detection and modeled it as a graph. There was a lot of reading involved, but the solutions themselves were mostly brute force and straightforward.”
“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.”
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.”
