Capital One Interview Questions — Page 15

Capital One·Data Scientist·Hiring Manager Screen

May 2026

Capital One data scientist interview with a pretty demanding 'why us' prompt that required specific product knowledge, a 90-day plan, and anticipating regulatory challenges. Felt more like a strategy case than a typical DS screen.

Why Capital One specifically? Give two or three concrete reasons tied to their actual products or technology, and connect each one to a past project you worked on with measurable results.
Walk through what you would actually do in your first 90 days: which problem you'd tackle, who the stakeholders are, what metrics you'd move, and a dashboard you'd ship.
What's a challenge unique to Capital One's domain that you'd anticipate running into, and how would you handle it?

“This is where I spent most of my prep and still felt underprepared in the moment.”

View Post

Capital One·Data Scientist·Onsite - Behavioral / Leadership

May 2026

Capital One data scientist behavioral round, three questions all requiring specific numbers and trade-offs. The structure was pretty demanding, each question had multiple sub-parts and they clearly wanted receipts, not just vibes.

Tell me about a time you proactively helped unblock a teammate or cross-functional partner under a hard deadline. What was the measurable impact, what did you deprioritize to do it, and who pushed back on your decision?
Describe a time you surfaced an incorrect number in a live setting. How did you diagnose the root cause quickly, correct it, rebuild trust with stakeholders the same day, and change your process so it wouldn't happen again?
What's the accomplishment you're most proud of that required influencing people without any formal authority? Walk me through the baseline metric, the obstacles, decisions you'd make differently, and how you'd defend the result to a skeptical VP who challenges both the data and the business logic.

“The 'who disagreed' part is what tripped me up.”

View Post

Capital One·Software Engineer·Technical Phone Screen

May 2026

Capital One software engineer interview with a matrix manipulation problem that had a clever optimization angle baked in. Pretty algorithmic, nothing behavioral from what I remember.

Given an n by m integer matrix and a sequence of commands (reverse a row in place, swap two rows, or rotate the matrix 90 degrees clockwise), apply all commands in order and return the resulting matrix. Then discuss whether you'd simulate each command literally or track transformation state lazily.

“I went straight to the naive simulation and it felt fine until they asked about the rotate command specifically.”

View Post

Capital One·Software Engineer·Onsite - System Design / Architecture

May 2026

Capital One system design round for a software engineer role. One question, but it was a monster. They basically wanted you to design an entire banking platform from scratch, and the scope kept expanding the more you talked.

Design an online banking system that supports secure login, account opening, ATM transactions, intra-bank and inter-bank transfers, and querying transaction statistics over a time window. Walk through the architecture, data model, APIs, concurrency controls, external integrations, analytics approach, scalability, security, and monitoring.

“I started with the usual stuff, auth, accounts, a ledger service, and thought I was doing fine.”

View Post

Capital One·Data Scientist·Technical Phone Screen

May 2026

Capital One data scientist case interview, heavy quant focus. They handed me a co-branded credit card partnership scenario and basically said 'go build the business case.' It was more finance-y than I expected for a DS role, but in hindsight it makes sense given how Capital One thinks about product economics.

Given a co-branded credit card partnership bringing in 50,000 new customers, compute the 12-month NPV per acquired user and for the full cohort. Walk through each revenue and cost component: interchange, rewards, annual fees, servicing, credit losses, and acquisition costs. Apply monthly discounting at 10% annually.
At what partner CPA does the deal break even, holding all other assumptions constant?
Recompute the NPV under interchange rate changes of plus or minus 0.3 percentage points, and separately under credit loss changes of plus or minus $10 per user. Which variable drives more risk to the decision?

“This was the core of the whole interview.”

View Post

Capital One·Data Scientist·Onsite - Behavioral / Leadership

May 2026

Capital One data scientist interview with a pretty demanding behavioral question that made me think harder than expected about how I frame my own work.

Walk me through your most meaningful accomplishment in your recent role. Cover what the baseline and target were, what constraints or risks you faced, what you personally did versus what the team did, the quantified outcomes including sustained impact months later, any artifacts you created to make the result repeatable, and why the result might have happened even without you.

“This question wrecked me a little.”

View Post

Capital One·Data Scientist·Onsite - Multi Round

May 2026

Capital One onsite for a Data Scientist role, and the whole session was basically a live statistical role-play around credit card default modeling. One meaty question, a lot of pressure to think out loud, and the expectation that you could translate math to a non-technical exec on the fly.

Pick a statistical model to estimate default probability for a new customer segment using account age, utilization rate, and credit score. Justify your choice, compute a 95% confidence interval for the default rate, and then explain what that interval means to a non-technical executive.

“I went with logistic regression pretty quickly and that part felt fine.”

View Post

Capital One·Data Scientist·Technical Phone Screen

May 2026

Capital One data scientist interview that was basically one long case study on credit card unit economics, experimentation design, and causal inference all rolled into a single question. Dense and technical, probably the most finance-heavy DS interview I've sat through.

Given several customer segments with data on monthly spend, outstanding balance, interchange rate, APR, cost of funds, operations expense, and loss rate, compute the unit economics per active account and rank the segments by contribution margin. Explain any dominance relationships you observe.
Derive the break-even cashback rate for each segment and show how it shifts under plus or minus 20% changes in loss rate and monthly spend. Which segments stay viable across all four scenarios?
Choose a single segment to launch the cashback feature to first, given that contribution margin must meet a threshold you define. Justify your threshold choice and explain what metric changes would flip your decision.
After launch, cashback is expected to lift both monthly spend and outstanding balance. Design a causal measurement plan that separates these two effects from selection bias. Cover the randomization unit, sample size inputs, primary and guardrail metrics, how you'd handle baseline adjustment, cannibalization from existing promo cards, and your stopping or rollout rule.

“I started with the contribution formula fine but fumbled on the annualized vs monthly timing mismatch for loss rate vs opex.”

View Post

Capital One·Software Engineer·Online Assessment (OA)

May 2026

Did the Capital One OA and it did not go as well as I'd hoped. The questions weren't hard on paper but I still fumbled parts of them, especially anything involving string parsing. Need way more practice before I try this again.

Solve a coding problem involving string parsing and manipulation.
Solve a coding problem best approached with a two-pointer technique.
Solve a coding problem requiring a HashSet and reverse tracking approach.

“This is what got me.”

View Post

Capital One·Data Scientist·Technical Phone Screen

May 2026

Capital One Data Scientist technical screen, one SQL question that looked manageable on the surface but had enough edge cases baked in to trip you up if you moved too fast.

Write a single SQL query to find the country with the highest probability of a sunny day. A day counts as sunny if any observation for that country on that date has condition = 'Sunny' (case-insensitive). Exclude dates where every observation for that country is NULL. Probability is sunny_days divided by total observed days, only for countries with at least 5 observed days. Break ties by probability descending, then total days descending, then country name ascending. Return one row with country_name, sunny_days, total_days, and sunny_day_prob rounded to 3 decimal places.

“The case-insensitive match tripped me up first.”

View Post