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.
“Two rounds total. First a 30-minute screen with the recruiter covering my background and salary expectations, then a 60-minute conversation with the hiring manager focused on my FP&A experience. What went well: the hiring manager asked concrete questions about work I'd actually done rather than abstract puzzles. What didn't: the role scope was described differently in the two rounds, and I had to ask twice to get clarity on reporting lines.”
“People are nice, questions are fair, but some questions might be niche. Had a hard time understanding the questions.”
“Overall it was fine, I think the final round left a sour taste in my mouth. It was supposed to be 4 interviews, 2 back to back and then the following the next day. I had 1 interview of the 2 during the day. Interviewer said it had to be rescheduled, then a couple hours later I received a note that said "As a result of the feedback you received, we are going to cancel your following interviews, ty. for interviewing with lyft"”
“The recruiter was very clear and prompt about the expectations and the reply time for emails was generally great. The technical interviews were all DSA and had a story built around the underlying question that the candidate has to uncover to get to the actual algorithm. The Googliness interview for me particularly was all 'how would you' questions instead of 'tell me about a time' questions, which surprised me a little and I probably did not do as well as I should have. Clarity of thought and conciseness in response is incredibly important for these interviews. For the onsites, both my interviewers were helpful and communicated really well. The second interviewer went really deep into the time and space complexity of Djikstra's, a couple layers below the standard answers and the follow-ups became increasingly complicated to answer. In hindsight, my overall interview loop focused on depth of DSA knowledge over doing all sorts of obscure medium and hard leetcode questions.”
“Overall, I had a positive interview experience with MoveWorks. The process was well-structured, and the interviewers were professional, friendly, and approachable. I appreciated that the discussions covered both technical depth and problem-solving approach, rather than focusing only on getting to the right answer.”
“Overall, the interview process was smooth and well-structured. The interviewers were friendly and gave me a good opportunity to explain my experience and approach to problem-solving. I felt the conversations were engaging, although a few questions were challenging and required me to think on my feet.”
“Process was relatively demanding considering the brand and type of work you would be doing. They require quick turn around, but then dragged their feet when it came to them to deliberate. After all was done, I felt like I was used for ideas and did not receive much value from interviewing with them.”
“What went well: The technical evaluation was refreshingly practical and closely mirrored real-world software engineering rather than abstract competitive programming puzzles. The coding sessions focused heavily on clean code architecture, defensive programming, edge-case handling, and reasoning through system performance trade-offs. The interviewers actively engaged as collaborative peers, providing helpful hints when exploring complex design decisions. What didn’t go well: Time management during the system design/ML infrastructure round was tight. Spending too much time in the opening minutes clarifying deep architectural assumptions meant rushing through the observability, rate-limiting, and fault-tolerance sections near the end.”
“Its good, but I was bad and dont really remember much. But all rounds was good. HR was nice. Tech guy on tech interview was nice too.”
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.”
