Citi Data Scientist Interview Questions

Citi·Data Scientist·Technical Phone Screen

Jul 2026

Quant-heavy technical screen for a Data Scientist role at Citibank. The whole thing was binomial tree pricing, both equity options and fixed income, which I wasn't expecting to be this deep for a DS position. Left feeling like I'd done okay on the mechanics but probably fumbled the conceptual explanation on the American call question.

Given a two-period binomial stock model with S0=100, up factor 1.25, down factor 0.8, and a 5% per-period risk-free rate, compute the risk-neutral probability and price a European call with strike 100 using backward induction.
Using the same binomial tree, price an American put with strike 100 and identify any nodes where early exercise is optimal.
Prove whether early exercise of an American call on a non-dividend-paying stock can ever be optimal in this binomial framework, and explain the intuition.
Using a two-period short-rate tree with given up and down rates and risk-neutral probability of 0.5, price a zero-coupon bond maturing at t=2 with face value 100.
Price a two-period coupon bond with face 100 and coupon 5 paid at t=1 and t=2 using the same short-rate tree, then report its yield to maturity and explain the no-arbitrage pricing principle behind your approach.

“The risk-neutral probability calculation itself is fine, just plug into the formula.”

View Post

Citi·Data Scientist·Onsite - Behavioral / Leadership

Jul 2026

Behavioral round for a Data Scientist role at Citi, focused pretty heavily on risk and product analytics judgment. Three questions, all variations of the classic 'show me you did something real' prompts. Nothing too surprising but the follow-ups had teeth.

Tell me about a time your analysis actually changed a decision that was already in motion.
Walk me through a situation where you discovered the data you were working with was unreliable. What did you actually do about it?
How do you handle it when a stakeholder brings you a request that isn't clearly defined and you're not sure what they actually need?

“This is the one I felt best about.”

View Post

Citi·Data Scientist·Technical Phone Screen

Jul 2026

Citibank data scientist interview that went deep into model risk territory. The whole thing revolved around one big technical question on PD model validation, and they clearly expected you to know the full lifecycle, not just throw out buzzwords.

Walk me through how you would validate a newly developed probability of default model, covering data partitioning, discrimination metrics, calibration, stability monitoring, backtesting, challenger models, and documentation.

“This is a lot to cover in one question and I kind of panicked trying to sequence it all.”

View Post

Citi·Data Scientist·Technical Phone Screen

Jul 2026

Citibank data scientist interview that went pretty deep into probability and expected value territory. The main question was a multi-part die-rolling problem that escalated from a clean derivation into generalization and then a break-even cost analysis. Not what I was expecting from a bank role but here we are.

You roll a fair six-sided die repeatedly, collecting the face value each roll. You must keep rolling if you get 4, 5, or 6, and stop on 1, 2, or 3. Derive the expected total payout, showing your work via conditioning on the stopping time or an infinite series.
Generalize the die problem: suppose P(forced to roll again) = p and the expected value of a single roll is μ. Express the expected total payout in terms of p and μ.
Now suppose every roll after the first costs a fixed fee c. What value of c makes the game fair (expected net payout = 0)?

“This part I actually handled okay.”

View Post

Citi·Data Scientist·Technical Phone Screen

Jul 2026

Citibank data scientist interview with a pretty involved Excel-based case question around credit risk visualization. One question, technical, and it required more domain fluency than I expected going in.

Using Excel, walk through how you would build visuals to communicate portfolio expected loss, risk-weighted assets, and concentration risk. What specific PivotTables, charts, or heatmaps would you create, what fields and measures would you use, and why do those choices actually help decision-makers?

“I knew the EL and RWA concepts well enough but the 'why does this help decision-making' part is where I got a bit handwavy.”

View Post

Citi·Data Scientist·Technical Phone Screen

Jun 2026

Interviewed for a Data Scientist role at Citibank and got a pretty deep dive into credit loss accounting concepts, specifically around CECL. Not what I expected going in, but it made sense given the domain.

How does the CECL framework differ from the older incurred loss model, and what are the practical implications around lifetime loss estimation, forward-looking forecasts, loan pooling, and the resulting effects on allowance levels and earnings volatility?

“This was a lot to unpack in one question.”

View Post

Citi·Data Scientist·Onsite - Behavioral / Leadership

Jun 2026

Behavioral prep material for a remote Data Scientist role at Citi, focused on three core prompts around data influence, data quality, and cross-functional prioritization. No specific outcome or date is mentioned, reads more like structured prep than a post-interview debrief.

Tell me about a time your analysis changed a decision that was already heading in a different direction. What did you look at, and how did you bring stakeholders along?
Describe a situation where you were working with data that turned out to be unreliable or missing. How did you catch it, and what did you put in place so it wouldn't happen again?
When you get competing requests from product, engineering, legal, and risk teams with no clear owner and everyone thinks their thing is urgent, how do you decide what to work on first?

“This one is trickier than it sounds because you have to walk a line between 'my analysis was right' and 'but the data was observational so I can't be certain.' I kept wanting to just say the model proved it, but the interviewer would probably push back on causality.”

View Post

Citi·Data Scientist·Technical Phone Screen

Jun 2026

Interviewed for a Data Scientist role at Citi, heavy SQL focus around crypto trading metrics. Two tasks back to back, both required getting the join logic and date math exactly right under pressure.

Given a trades table and a users table, compute the share of active traders in the last 30 days who made at least 3 trades in that same window. Return the count of active traders, count of power traders, and the ratio as a decimal.
For each signup cohort, compute 7-day retention defined as a user making at least one trade on exactly the 7th calendar day after their signup date. Include users who never traded.

“I got the denominator wrong at first.”

View Post

Citi·Data Scientist·Technical Phone Screen

Jun 2026

This was a case-style interview for a data scientist role at Citi, basically a product analytics deep dive on a crypto trading scenario. The structure was pretty demanding and they clearly wanted you to think out loud through measurement, segmentation, and recommendations rather than just listing ideas.

BTC market volatility is elevated but retail trading volume on the platform has dropped. Walk through how you'd investigate this with data and translate your findings into a concrete recommendation.
If session counts are stable but executed trade volume is falling, what does that tell you and what would you do next?
How would you test whether a change in risk policy caused the trading volume drop?
During a volatility spike, what metrics would signal that a reliability or infrastructure issue is causing the volume drop rather than a demand issue?
If the volume decline is isolated entirely to new users, how does your recommendation change?

“This is the kind of question where you can really embarrass yourself by jumping straight to 'users are scared of volatility' without checking whether the metric is even real.”

View Post

Citi·Data Scientist·Technical Phone Screen

May 2026

SQL-heavy screen for a data scientist role at Citi. One question, pretty deep on window functions and financial metrics. Not a lot of fluff.

Write a SQL query to calculate 12-month rolling default rates by customer segment. You have a table with columns for month, segment, number of defaults, and number of accounts. For each segment and month, compute the sum of defaults over the current and prior 11 months divided by the sum of accounts over the same window.

“This one took me a minute to set up correctly.”

View Post