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 most awkward part was they kept questioning my ability to analyze data, and I had actually initiated and been a big part of the migration from Microsoft to analyze data, so it felt really strange.”
“When they wrote that one column depends on another, I pretty much immediately jumped to cycle detection and modeled it as a graph. There was a lot of reading involved, but the solutions themselves were mostly brute force and straightforward.”
“Overall, the interview process was well-structured and gave me a good opportunity to demonstrate my problem-solving and programming skills. The interviewers were friendly, professional, and encouraged me to think through problems rather than simply focus on getting the final answer. What went well was the clarity of the problems and the collaborative nature of the discussions. I particularly appreciated being able to explain my approach, discuss trade-offs, and receive feedback or hints when appropriate. The process felt focused on understanding how I reasoned about problems rather than just evaluating whether I could produce a solution quickly. One area that could be improved is providing slightly more clarity around expectations for each stage of the process, particularly regarding the scope and format of the technical interviews. Overall, though, I had a positive experience and appreciated the time and effort the interviewers put into making the process fair and engaging.”
“The interviewer seemed nice and helpful. The first half will be about a system that I have owned and the second half is about System Design.”
“I have completed the first stage so far, the recruiter screen, so this covers that plus what she laid out about the rest of the loop. The screen was 25 minutes, audio only with camera off, and she said video is expected from the next round onward. What went well: she was unusually transparent. She walked through the entire process unprompted, both phases and all seven steps, and covered the full compensation structure without me asking, saying she wanted no surprises later. She also explained that Stripe runs a general product loop, so clearing the phase one interviews makes you eligible for any product opening, but you need a team match before you can enter phase two. What did not go as well was on my side. One of her questions had four parts and I answered only the first three. And she never asked whether I had questions, so there was no natural moment to ask about the role or the team. The full loop as she described it: recruiter screen, product sense interview with a PM, hiring manager interview, then phase two with a take-home assignment and three more interviews, then the hiring decision.”
“The process was more rigorous than anything I’d done at other big tech companies, but the recruiter was actually accurate and helpful on what to prepare. A few things caught me off guard: one round had the level of details and requirements for scalability.”
“The difficulty was not in the technical, but in the behavioral questions. It seemed like there was a hidden rubric beyond the basics of getting things done that were not necessarily apparent at first glance. Perhaps the role of the FDE is to take in social cues and have an instinct with human interaction that they're judging for here. It seems like they really deeply care about why you want to join the company and the team. It's not really something you can cosplay because they will drill you with different questions from multiple interviewers. I love Stripe as a product isn't going to suffice. Perhaps read their blogs and other online resources about the company culture. They seem to highly value people who work autonomously to scope, design, implement, and deploy solutions while also doing a bit of project management for the parts of projects that do require more resources.”
“Till now the process has been relatively easy if you prep well. Make sure to practice when to use which data structures, explain why you are using them.”
“By far the most technically challenging interview process I've ever had to do for new grad product management roles. Successive coding questions in a constrained time block.”
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.”
