SoFi Software Engineer interview questions

34 Software Engineers have shared notes from their SoFi interviews, with the questions they were asked in each round. That is 87% of the 39 SoFi interview notes on Screna AI.

34 Software Engineer interview notes

SoFi·Software Engineer·Technical Phone Screen

Jun 2026
SoFi coding screen with a text-wrapping variant. Basically LeetCode 68 but without the justified padding, just greedy packing. Pretty straightforward if you've seen the original problem before.
  • Given an array of words and a max line width, group the words into lines greedily so each line fits within the width. No need to pad lines to a fixed length, just pack and return.

“Simpler than the classic justify-text problem since you skip all the padding logic.”

View Post

SoFi·Software Engineer·Technical Phone Screen

Jun 2026
Got a coding question at SoFi for a software engineering role that was essentially a graph traversal problem dressed up as a choose-your-own-adventure scenario. Pretty interesting framing, though the core of it was just DFS with memoization once you stripped away the story wrapper.
  • Given a choose-your-own-adventure graph structure with choice nodes, option edges, and a set of ending nodes, find all endings reachable from the start node by traversing every possible single path through the graph.

“The story framing threw me off for longer than I'd like to admit.”

View Post

SoFi·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at SoFi for a software engineer role. Just the one question about delegation and ownership, which sounds easy until you're actually sitting there trying to remember a story that doesn't make you look like a control freak.
  • Tell me about a time you collaborated with teammates by handing off part of the work to them. How did you decide what to delegate, how did you support them, and what came out of it?

“I had a decent story ready but I fumbled the middle part about how I actually supported the person after handing things off.”

View Post

SoFi·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at SoFi for a software engineer role. The whole thing revolved around one architecture diagram and what could go wrong with it. Pretty focused interview, not a lot of fluff.
  • Given a system diagram showing the flow from a web application through DNS, a load balancer, your service, a database, and an external API, what potential failure points or issues do you see?

“This is the kind of question that looks easy until you start talking and realize you're just listing buzzwords.”

View Post

SoFi·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at SoFi for a software engineer role, basically one question about a project you cared about. Pretty low-key but you need to have a real answer ready.
  • Walk me through a project you found genuinely interesting. What drew you to it, what was your specific role and contribution, and what did you take away from the experience?

“I had an answer prepared but it felt a little rehearsed coming out.”

View Post

SoFi·Software Engineer·Technical Phone Screen

May 2026
SoFi software engineer interview where the main focus was a deep resume walkthrough. They weren't just skimming, they wanted specifics: numbers, timelines, why you picked one approach over another.
  • Walk me through your resume, and for one or two projects, go deep on the technical details including the problem context, your specific contributions versus the team's, the design choices you made, the trade-offs involved, and the outcome.

“This is the kind of question that sounds easy until they start poking.”

View Post

SoFi·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at SoFi for a software engineer role, pretty much all leadership and influence questions. Nothing technical, just the usual 'tell me about a time you...' format the whole way through.
  • Tell me about a time you led a team or initiative. How did you set direction, keep people motivated, handle disagreement, and ultimately deliver the outcome?

“This is basically four questions crammed into one and I kind of rambled trying to hit all of them.”

View Post

SoFi·Software Engineer·Technical Phone Screen

May 2026
SoFi full-stack screen that was basically one meaty coding problem the whole time. The problem was interesting but I wasn't expecting a probability/simulation angle in what I thought would be a standard backend round.
  • Given a run-tracking system with classes representing individual runs and collections of runs, implement a Monte Carlo simulation (10,000 trials) that estimates the probability an in-progress run will finish at or below the current personal best. Each trial should randomly sample obstacle completion times from historical runs to fill in the remaining obstacles, then compare the projected total against the personal best.

“My first instinct was to overthink the class design and I wasted probably three minutes asking clarifying questions about the data model before realizing the sampling logic was the actual point.”

View Post

SoFi·Software Engineer·Technical Phone Screen

May 2026
Got a graph traversal problem at SoFi that was dressed up as a choose-your-own-adventure story, which honestly threw me for a second before I realized it was just reachability in a directed graph. Solid technical screen, nothing behavioral, just the one meaty problem.
  • You're given a choose-your-own-adventure story modeled as a graph where every choice node has options pointing to other nodes or ending nodes. Unlike a typical path problem, you must traverse ALL options at every node. Find the complete set of reachable ending nodes from the start node, handle cycles, and analyze the time and space complexity.

“The story framing tripped me up at first.”

View Post

SoFi·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at SoFi for a software engineer role. Just one question but it had a lot of weight to it, the kind where you can tell they're really probing how you handle org friction, not just whether you're a good coder.
  • Describe a situation where another team refused or deprioritized work you needed them to do. How did you handle the disagreement, get them aligned, and still reach the outcome you were after?

“This one took me a second to land on a good example.”

View Post