A recruiter reached out the very next day after I applied for the job. The recruiter was prompt in her responses and did a great job coordinating the whole process.
The first step in the process was an interview with the Hiring Manager. They described what the team does and focused on my past experience with some behavioral questions. I was asked to dive deep on a recent project of mine.
The next step was a 1-hour phone screen with a senior engineer. This covered behavioral questions about past experience, followed by a live coding round (easy).
The last step was 4 rounds of virtual onsite interviews, each lasting 1 hour, with senior engineers and the senior manager of the team. The first three rounds focused on system design and behavioral questions. It seems SoFi really wants people who are good at system design to help build their products and scale them. I had the best experience though – the design questions were challenging but very enjoyable, fluid, and conversational. Interviewers were polite and really seemed to want you to succeed. The last interview of the day focused on live coding (medium difficulty) with a mix of behavioral questions.
Overall, I had a great interview experience and came away with a feeling of wanting to work with the engineers who interviewed me.
Project deep dive
Standard behavioral questions
System design (not the common ones usually found on the web, but this may vary based on the interviewer).
The following metrics were computed from 4 interview experiences for the SoFi Staff Software Engineer role in Seattle, Washington.
SoFi's interview process for their Staff Software Engineer roles in Seattle, Washington is very selective, failing most engineers who go through it.
Candidates reported having very negative feelings for SoFi's Staff Software Engineer interview process in Seattle, Washington.