Risk Management interview preparation

Questions

100

Traced to a firm

37

Firms

12

Updated

September 2026

Asked at

All firmsUBS14MSCI7BLBlackRock5FTFranklin Templeton3Oaktree Capital Management2Scotiabank2Jane Street1Moody's1Neuberger Berman1PIMCO1SSState Street1TSTruist Securities1

Topic

All topicsMarket risk and VaR14Tail risk and stress testing5Greeks and sensitivities5Credit risk11Counterparty risk and CVA6Operational risk5Model risk and validation6Regulatory capital7Liquidity risk and ALM6Statistics and quant foundations7Indian regulation7Risk governance and appetite4Markets and macro9Fit and career8

Level

AnyCoreIntermediateHard

Type

AnyTechnicalCaseBrainteaserMarket viewFit

1. 093Tell me about your Python experience and what you have actually built with it.Fit and careerIntermediatetechnicalBLBlackRockRisk and Quantitative Analysis · New York · 2026

   Say this

   Be specific and be honest about the level. Name the libraries, describe one thing you built end to end, say what broke and what you'd do differently. A concrete small project beats a claimed proficiency every time.

   Then walk it

   1. Set the level honestly with a self-assessment they can verify: comfortable with pandas and numpy, have used statsmodels and scikit-learn, can write a class and a test, not a software engineer. Overclaiming is fatal because the next question is usually technical.
   2. Then one project in detail. For a risk role the ideal one is risk-adjacent: pulled daily prices for a twenty-stock portfolio, computed historical and parametric VaR, backtested the exceptions over three years, and showed the parametric version under-reporting breaches in the volatile period. That's a real answer and it's a week of work.
   3. Say what the data did to you, because that's the honest part of any data project. Corporate actions, missing days, tickers that changed, timezone alignment. Anyone who's done real work has a data-cleaning story, and its absence is a tell.
   4. Name the specific libraries per task: pandas for the data, numpy and scipy for the maths, statsmodels for regression and time series, matplotlib for output, and pytest if you've written tests. Vague 'I know Python' invites a hard follow-up.
   5. Have a view on tooling practices, briefly: version control, a requirements file, functions rather than one long notebook, a couple of assertions on the data. Risk teams care about reproducibility because a number that can't be reproduced can't be signed off.
   6. If your experience is thin, say so and say what you've done about it. 'I've done the CS50 problem sets and built this one project, I'm not fast yet' is respected. Claiming pandas and then failing to describe a groupby is not.
   7. Close with the risk-relevant framing: the reason a risk function wants Python is to check the vendor system's number independently. Being able to build a rough independent calculation is a control, not a convenience, and saying that shows you understand why they asked.

   Where candidates lose it

   Claiming a level you can't demonstrate. Buy-side risk interviews frequently follow this with a screen-share or a whiteboard question, so calibrate honestly. And the answer that wins is one small finished project described in detail, not a list of libraries.

   Expect next

   • Walk me through how you'd compute historical VaR in pandas.
   • What went wrong in that project?
   • Have you used SQL, and for what?

   Reported by candidates at BlackRock (Risk and Quantitative Analysis, New York, 2026). Source: Wall Street Oasis.

