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.
“Pretty easy leetcode. The final round is just a few hours to implement an app. Not too difficult if you are comfortable creating an app.”
“All 3 rounds in loop were smooth, they are friendly and interviews went smoothly. I took entire loop in one go so it helped to be very much prepared.”
“It was okayish, however would have been better if I was better prepared for ML sys design fo NLP. I was good for CV projects and I filled out I want to go for CV but they gave me a NLP problem and was stumped there.”
“The interview was not too bad, two mediums and two hards. I just don't enjoy coding that much so it went downhill.”
“The recruiter screen was very basic, about experience and expectations. The coding part had two problems, one LC easy and another LC medium but also on the easier side. The system design is very similar to what you find on the first few problems on youtube.”
“My interview process started with a CodeSignal GCF online assessment that had four sections with increasing difficulty. The earlier sections were more straightforward and focused on implementation speed and correctness, while the later sections required more problem-solving depth and handling more complex constraints under time pressure. After that, I had a technical interview consisting of two LeetCode-style medium questions in a 45-minute session. The focus was on both arriving at efficient solutions and clearly communicating my thought process while working through each problem. What went well was my ability to understand the problems quickly and stay consistent across different difficulty levels. What didn’t go as well was pacing, especially in balancing correctness and optimization within the time limits. ”
“> My interview process with Temenos consisted of multiple rounds, including discussions on Core Java, Spring Boot, microservices, system design, databases, and my previous experience in banking and enterprise software projects. The interviewers were knowledgeable and focused on understanding both technical depth and problem-solving approach. What went well was the detailed discussion around real-world projects, architecture decisions, and domain experience. One challenging aspect was the depth of some technical and design questions, which required a strong understanding of system architecture and trade-offs. Overall, the process was professional, structured, and relevant to the role. ”
“Here's a short version suitable for Exponent: > The Oracle interview process consisted of a recruiter screening, two technical rounds, a system design discussion, and a managerial round. The technical interviews focused on Java, data structures, microservices, databases, and problem-solving. The system design round evaluated scalability, API design, and architectural trade-offs. Interviewers were professional and focused heavily on real-world experience and project discussions. Overall, the process was structured, challenging, and relevant to enterprise software development. ”
“It went good. Recruiter was polite and informative. Technical interviewers were helpful and engaging.”
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.”
