← Back to Directory

SoFi interview notes, page 6 of 7

Large Enterprises

Most of these SoFi write-ups come from Software Engineers (52), then Frontend Engineers (5) and Data Scientists (4). The most reported rounds are the technical phone screen (37), the system design round (11), the behavioral / leadership round (9) and the hiring manager screen (3).

61 interview notes · updated Jul 2026

SoFi·Software Engineer·Online Assessment (OA)

Jul 2026
SoFi OA for a software engineer role, two coding problems, nothing too wild but the second one had me staring at it longer than I'd like to admit.
  • Given a sorted array of request timestamps and a window size, find the maximum number of requests that fall within any inclusive time interval of that length.
  • Given a binary string, every second all adjacent '01' pairs swap simultaneously to become '10'. How many seconds until no '01' pairs remain?

“Sliding window, pretty textbook.”

View Post

SoFi·Software Engineer·Onsite - Behavioral / Leadership

Jul 2026
Behavioral round at SoFi for a software engineer role. Just the one question shared here but it was a meaty one about navigating conflict upward.
  • Tell me about a time you disagreed with someone significantly more senior than you. How did you handle it without damaging the relationship?

“This one made me pause because the instinct is to say something diplomatic and safe, but I think they were actually probing for whether you have a spine.”

View Post

SoFi·Software Engineer·Onsite - Behavioral / Leadership

Jul 2026
Behavioral round at SoFi for a software engineer role. One question, cross-functional flavor, the kind that sounds straightforward until you're actually in it.
  • Describe a situation where another team refused or kept deprioritizing work you needed from them. How did you handle the disagreement, get everyone on the same page, and still get what you needed?

“I had a decent story for this but I think I spent too long on the backstory and rushed the resolution part, which is probably the only part they actually care about.”

View Post

SoFi·Data Scientist·Technical Phone Screen

Jul 2026
SoFi DS interview that was basically one massive experiment design question stretched across six sub-parts. Felt more like a take-home being graded live than a normal interview. The depth they expected was real.
  • You're rolling out a new home page ranking algorithm. Walk through a three-stage evaluation plan: offline replay, small-scale interleaving, then full A/B test.
  • How do you define the exposure unit for this experiment, and how do you handle bucketing to prevent contamination across sessions or devices?
  • The primary metric is 30-day funded-account conversion per 1,000 impressions, with a baseline of 1.20% and a target relative uplift of 5%. Compute the required per-arm sample size at 80% power and alpha 0.05, then discuss how repeated exposures and cluster-robust variance change that number.
  • What guardrails would you put in place for this experiment, and how do you set sequential testing boundaries to allow early stopping without inflating Type I error?
  • How do you handle novelty effects, carryover bias, and seasonality? What's your ramp policy and how do you get early signal on a 30-day outcome metric?
  • How would you analyze heterogeneous treatment effects across user segments like new vs. existing users or credit tiers, and how do you control false discovery rate across those subgroups?
  • How do you detect p-hacking or Simpson's paradox in your results, and what are your ship criteria when the primary metric and guardrails point in different directions?

“The structure they wanted was pretty clear once I heard 'three-stage' but I fumbled the offline part.”

View Post

SoFi·Software Engineer·Technical Phone Screen

Jul 2026
SoFi coding screen with a word-wrapping problem that's basically LeetCode 68 but without the justification step. Pretty straightforward if you've done greedy string problems before.
  • Given an array of words and a maximum line width, pack words greedily into lines so each line stays within the width limit. No need to pad or justify the lines, just return them as-is.

“Easier than the classic version since you skip the padding logic entirely.”

View Post

SoFi·Frontend Engineer·Technical Phone Screen

Jul 2026
SoFi frontend round that was basically one big coding prompt. They had me build a loan estimator component in React, which sounds straightforward until you realize they want form handling, live calculations, accessibility, and then two follow-ups stacked on top of each other.
  • Build a React component that takes loan amount, interest rate, and term as inputs, computes monthly payment and total interest in real time, and renders the results. The implementation should cover form interaction, styling, calculation logic, and accessibility including labels, ARIA attributes, and keyboard support.
  • How would you debounce the recalculation so rapid input changes don't trigger it on every keystroke, and cache results for previously seen combinations of loan amount, rate, and term?

“The math part was fine, standard amortization formula.”

View Post

SoFi·Software Engineer·Technical Phone Screen

Jul 2026
SoFi software engineer interview with a graph traversal problem that sounds like a fun puzzle until you realize they want you to talk through complexity and cycle handling on top of writing the actual solution.
  • You're given a choose-your-own-adventure story modeled as a graph. Each node has options pointing to other nodes or ending nodes. Unlike a normal adventure where you pick one path, here you must traverse ALL options from every node. Find every reachable ending from the start node, handle cycles, and analyze the time and space complexity.

“The story framing threw me off for a second.”

View Post

SoFi·Software Engineer·Technical Phone Screen

Jul 2026
SoFi software engineer interview that went deep on a classic jump game problem. They didn't just want code, they wanted the full treatment: proof of correctness, complexity analysis, edge cases, the works.
  • Given an array of non-negative integers where each value represents the max steps you can jump forward from that index, first determine if you can reach the last index from index 0, and then find the minimum number of jumps to get there. They wanted an O(n) time, O(1) space solution, plus a correctness proof, complexity analysis, and a full edge case walkthrough.

“This is jump game 1 and 2 stapled together, which I didn't expect.”

View Post

SoFi·Software Engineer·Hiring Manager Screen

Jul 2026
Hiring manager round at SoFi for a software engineer role, two-part format that felt more like a structured conversation than a standard behavioral screen. The project deep-dive was expected, but the 'teach me something' portion threw me a bit.
  • Walk me through a recent project: what was the problem, what was your role, what trade-offs did you make, and what was the measurable impact?
  • What would you do differently if you could go back and redo that project?
  • Teach me one technical concept or tool you've learned recently, as if you're explaining it to someone in my context.

“This is the kind of question where you think you're ready and then realize mid-sentence that your 'measurable impact' is kind of fuzzy.”

View Post

SoFi·Data Scientist·Onsite - System Design / Architecture

Jul 2026
Big open-ended system design question for a DS role at SoFi, basically asked to architect a full personalized ranking system for financial products from scratch. No prior context, just dropped into it cold. The scope was way wider than I expected for a single interview block.
  • You're the first data scientist asked by a PM to build a personalized ranking system for financial products on a fintech app home page. Walk through an end-to-end solution: objective function, ranking approach, features, bias handling, business rule constraints, inference architecture, metrics, and monitoring.

“This was basically eight questions duct-taped into one.”

View Post