OneMain Financial Interview Questions — Page 2

OneMain Financial·Data Scientist·Technical Phone Screen

Jun 2026

Had a technical screen for a Data Scientist role at OneMain Financial that leaned heavily into channel analytics and business metrics. Pretty applied, less about coding and more about thinking through funnel math and what numbers actually matter.

You're given impressions, click-through rate, and conversion rate for three sales channels (online, phone, email). Calculate expected purchases per channel, rank them by conversion efficiency, and estimate total expected revenue using an average order value. Then explain what additional metrics you'd want to assess channel performance more completely.

“The math part was fine, impressions times CTR times conversion rate, nothing tricky there.”

View Post

OneMain Financial·Data Scientist·Technical Phone Screen

Jun 2026

Technical screen for a Data Scientist role at OneMain Financial, focused almost entirely on regression diagnostics. One meaty question that spiraled into four sub-parts, which I was not fully prepared for.

You've fit a linear or logistic regression model and you suspect multicollinearity among the features. Walk through what multicollinearity is, how you'd detect it, how you'd fix it, and what changes you'd expect in model behavior afterward.

“This hit me as one question but it was really four questions stitched together.”

View Post

OneMain Financial·Data Scientist·Technical Phone Screen

Jun 2026

OneMain Financial data scientist interview that went deep on preprocessing pipelines for churn modeling. One question, but it was a beast covering imputation, outlier treatment, calibration testing, and MNAR bias all at once. Left feeling like I'd answered 60% of it well and glossed over the rest.

You're building a customer churn model with messy features: right-skewed spend data with extreme outliers, zero-inflated count features, and categorical plan types. Missingness is a mix of MAR and MNAR (high-spend users sometimes skip income). Walk through your full preprocessing pipeline for both linear models and tree ensembles, explain the tradeoffs of different imputation and outlier strategies, describe how you'd test the pipeline's effect on calibration and SHAP without introducing bias, and address what you'd do if about 10% of records are MNAR on a key feature.

“This was basically four questions stapled together and they wanted a coherent answer, not four separate answers.”

View Post

OneMain Financial·Data Scientist·Technical Phone Screen

Jun 2026

Technical screen for a Data Scientist role at OneMain Financial. One meaty SQL question covering cohort analysis, retention math, and deduplication all at once. Felt like a take-home problem crammed into a live session.

Using PostgreSQL, write a single SQL query that computes D30 retention rate and 30-day ARPU for monthly signup cohorts. D30 retention counts users who had any event exactly on signup_date + 30 days (events before signup date are treated as data errors and excluded). 30-day ARPU is total payments within the first 30 days divided by cohort size. You also need to deduplicate events that are exact duplicates on (user_id, event_ts, event_name). Explain how your query handles duplicates and late events.

“This one took me a minute to untangle because there are actually three separate problems stacked on top of each other: the dedup, the retention window logic, and the ARPU window, and they all feed into one final aggregation.”

View Post

OneMain Financial·Data Scientist·Online Assessment (OA)

Jun 2026

SQL screening for a Data Scientist role at OneMain Financial. Four queries on a single orders table, nothing too wild, but it moves fast if you're rusty on aggregation syntax.

Write a query to count how many orders each customer has placed.
Return the total revenue generated for each day.
Find the customer(s) with the highest single order amount.
Select all orders where the amount is above the overall average order amount.

“Pretty standard GROUP BY stuff.”

View Post

OneMain Financial·Data Scientist·Technical Phone Screen

Jun 2026

Live coding round at OneMain Financial for a Data Scientist role, four Python problems back to back with a no-libraries constraint and an O(n) time requirement on everything. Pretty standard stuff but the pace kept it stressful.

Write a function that reverses a string in-place.
Write a function that returns True if a given integer is a palindrome, False otherwise.
Generate the n-th Fibonacci number iteratively, without using recursion.
Given an unsorted list of integers, return a new list with only the unique values, preserving the original order.

“Tripped up for a second because strings in Python are immutable, so 'in-place' doesn't really mean what it sounds like.”

View Post

OneMain Financial·Data Scientist·Technical Phone Screen

Jun 2026

Did a technical screen for a Data Scientist role at OneMain Financial that turned into a straightforward profitability case. Nothing too wild but the sensitivity analysis part tripped me up more than I expected.

Given a restaurant's fixed costs, variable costs, and revenue per customer, calculate the break-even number of customers and the resulting profit.
Re-calculate profit after costs drop by a specified amount, then again after revenue per customer drops by a specified amount. For each scenario, explain what the change means for the business.

“They handed me the numbers directly so no ambiguity there.”

View Post

OneMain Financial·Data Scientist·Technical Phone Screen

Jun 2026

Case-style interview for a Data Scientist role at OneMain Financial, built around running a mock software company through a profit optimization exercise. Pretty quantitative for a DS screen, felt more like a micro econ exam than anything else.

You're given a software company's fixed costs, variable costs, and a price-demand curve. Find the profit-maximizing price, and tell me what additional data you'd want before standing behind your recommendation.

“I knew the marginal revenue equals marginal cost rule going in, but actually working through it with made-up numbers on the fly was messier than expected.”

View Post

OneMain Financial·Data Scientist·Technical Phone Screen

Jul 2026

Interviewed for a Data Scientist role at OneMain Financial and ran into a product finance case about a new credit card launch. Pretty quantitative for a DS screen, more than I expected.

A new credit card product earns revenue from an annual fee and interchange fees, and incurs costs from cashback rewards. Write out the break-even equation, then calculate the number of active cardholders needed to cover all costs given specific inputs. Also explain how changing the cashback rate or annual fee would shift that break-even point.

“I wasn't expecting a full unit economics case in a DS interview.”

View Post

OneMain Financial·Data Scientist·Technical Phone Screen

Jul 2026

Technical screen for a Data Scientist role at OneMain Financial. The whole thing was basically one long pandas/session-analytics problem that kept growing more constraints as I thought I was finishing it. Harder than I expected for what I assumed would be a standard DS interview.

Given a pandas DataFrame with user events (including a string/ISO8601 timestamp column that can be missing, a server-side datetime column, a URL, and a user ID), build 30-minute inactivity-based sessions per user. You need to: impute missing timestamps from the server log column, sort events robustly even if rows are out of order, assign session IDs when the gap between consecutive events exceeds 30 minutes, compute per-user stats (session count, median session duration, 95th percentile of pages per session), and make sure the whole thing works in streaming chunks without loading all users into memory at once. Also explain correctness on edge cases like exactly-30-minute gaps, duplicate events, and DST shifts.

“This one just kept expanding.”

View Post