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.
“> 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.”
“The process was pretty straightforward. Interviews were primarily focused on behavioural types of questions and my past work experience. I had a list of STAR stories prepared.”
“You need to focus on prep for a couple of weeks but if you do, the interview is pretty standard. In my case, it was a super day format. ”
“It was nice but very robotic. The question was same as reported be others before. I started with the verbal solution first and then code in google doc. ”
“The recruiter was great. The process went by quite quickly, and they were quite flexible with the scheduling. Overall, I'd say the interview process itself was not the most difficult, and definitely work through all of the materials that the recruiter shares with you beforehand. ”
“The process was pretty straightforward. However, the technical round was a frontend system design instead of a live coding round, which I was promised. I was caught off guard, but it worked out. For the finals, there were total of 5 rounds, 2 cultural and 3 technical. Two coding rounds among the technical rounds and an opinionated round where you discuss your opinions on different parts of engineering decisions, such as styling, state management, and so on.”
“The process was very precise. They are interviewing multiple students at the same college all at once and on the same day. You get feedback by the next day. Then you had to go in person to the offices for the final round interviews which takes 1 whole day”
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.”
