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.
“It was a standard recruiter screem where the recruiter ask for your past experiences. They did mention to fill in impressive technical project statements (usally 1 to 3) and explain the next steps of the interview.”
“What did not go as well was that the interview covered a very broad range of technologies. Although I have a good overall understanding across these areas, there were some topics where I would have liked to provide deeper technical detail, especially when switching quickly between domains”
“Easy to interview. Recruiter + director were very nice but tech screen engineer was quite cold. Unique experience with the Ai coding round being the first one.”
“The recruiter screen is to check whether you can fit into the fast-paced environment of the company. The take-home project is not a trivial one, and the timeline is a bit tight to submit a proper solution on time. This is probably done on purpose, to see how you can manage tight deadlines.”
“Both rounds went well. I highly recommend reviewing previously asked questions for the company you are interviewing with. I was pleasantly surprised to find that I could solve both problems easily, as I had already practiced the similar questions on LeetCode”
“Interviews went smoothly. They expect you to be able to deeply unpack your responsibilities in your current/former roles and expect you to elaborate in great detail as well about how your organization functions, different teams interact with each other, etc.”
“The interview process in very well organised and it will take long to complete all rounds. You would be judged on your past work, your background and how well you present your self.”
“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. ”
“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.”
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.”
