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.
“technicals were passable with some prep. for onsite, it helps to be familiar with more exotic forms of pipeline parallelism”
“The process was smooth. First round was a mix of product solutioning and code evaluation. Recruiter screen was easy too , had to walk through the resume basically.”
“The process was more rigorous than anything I’d done at other big tech companies, but the recruiter was actually accurate and helpful on what to prepare, which is rare and I really appreciated that. A few things caught me off guard: one round had a heavy focus on low-level system design and concurrency, which wasn't explicitly mentioned in the initial prep guide. What went well was the structure of the technical rounds they felt very practical and less like abstract LeetCode puzzles. The interviewers were engaged and gave good hints when I got stuck. What didn’t go well was my time management in the coding round; I spent too long optimizing a solution that was already passing the test cases, which left less time for the follow-up questions at the end. ”
“The screen was normal behavioral questions with the only technical one being how would I improve a product of my choosing.”
“I was referred by a friend in that Company. First had the call with the HR, which discussed the salary expectations, and experience, and tech stack, then first interview was scheduled, in that interview I was also asked to design the Cricbuzz like event streaming system, and basic questions about my projects, what is the work I've done in the sharding etc. in the second interview we went with the spring internals, and also to implement LRU Cache (logic edge cases, how it will work in multithreaded environment) Third round , on resume, and Design a HLD for a system that serves userQueries on the constant data and returns answer to queries, but the traffic is 1M users/sec.”
“Overall the interview process was smooth. A recruiter call to align on the work culture and talk about what the company does, and why you're interested in working there”
“The interview questions were quite unclear and I had to figure out what she is asking for. Also, she was asking really deep mechanical questions about the estimator I am using and my selection about the sample size. ”
“The interview was challenging and required me to think deeply about my product decisions and experiences. I enjoyed the level of detail and the directness of the conversation. I felt well prepared by the recruiting team, and the interview gave me a good opportunity to discuss real product problems and the reasoning behind my decisions.”
“Interviews is quite good, and interviewers kept it more conversational. Be more confident. Prepare the technical skills mentioned in your resume.”
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.”
