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 process was straightforward, recruiter call followed by online assessment. Depending on the assessment, you are invited for a virtual on-site, with coding and system design. If you succeed, then there is a deep dive project round and finally behavioral. Interview is split into stages.”
“The process was pretty straight forward just know how to do leetcode very well. I messed up the intervals question in which i was to merge intervals but build a new list on it which i could not really comprehend ”
“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.”
“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”
“The interview process consisted of two technical rounds and lasted around 5.5 hours in total. The interview started with basic questions and gradually became more challenging. The interviewers focused heavily on problem-solving ability, C++ fundamentals, data structures, memory management, and operating system concepts. For coding questions, they often started with a straightforward version of a problem and then continuously modified constraints, expecting more optimized solutions. What went well was explaining my thought process, discussing trade-offs, and solving the initial versions of the problems. What didn't go well was some of the deeper follow-up discussions around low-level system concepts and advanced optimizations, where the interviewers kept pushing for further improvements.”
“2 HLD rounds, 1 LLD round, 1 HM round. Did well in all the technical rounds. HM round - I got rejected because the Hiring Manager thought my scalability experience was not upto the expectations.”
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.”
