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 two product cases I had was very out of the box and I was thrown off. The final product jam round on Uber Eats was rapid fire.”
“The interview process was well-structured and transparent, spanning an online test, two technical rounds, and an HR discussion. The interviewers were approachable and gave me time to think through problems rather than rushing me. I appreciated the logical progression from aptitude to coding to design concepts. What went well was the technical discussion — I was able to clearly explain my project work and core CS concepts. What could have gone better was my initial nervousness during the first technical round, which slowed me down on a question I actually knew well. Overall, it was a positive and fair experience. ”
“The interview went very well, the interviewers were very nice. They don't ask questions out of the scope, they were very helpful and supportive. The communication was key in taking the interview, there was an area I have been asked about, showing eagerness to learn was enough for the interviewer. But, of course, I had to show solid skills in other areas. I learned from this interview that it isn't over until it's over, do not give up mid interview, just carry on answering to the best of your ability.”
“The overall interview process was well-structured and organized. The interviewers were professional, friendly, and gave me sufficient time to think through problems and discuss my approach. I appreciated that the rounds covered a good mix of coding, design, and behavioral topics, allowing me to demonstrate both technical depth and problem-solving skills. What went well was the technical discussion around system design and real-world engineering challenges. The interviewers encouraged clarifying questions and were interested in understanding my thought process, trade-off analysis, and experience operating large-scale systems. The coding problems were relevant and allowed for meaningful follow-up discussions around optimization and scalability. One area that could have gone better was time management during some of the coding rounds. While I arrived at correct solutions, I spent more time than expected discussing edge cases and alternative approaches, which left less time for implementation refinements and testing. In hindsight, I could have balanced exploration and execution more effectively. Overall, it was a positive experience. The process felt fair, technically challenging, and reflective of the engineering problems one would encounter in the role. I also enjoyed interacting with the interviewers and learning more about the team's work and technical challenges.”
“Initially considered for IC6 but performed poorly in the system design so got down-leveled to IC5. For IC6 consider how your system interacts with other systems.”
“The whole process was smooth for me, prepared well from meta tagged leetcode questions and for system design hello interview was more than enough”
“The process was straightforward and moved pretty quickly. I had to download an external app to do the video-call interviews. The questions were standard product questions and the interviewers seemed to be going through the motions (i.e. not particularly prepped).”
“Coding focussed with focus on leetcode style problems. The design prompts are simple and abstract like design netflix or design instagram, etc. It is upto you to drive design discussion and this round decides leveling”
“Comparatively easy, but took a lot of time to complete the process. Keep your calm and you should be good.”
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.”
