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.
“Our interview process is straightforward: an initial conversation, a technical interview, and a final discussion focused on experience, communication, and problem-solving. What went well was keeping the process practical and giving candidates a chance to explain how they approach real problems. What didn’t go well was that some interviews took longer than expected, so we’re working to make the process more consistent and efficient.”
“The interview process was professional and well-structured, focusing heavily on real-world distributed systems challenges, which I found to be a great opportunity to showcase my skills. While the experience was positive, I struggled to align with the interviewers on certain technical nuances during our discussions, which ultimately led to my rejection.”
“The HR call was 30 mins. So a proper deep dive into candidate interests and suitability. It was quick and next round was scheduled immediately ”
“The process was pretty simple from the early start, but they emphasize a lot on matching Anduril's core values and see if you're a culture fit. I would have better prepared my stories and gaps for the behavioral interview. There were gaps regarding technical depth and being too ambiguous.”
“The interviewers were conversational, trying to understand the thought process. They were not stuck on right/wrong route but rationale behind the answer. ”
“Generally salesforce keep interviews in one two days hiring drive where each round eliminating.So i got the interview opportunity via referral so didnt gave OA but scheduled DSA round as very first round where 45 minutes and two medium to hard level questions should be done with almost optimised approach and time complexity explaination.”
“The process had a great focus on ML, which is to be expected. The hiring manager was quite knowledgeable and easy to talk to. The company seems to have had some pretty crazy stock fluctuation in the last few years, which I thought was kind of a red flag. Not sure if that is a sign of a healthy business.”
“The coding question was easy but the questions about debugging were very hard. Had to have production level knowledge to answer those.”
“Overall, the interview process was structured and covered a good mix of DSA, software engineering practices, system design, and behavioral/team-fit discussions. I went through five rounds, and the difficulty was reasonable but the questions were varied and required adapting quickly between problem-solving and design-oriented discussions. The DSA rounds went well, particularly because the problems tested both fundamentals and the ability to reason through domain-specific constraints. The system design round was the highlight for me. I enjoyed discussing the bottlenecks in the initial design, reasoning about the 50,000 RPS traffic spike and limited inventory, and iterating toward a scalable solution. The hiring manager round was also a good experience because it went beyond standard behavioral questions and involved a detailed discussion of my past work, architecture decisions, database migration considerations, and how I would use AI tools while solving engineering problems. One thing I found challenging was that the software engineering practices round was more DSA-focused than I had expected, so there was less emphasis on software design/practices than I had anticipated. Overall, though, the process was positive and I received encouraging feedback throughout.”
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.”
