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.
“Recruiter was extremely unclear about what the rounds would entail. Thought it went fine but was hard to prepare because there wasn't really any set structure.”
“Meta is still leetcode heavy and medium to hard questions should be expected. Since it's leetcode style interview you can predict the out come and also prepare easily. What didn't go well - For the second question couldn't walk-though the code with example due to time constraint. - I spent too much time explaining my approach for both problems. Overall keep your thoughts concise and finish the code first to quickly finish both questions.”
“Overall Experience was really good. What went well --> Could answer lld, hld problems well & could write code from AI as well. What didn't go well --> Wasn't prepared upto mark for Behavioral round which costed me offer”
“The interview process went well. The recruiter was very responsive and supportive throughout the process. Had a recruiter screening call and an HM call. I am pretty sure that the HM did not like my profile, or there was no fit for the role.”
“Firstly, I was contacted to book a recruiter interview, then got an automatic rejection. The recruiter reached out that it was by mistake and it went out automatically, an honest mistake but a bit stressful before an interview. The interviewer felt a bit confused about my experience, asking questions about things I've already outlined in detail in my resume, but again, it could be a formatting error on my end (even though I haven't had that issue with other interviewers with the same resume). The interview ended up being 80% asking about my previous company & how the team worked, which felt like I was repeating myself continuously. I also answered with the usual answers, but the interviewer would repeat the exact same question again. Overall, a weird interview, I ended it not knowing how much I actually talked about the role or my experience.”
“Discussions about frontend fundamentals and my work experience went well. I was supposed to code the solution within 10 minutes after I had thought through the approach, but I took longer because I was supposed to solve the question in JS, while I primarily solve DSA questions in C++. ”
“What went well was that I was professional, and I’m pretty sure I communicated clearly. What didn’t go well was I wasn’t able to explain the impact.”
“I was given a PDF of questions related to the card game. I was asked to choose a language, I chose Python, and then I had to write complex Python logic to simulate the Card game amongst 4 players. The logic was not that hard; what was hard was that we had to write a lot of code in a very short amount of time. The interviewer was very helpful and asked me to correct my mistakes pretty early, which saved me some precious time.”
“The interview process was very fast. 4 rounds in almost one week. Their take-home assignment expressed that, given how much you were asked to complete in 3 days (PRD, GTM strategy, working prototype), they look for passion in the space and are quite technical and expect you to be. ”
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.”
