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.
“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.”
“The interview process was challenging but very informative. The recruiter guided me well about preparation.”
“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.”
“OA: CCAT Phone: Rover VO: Life story: how to get into tech? What's your plan 1-2yrs? Have you looked at the link I sent you and what do you think about it? What do you think about 40% growth? Pair: Word guessing game (front end) Project deep dive: can use your own diagram or PPT ”
“The engineer was good, worked with you to solve the problem. I confused between LRU and LFU which I think was the major problem.”
“Both core rounds went okay-ish so far. The DSA round was strangely fixated on trees (weird) —the one topic I had not really prepared in-depth for Amazon—and was too focused on DP, strings, sliding window, LCS, and the type of stuff Amazon usually focuses on.”
“The interview consists of two parts: a 45 min LC style coding and 15 mins conversation on your prior projects. The 45 min question was to build an arithmetic evaluator. For that, you have to use the Shunting Yard algorithm. It was only "+", "-", "(" and ")". I'm not sure if we would have used more operators, maybe some with precedence, if I had gone further. I had a hard time understanding the interviewer. I learned later on from Chat that you should contact your recruiter immediately if this happens.”
“Ok! The interview quality was bad, they do not hire much, and their tech stack is not on par with the market. ”
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.”
