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.
“What stood out to me is that every loop round started with product sense, then I had to turn that answer into a data model, and from that they jumped straight into SQL and Python. One case was even an Instagram metric drop where I had to do root cause analysis live.”
“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.”
“The interview went well as I expected the questions where L2. They asked about project and challenges during the project and how i overcame those challenges while collaborating with teammates ”
“Technical screening wasn't that hard. Have to solve 3 SQL and 3 Python. You are fighting against the time.”
“Overall, the interview process was well organized and professional. The interviewers were engaged, respectful of time, and provided opportunities to discuss both technical and behavioral experiences. I appreciated the focus on real-world problem solving and the chance to explain my thought process rather than just provide answers. What went well was my ability to communicate my experience with data engineering, data warehousing, ETL pipelines, and large-scale data processing. I was also able to provide detailed examples from past projects and relate them to the requirements of the role. One area that could have gone better was managing time during some of the technical discussions. In a few cases, I spent more time than necessary exploring alternative approaches before arriving at the final solution. Looking back, I could have structured my responses more concisely and clarified assumptions earlier. Overall, the process was a valuable experience that helped me better understand the role, the team’s expectations, and the areas where I can continue to improve”
“The process was bizarre. During the recruiter call, they said the next interview will be behavioral. But it was pure technical. Asked lot of networking questions and system designs”
“The process was rigorous. SQL speed and precision is the key. In depth product sense, modelling concepts are needed.”
“Interviewer were all really nice. Technical portion requires to be thorough in explaining thought process”
“The process was overall good, recruiter provided lots of advice and pointers for what to study. The biggest challenege is the pressure and time crunch on making sure you can answer everything but maintaining accuracy.”
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.”
