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 completed four interview rounds, from the initial recruiter screen to the final System Design round. HR was very supportive throughout the process. The coding rounds consisted of one Medium LeetCode session and one scenario-based OOP coding session. I didn't pass the final System Design stage; feedback indicated they value design skills more than coding speed or syntax, noting that AI tools have made the implementation side of engineering much easier.”
“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.”
“I have 2 technical screens and the bar for EM for system designs is very high. The recruiter communication was very good. However the process took very long. ”
“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. ”
“It was more or less what I expected. ”
“I was first contacted by the recruiter for a buisness DS position and had a quick screen. They walked me through the several rounds and what is covered in each. Later on they even helped me go through feedback for each round. Had a total of about 5-6 rounds. The rounds were mostly case study and statistics oriented. Had very little ML depth questions. ”
“Hiring managers asked a lot of questions about Java internals, Java build system internals (Maven vs Gradle behaviors), networking internals (HTTP vs HTTP2)”
“MY DSA was top notch so no issues there, leadership principle questions are predictable so I answered thoroughly.”
“Overall went well. There were some technical questions which were asked but the interviewer assisted me to answer them.”
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.”