2. 097Why shouldn't we hire you?Fit and careerIntermediatesuperdayMSCIFinancial Tools · Monterrey · 2013

   Say this

   Give one real gap, evidence you're aware of its cost, and what you're doing about it. The question is a self-awareness and composure test, so a deflection fails it and so does anything that sounds rehearsed as a humblebrag.

   Then walk it

   1. Pick a gap that is genuinely a gap, relevant enough to be credible, and not fatal for the role. Depth in a specific product area, limited experience of a particular regulatory regime, less coding experience than someone from a quantitative background. Those are all real and all fixable.
   2. Then show you understand the cost to them rather than just naming it. 'I've never worked on a trading floor, so I'd be slower in my first months at reading how a desk actually behaves and where to push.' That's an honest account of what they'd be taking on.
   3. Then the mitigation, with evidence rather than intention. A course completed, a project built, a book worked through, a conversation with people doing the job. Intentions are free; evidence is not.
   4. Then, briefly, what you'd need from them, because that's what a real hire sounds like: early exposure to the desk, a named person to ask stupid questions of. It signals you've thought about ramping up rather than just getting in.
   5. The failure modes to avoid: the fake weakness like 'I work too hard' or 'I'm a perfectionist', which insults the question. Listing three genuine weaknesses, which is more honesty than was asked for. And attacking the role, which reads as bad judgement.
   6. Keep it short. Sixty to ninety seconds, one gap, no spiral. The composure part of the test is whether you can say something uncomfortable calmly and then stop talking.
   7. And don't argue with the premise by saying 'you should hire me because...'. Answer the question they asked first, then one short sentence on why the gap is worth it.

   Where candidates lose it

   The fake weakness. Interviewers hear 'I'm a perfectionist' several times a day and it scores as evasion. The other failure is over-disclosure, turning it into a confession. One real, relevant, fixable gap with evidence of work on it, delivered calmly and then stopped.

   Expect next

   • What would your last manager say you need to improve?
   • How long would it take you to close that gap?
   • What part of this job do you think you'd find hardest?

   Reported by candidates at MSCI (Financial Tools, Monterrey, 2013). Source: Wall Street Oasis.

3. 098Tell me about a time you faced an ethical decision.Fit and careerIntermediatesuperdaySSState StreetGlobal Data · Boston · 2024

   Say this

   Use a real, small, resolved example where you noticed something, raised it through the right channel, and it got fixed. Scale doesn't matter; the pattern does. In a risk role this question carries more weight than anywhere else, because escalating uncomfortable things is the job.

   Then walk it

   1. Pick something genuinely ambiguous but low stakes: a number in a report you knew was stale being presented as current, a teammate overstating a result, an expenses issue on a committee, a colleague sharing data they shouldn't have.
   2. Structure it as situation, what made it a dilemma, what you did, and the outcome. Fifteen seconds on the setup and most of the time on the action, because the action is what's being assessed.
   3. Show proportionality. Go to the person first where that's appropriate, then escalate if it isn't resolved. Regulated firms want judgement, not someone whose first move is always a report, and they also want someone who doesn't stop at an awkward conversation.
   4. Be specific about the discomfort. 'I didn't want to accuse him, so I asked where the number came from' is credible. Certainty and righteousness are not, and they read as a story polished for interviews.
   5. The risk-specific addition that makes this answer land: say what you'd do if the escalation went nowhere. Document it, take it one level up, and use the formal channel, whistleblowing or compliance, if it's material. A risk professional who stops after one unsuccessful attempt is a liability, and interviewers know it.
   6. Two stories to avoid: one where you did nothing and rationalised it, and one so serious that it raises questions about the environments you've been in. And never disclose a real employer's confidential matter, because how you handle confidentiality in the interview is itself part of the test.
   7. Have one prepared and rehearsed. 'I can't think of one' is the worst available answer and it's the most common.

   Where candidates lose it

   Claiming you've never faced one, or telling a story where you stayed quiet and justified it. In a risk seat the willingness to raise something unwelcome is the core competency being tested. And you must be able to say what you'd do if the first escalation was ignored.

   Expect next

   • What if you had raised it and nothing happened?
   • What if it had cost you the grade, or the offer?
   • Where's the line between judgement and looking the other way?

   Reported by candidates at State Street (Global Data, Boston, 2024). Source: Wall Street Oasis.

Firm tags come from public, anonymous candidate reports on Wall Street Oasis: strong signal, not sworn testimony. Firms are named as the places a question was reported, not as partners of Fin Maverick. Answers are written for this page to show how to think out loud; they are not scripts to recite.