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.
“Discussions about frontend fundamentals and my work experience went well. I was supposed to code the solution within 10 minutes after I had thought through the approach, but I took longer because I was supposed to solve the question in JS, while I primarily solve DSA questions in C++. ”
“What went well was that I was professional, and I’m pretty sure I communicated clearly. What didn’t go well was I wasn’t able to explain the impact.”
“I was given a PDF of questions related to the card game. I was asked to choose a language, I chose Python, and then I had to write complex Python logic to simulate the Card game amongst 4 players. The logic was not that hard; what was hard was that we had to write a lot of code in a very short amount of time. The interviewer was very helpful and asked me to correct my mistakes pretty early, which saved me some precious time.”
“The interview process was very fast. 4 rounds in almost one week. Their take-home assignment expressed that, given how much you were asked to complete in 3 days (PRD, GTM strategy, working prototype), they look for passion in the space and are quite technical and expect you to be. ”
“The recruiter mentioned that I will be heavily judged on my Communication as well as problem-solving. What went well: 1. I solved all the questions. 2. I was communicating very well. I wasn't able to pass the round because the interviewer wasn't helpful at all. I asked a question regarding an assumption to the third SQL question, and she said no. When I coded it and received the wrong answer, she said your assumption was wrong. Also, she said, "Don't tell me, you can solve it any way you want to solve." Her phone rang twice (I could sense she was using it, looking down). She was kind of rude, she ran my code while I was coding, causing confusion at my end. Yes, an interview is a collaborative exercise in DoorDash. She added something to my code even without telling me, leading it to fail, and consuming my time to debug.”
“So far so good. Yet to complete, so cannot answer this one fully, but the HR asked me what salary you are expecting, which was slightly off-putting. I did not want to give a figure and box myself. ”
“The interviewer seems pretty busy with his work, so the interview went straight into the question. It was fine, and he seems kind.”
“The process was more rigorous than anything I'd done at other big tech companies, but the recruiter was actually accurate and helpful on what to prepare, which is rare, and I really appreciated that. A few things caught me off guard: one round included a coding test unlike anything I’d seen before. They asked me to create a voice agent with sub-500ms latency.”
“The interviews are easy/medium difficulty for an experienced engineer. The first coding round includes Java-related questions before moving on to an easy LeetCode-style problem. There is no virtual onsite; candidates are required to go to the office in San Francisco, and there are four rounds in total. The interviews are very friendly and feature relatively easy-to-solve problems.”
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.”
