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 overall interview process with SoFi was structured, professional, and gave me a good opportunity to learn more about the team, the role, and the company’s expectations. The process included a mix of technical and behavioral conversations, which helped evaluate both engineering depth and culture fit. What went well was that the interviewers were thoughtful, respectful, and engaged throughout the conversations. I appreciated that the discussions were practical and focused on real engineering problems, tradeoffs, collaboration, and impact. The culture-focused conversations also gave me a better sense of how SoFi operates and what they value in senior engineers. What could have gone better was the scheduling and pacing of the interview process. Some of the rounds were grouped closely together, which made it harder to prepare deeply for each area, especially for system design and project deep dive discussions. I also would have appreciated a bit more clarity upfront on what each round would focus on and how to best prepare. Overall, it was a positive and rigorous interview experience. The process gave me a strong impression of SoFi’s engineering culture, and I appreciated the opportunity to meet with the team and discuss both technical leadership and execution in depth.”
“The process was relatively straightforward. I don't think there were any questions there were misleading and everyone was nice and was professional.”
“It was amazing. Had lovely conversations and it was amazing. I got nervous towards the end and the panel understood hence was not rejected at last round”
“The main technical and System design Interview was with the panel. It was a very long interview that took about 2 hours. All of the interviewers seemed very satisfied with my explanations and reasoning. I kept on engaging them during the session, my system design explanations were also very accurate, and pinpointed. I had another session, also about an hour long; he mostly focused on my previous projects and my overall experience in the market. During my second interview, that single interviewer (who was absent in the first one) kept on rehearsing that they needed someone with hands-on experience on Azure, which was very confusing for me, and maybe in the end, that became the reason for my being rejected.”
“The round was with the hiring manager, she asked me alot of questions on churn, profit and lifetime value, which was the focus of the team. Others were basic ML questions like bias variance tradeoff, and project deepdive.”
“It was overall good experience. Except you have 4 rounds continuously. What went well? Asking them solid questions and being able to come up with a working solution. What didn’t go well? Not preparing enough for system design as a DevOps Engineer.”
“The process was different than most tech companies. There was no Leetcode or algorithmic questions. The questions were more open-ended and the emphasis was on writing clean and obviously correct code, as well as communicating effectively. The recruiter helped helped make sure the process went smoothly.”
“The interview process was straightforward not focused on any particular tech stack mostly DSA and projects.”
“It was good overall, and in order to clear any stage of the process, one need's have a solid understanding of SQL, Statistics, and Business Case studies. ”
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.”
