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 started with a recruiter screening testing some behavioral questions and some technical questions she read from a question bank. Then, I did a coding interview online. Finally, a 4 rounds loop online (as opposed to my previous attempt when I did the loop in one of their London (UK) offices): 2 coding interviews, 1 system design, 1 behavioral with an engineering manager.”
“assessment went well, two medium LC questions, loop had 3 rounds, two rounds were medium LC, one round was CS fundamentals.”
“the interview process was very rigorous i did not know most of the things they asked , but i was confident in what i know , also they asked practices which are used in day to day industry not just basic coding ”
“The process was structured, thoughtful, and generally well run. The interviews felt focused on practical judgment, problem-solving, communication, and how I approach ambiguous technical and product situations. I appreciated that the conversations were substantive rather than purely checklist-based. What went well was that I felt able to draw on real examples from my past work, especially around leading technical projects, working with customers, and making tradeoffs under uncertainty. The interviewers were engaged and asked good follow-ups, which made the discussions feel collaborative. What was harder was that some parts required being very concise while still giving enough technical depth. In a few moments, I probably could have structured my answers more clearly upfront before going into details.”
“The interview process for the Full Stack Developer role consisted of a take-home assessment followed by a final interview round. The take-home focused on practical software development and gave me an opportunity to demonstrate my coding approach, problem-solving skills, and ability to structure a solution independently. The final interview covered a mix of computer science fundamentals, technical problem-solving, and questions about my previous development experience. We discussed topics such as data structures and algorithms, object-oriented programming, databases, APIs, and general software engineering concepts. There were also questions about projects I had worked on and the technical decisions I made. Overall, the process was fairly well structured and provided a good balance between practical coding and theoretical knowledge. The interviewers were professional, and the final round allowed me to explain my reasoning and discuss my experience in more depth.”
“Interview process was straightforward with standard components: Leetcode (2 rounds), System Design (2 rounds), Behavioural (1 round). Leetcode is of level Medium to Hard, with practice. You can probably do it.”
“It went really well, they were trying to confirm whether I actually solved the assessment on my own and understood my solution.”
“Overall, the interview process was well organized and structured. I appreciated the communication throughout the process and the opportunity to speak with different people from the team. The technical interviews were challenging but relevant and gave me a good understanding of the level expected at Google. One thing that could have gone better was the amount of time between some stages, as it made the process feel a bit longer than necessary. Overall, though, I had a positive experience and appreciated the professionalism and transparency of the interviewers. ”
“The process was very straightforward. In both technical rounds, I was asked questions from the top 50 Meta tagged LC questions list. Behavioral was also very standard.”
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.”
