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 very rigorous but the recruiter was actually accurate and helpful about what to prepare, which is rare and I really appreciated that. The process consisted of a system design interview and a coding interview. The system design round focused on designing a payment processing system. The interviewer pushed beyond a basic design and spent a lot of time exploring failure modes, retries, idempotency, operational concerns, and correctness under real-world conditions. It felt closer to designing something that could actually run in production than many system design interviews I've done elsewhere. The coding round was also fairly challenging. The problem itself wasn't especially difficult from an algorithmic perspective, but it required careful handling of edge cases and a precise understanding of the requirements. I felt like there was less emphasis on LeetCode-style tricks and more emphasis on building a correct, production-quality solution. What went well was that the interviewers were engaged and clearly knowledgeable. The conversations felt collaborative rather than adversarial. What didn't go well, at least for me, was that I underestimated how much depth they expected around correctness and edge cases. In hindsight, I would have spent more time validating assumptions and thinking through failure scenarios before diving into implementation.”
“The process was short-lived for me, unfortunately. The coding interview was an hour long, and the question was similar to the game of life, but for an infection spreading across a 2D array. I approached it much too methodically - explaining my approach before implementing, like I've learned to do from past technical interviews. The thing about this one is that theres FIVE long parts, and you have to pass the test cases for each part before you move on to the next. If I could do it again I would be frantically coding from the very beginning - waste no time. Add print statements to debug. The interviewer doesn't help or guide much, its mostly on you.”
“The interview focused on my experience with Node.js backend development, including API design, database management, caching, and real-world project implementations. What went well was explaining my production experience and problem-solving approach; areas for improvement include providing more detailed answers on certain concepts and system design scenarios.”
“Coding, Data Structures & Algorithms These questions focus heavily on C/C++ mechanics, memory manipulation, and strings. "Implement an LRU cache with serialization and evolving constraints." "Design a simple hashmap without any STL." "Implement memcpy and memmove from scratch, first defining the difference between them, then writing the implementation." "Write functions to serialize and deserialize a list of strings." "Reverse a linked list." "Merge Intervals." "Given an integer array nums and an integer k, return true if nums has a subarray of at least two elements whose sum is a multiple of k."”
“The interview process was challenging but very informative. The recruiter guided me well about preparation.”
“The process is very technical, they care a lot about computer science fundamentals eg. how a dict works and how to deal with collisions. I wasn't prepared for these kind of questions so didn't answer as precisely as I could have. ”
“All the rounds went well except the final one, where I got stuck at a point which was implementing the percentage rollout feature and went blank, interview went downhill after that.”
“Wandered around of all DSA algorithms to come up with solution. Finally could land with BFS approach at the end with that couldn't complete the code and test. ”
“The process was well-structured — it started with a recruiter screen, followed by a technical phone interview, and then a virtual onsite with 4–5 rounds covering coding, system design, and behavioral questions. What went well was that the interviewers were communicative and the scheduling was smooth. What didn't go well was that the system design round felt rushed — there wasn't much time to go deep into trade-offs before moving to the next topic. Feedback after each round was limited, which made it hard to gauge where I stood.”
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.”
