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.
“Practice leetcode fundamentals (graph, tree), practice system design fundamentals, speaking/thinking out loud, being able to explain full flow of what happens from when user/request is received to processed to returned (ensure components are disconnected/missing a flow path)”
“1 Phone Leetcode Onsite loop 1 LC, 1 SD, 1HR + 1 EM ( 30m each) Process seemed quite standard, the leetcode were all from top 50 tagged.”
“The process moved pretty fast, the onsite while intense interviewers were great and ready to help out.”
“It went pretty well. The interviewers were very nice, so it was easy to talk through my behavioral stories without putting on a super professional act. Coding challenges were mostly medium leetcode questions.”
“Interviews were surprisingly easy and seemed more vibes based. Nothing was ridiculously difficult or unfair. It was more of a "does this kid seem smart and genuine"”
“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 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.”
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.”
