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 interview loop was definitely more AI/ML focused than software focused. There was no leetcode really, but I did have to write a simple KNN algorithm from scratch.”
“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.”
“Round 1: HackWithInfy Duration : 3 hours Format : 3 coding questions Easy to Medium Medium to Hard Hard I managed to solve: 60% of the test cases in Question 1 100% of the test cases in Question 3 Result: Shortlisted for the SP Role Interview Round 2: In-Person Interview at the Office Duration : ~1 hour 30 minutes Interview Flow : Self-introduction Discussion on the projects listed in my resume Reasons for choosing those projects Justification for the tech stacks used SQL: Join operations DSA: Question 1 (Medium) – Leetcode 54: Spiral Traversal (Explained the approach and wrote the pseudocode). DSA: Question 2 (Hard) – Leetcode 32: Longest Valid Parentheses (Started with the brute force approach and then gave the optimal solution). Puzzle – Pair of Socks (Was unable to give the correct answer on the first attempt, but later provided the correct solution with the interviewer's hint). Asked for feedback on areas of improvement Discussed relevant tech stacks to learn next I had mentioned in my resume that I teach DSA to my friends through online sessions. The interviewer appreciated this and encouraged me to continue.”
“Strong Domain & Cultural Alignment: Deep familiarity with Capital One’s data-driven decision culture, framework-oriented problem solving, and internal risk/analytics architecture made the conversation natural and fluid.”
“Less rigorous than other interview processes; ive heard some interviews at tiktok go up to 6 rounds but mine was only 3”
“focus more on business sense as compared to technical details (though equally important) the process was very fast”
“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).”
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.”
