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.
“The interview process was very simple. Unlike other software companies there were little technical deep-dives. There were no coding rounds, however there were 2 system designs, 1 behavioral and 1 cross-functional round. Questions were nothing out of the ordinary. Interviews went very well that I landed an offer.”
“It was a good interview overall, I was just not prepared for it. Because it was a researcher role, i was first ask an my experience doing AI/ML research then we moved on to the technical problem, that I completely flunked because of nervousness and totally forgoing reviewing DS and Algorithms”
“The process was technically almost trivial. They focused a lot on your communication, and how you would work with clients less on pure technical skills. The 3 rounds were all pretty easy, outside of the initial conversation they all took 2+ hours each.”
“The interview started with a resume discussion and a system design round. There wasn't enough time left to fully code the LeetCode problem and dry-run the test cases. The interviewer didn't even switch on their camera, and it felt like they weren't very interested in conducting the interview.”
“The interview began with a brief self-introduction, followed by two questions: Most challenging project. What do you want to work on at Meta? The discussion lasted exactly 15 minutes. The interviewer did not interrupt at any point. Notification of passing the initial interview was received after an hour. ”
“it was super straightforward. some context: It was a frontend interview, I'm normally backend, so I needed more time to build it out. my familiarity wasn't super strong, but I presume that would be a straightforward screen for a FE SWE”
“My interview process was thorough and gave me a good sense of both the technical and operational expectations of the role. What went well was the opportunity to discuss large-scale program delivery, stakeholder management, and how I have led complex cross-functional initiatives. In my current and previous roles, I've managed programs involving technology teams, business stakeholders, risk partners, and vendors, so I was comfortable discussing governance, prioritization, execution planning, and driving outcomes across multiple groups. I also enjoyed discussing how AI can be applied to solve business problems rather than focusing solely on the technology itself. One area that challenged me was some of the deeper AI and machine learning discussions. While I have successfully led AI-enabled initiatives and proof-of-concepts, my strength is program leadership and business value realization rather than building ML models myself. There were a few moments where I had to think carefully about technical trade-offs and model-related considerations. However, I approached those questions by focusing on how I would partner with data scientists and engineers, ask the right questions, manage risks, and ensure alignment with business objectives. Overall, I felt the process validated my strengths in delivery leadership, stakeholder management, strategic planning, and operational execution. It also highlighted areas where I can continue strengthening my AI technical depth. I left the process with an even greater appreciation for the importance of combining strong program management with a practical understanding of AI capabilities and limitations.”
“The process was fairly quick. Recruiter gets back very fast. Good experience. All interviews completed within a week.”
“Went harsh and the interviewer was rude while asking the questions it was 45 mins but they extended it beyond 1 hr”
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.”
