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.
“I didn’t get much feedback on the panel interview round but I found it helpful that the hiring manager was also on the call. I had a prior interview with him and he seemed to like my background. I didn’t execute well enough on the presentation side in my opinion. ”
“Easy normal behavioral questions and case study round was also easy cover every topics possible dont rely on AI tools”
“The XFN behavioral interviews were pretty standard. The things that caught me off guard was 1) the app critique, because they just let me keep talking and using the app and I wasn't really sure what they were looking for 2) the technical system interview, because the interviewer went super deep, pushing me on latency constraints, how I would design algorithms, and defining technical architectures that I wasn't familiar with.”
“The interview process consisted of several stages: an initial recruiter screening, an online assessment, technical/product interviews, and a final round of behavioral interviews. The recruiter screen focused on my background, product experience, and motivation for applying to Meta. This was followed by an online assessment that tested my product thinking, analytical skills, and ability to structure solutions clearly. In the technical interviews, I was evaluated on product sense, execution, and analytical thinking. I was asked to design product features, define success metrics, and walk through how I would investigate changes in key performance indicators. These interviews emphasized structured thinking, user-centric design, and data-driven decision-making. The final stage included behavioral interviews, where I discussed past experiences, leadership, conflict resolution, and how I align with Meta’s values. There was a strong focus on collaboration, impact, and ownership. Overall, the process was rigorous but well-structured. It largely matched my expectations in terms of the focus on product design, metrics, and behavioral fit. The emphasis on clarity of thought and structured problem-solving was particularly consistent with what I had anticipated. ”
“The process is straight forward. Getting interviews as an external candidate is difficult. The interviewers are very friendly and accommodating. ”
“Poorly organized and no clarity from the hiring manager or the recruiter. I felt rushed and was not comfortable talking to someone who interrupts mid-sentence with their half-baked comments about the supply chain. ”
“It was well organized, and the teams took turns so as not to be redundant. It is helpful to go with data-backed examples like AI did for easy reference. While it is not always obvious, you can look up facts like who is the market leader in grocery or what's the number of customers /DAO for an app. It's not necessary to memorize all these Google-able numbers. I was asked a question about TikTok. I explained how I don't use apps that drain my time and focus, and they gave me a different question. ”
“The process was highly structured and intellectually demanding, spanning five distinct rounds that tested engineering fundamentals, product design, strategy, and leadership. It felt more rigorous than many standard big-tech interviews because it required a deep dive into Okta’s specific ecosystem, particularly the Okta Integration Network (OIN) and its technical nuances.”
“It was really interesting to me since Microsoft PM interviews are known to test heavily (sometimes only) on behavioural as opposed to PM frameworks. However, my experience was mostly PM frameworks with an AI twist on them, which tripped me up a little bit. ”
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.”
