Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
Interviewed recently? Share your interview experience to unlock full access, or become a member.
“It didn't go as expected. I did not have as many interviews as expected, and overall, the process wasn't great as the recruiter changed midway.”
“I interviewed for an AI role so there was a clear focus on AI knowledge and experience throughout. Less focus on testing product skills but more on how comfortable I'm with designing a knowledge base, metrics, evals, trade-off's. It was more technical than I was prepared to answer”
“The process is a bit different than other companies. They are thorough and stress a lot of importance on the cases you will have to complete. The recruiter is very supportive throughout the process. ”
“While the process is relatively demanding, it can be completed rapidly, with a significant emphasis placed on cultural alignment and core values.”
“The process was recruiter call followed by technical screen. If one is successful, then virtual onsite - coding and system design/project depending on the team matched with. Recruiters are helpful and explain the process well and send the required material for preparation.”
“The process was quick with all interview rounds initially scheduled in the same week. The technical interviews were adapted to real world code implementations and didn't directly relate to Leetcode style problems. The system design round was very open-ended with no definite question and highly ambiguous requirements.”
“The overall interview process wasn't good. The employees I was supposed to initially interview with rescheduled. I ended up being interviewed by employees that were not familiar with the technical domain I work in. Phone screen was a typical Leetcode easy/medium question involving array manipulation and counters. Final round involved the typical behavioral questions and a leetcode medium graph question. Was given a use case to automate with CypressJS but the website design had changed so it wasn't even possible to do. Interviewer was clueless so we pivoted to something else. They were also rude and snarky as if it was my fault they were unprepared, obviously never attempted what they were asking, and were ignorant to the domain. Was ultimately ghosted and they never responded back. Probably for the better the way the Pinterest CEO is prioritizing the AI sloppification of Pinterest and laying off engineers. ”
“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.”
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.”
