Sofi Software Engineer Interview Guide

Candidates describe SoFi's software engineer interviews as varied, so prepare for both technical depth and people-focused conversations. Most accounts begin with a recruiter call, followed by a technical screen. Those screens differ: one candidate had two LeetCode mediums after already passing an online assessment, another a Karat session, another an hour-long DSA round with two staff engineers, and one a SQL session on CTEs and window functions. One candidate for a DevOps-leaning role instead shared their screen with the engineering lead to solve a basic Python web scraping problem.

For later rounds, one candidate reported an OOD round, a coding round, a system design round and a manager or behavioral round. Another had a LeetCode medium, a behavioral interview and a system design interview, then a final LeetCode hard round, with converting Roman numerals to integers as one example question. One candidate got a design prompt for a GIF sharing service. They were told SoFi sometimes uses an object-oriented design round, which in their case was replaced by an extra system design round. Another said the coding round focused on something different from what the schedule described, so ask what style of problem to expect.

Behavioral questions come up often. Candidates mention conflict with a manager, working with other engineering teams, cross-functional work, and knowing SoFi's values and why you want to join.

Round counts and logistics were inconsistent. Reports range from two rounds to seven in two days, and one candidate was moved to a different role before the onsite because the original had been filled. Confirm each round's format with your recruiter, and prepare clean data structures and algorithms, SQL, system design and a bank of collaboration stories.