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.
“Mostly behavioral. One round with Hiring manager, and another round with peer level team managers. Interviewers were required to take notes in a STAR format.”
“It was a straightforward interview process. I was contacted by the recruiter, had hiring manager, skip level / team screen and then an onsite meeting with cross functional team members. I didn't appreciate that there was miscommunication with the recruiter on which of the two roles that were open that I was interviewing for, and that ultimately cost me an offer because I prepared a deck for the wrong role. ”
“The overall process was spread across months making it challenging to keep up with constant preparation. I was able to ace the product design, analytics and execution questions. I could have done better in the cross functional round.”
“Overall experience was ok. The length of the interview was very long, and the recruiter sometimes would wait a couple of days before replying back ”
“The process was well-structured, starting with a recruiter screen followed by a deep dive with the hiring manager and a final "super day" involving cross-functional stakeholders (Engineering, Sales, and Supply Chain). What went well was the alignment on product vision; I was able to demonstrate how my technical background helps bridge the gap between complex chemical solutions and digital customer tools. What didn’t go well was the initial technical case study—it was more data-heavy than I anticipated, requiring a very quick pivot to explain how I’d prioritize features under tight regulatory constraints.”
“Overall, my interview experience was excellent. The recruiter promptly provided all the necessary details, clearly explained each stage of the interview loop, and outlined how the rating and hiring-decision processes work. The entire process was well-structured and transparent. I understood that I received three “Strong Hire” ratings and one “No Hire,” with the single negative rating determining the final outcome. This was difficult to understand because I felt that particular interview was one of my strongest. Also, there seemed to be a disconnect between the interviews and the rejection feedback. The interviews focused primarily on general skills, and I was not asked many detailed questions about the relevant domains. Nevertheless, the feedback cited a lack of domain expertise as a key concern. It would have been helpful if the interviews had explored domain knowledge more thoroughly, giving me a fair opportunity to demonstrate my experience in those areas. ”
“Recruiter was good at communicating throughout and the interviewers seemed really engaged in the process. Excitable about their space. There is a product design portion where, given a prompt and UX snippet, users are asked to design a solution to the prompt. You are given about 30 min and then are grilled on that. There’s a basic analysis portion ensuring you can read basic data and infer decisions. ”
“The process was more rigorous than anything I’d done at other big tech companies, but the recruiter was accurate and helpful in guiding preparation, which I really appreciated. A few things caught me off guard: one round had unexpected case-style questions that weren’t mentioned beforehand. Overall, the structure was fair, and the interviewers were professional, though the pacing felt a bit rushed at times.”
“Straight forward, easy behavior, one system design. Overall similar to how Amazon interviews. HM was bit tough, I couldn't read if she is interested or if she is forced to interview me. But Skip, and everyone else were super nice. ”
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.”
