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. 042What is operational risk, and what are the Basel event categories?Operational riskCorephone / first roundOperational riskGlobal capability centres

   Say this

   Basel defines it as the risk of loss from inadequate or failed internal processes, people and systems, or from external events. It explicitly includes legal risk and excludes strategic and reputational risk. Seven event categories, and the money is concentrated in two of them.

   Then walk it

   1. The seven Level 1 categories: internal fraud; external fraud; employment practices and workplace safety; clients, products and business practices; damage to physical assets; business disruption and system failures; and execution, delivery and process management.
   2. The distribution is extremely skewed. Clients, products and business practices is where the enormous losses sit, because that's mis-selling, market manipulation and conduct fines. Execution and process management is where the high-frequency, low-severity losses sit.
   3. That skew shapes the whole discipline. You need two lenses: a frequency lens for process errors, which you fix with controls and automation, and a severity lens for tail conduct events, which you manage through governance and culture rather than through controls.
   4. The measurement toolkit: internal loss data, external loss data for events you haven't had, scenario analysis for the tail, RCSAs for the forward-looking control view, and KRIs for early warning. Those five are the standard op risk framework and you should be able to name all five.
   5. Capital: Basel III's Standardised Measurement Approach replaced the old internal models. It's a Business Indicator Component scaled by a marginal coefficient, then multiplied by an Internal Loss Multiplier based on your ten-year average loss history. So your own losses now drive your capital, which is the incentive it was designed to create.
   6. The honest difficulty: operational risk loss data is sparse and non-stationary. Ten years of history contains very few tail events, and the risks that matter now, cyber and third-party concentration, barely appear in it. So scenario analysis carries weight that the maths can't support, and that's a judgement-heavy exercise.

   Where candidates lose it

   Reducing operational risk to fraud and system failure. The largest losses in banking history in this category are conduct and mis-selling, not rogue traders or outages. Naming 'clients, products and business practices' as the big-money bucket immediately shows you've looked at the loss data.

   Expect next

   • Which category holds the biggest losses historically?
   • How is operational risk capital calculated now?
   • Where does cyber risk fit in that taxonomy?
2. 043What is an RCSA, and how would you actually run one?Operational riskIntermediatetechnicalOperational riskGlobal capability centres

   Say this

   A risk and control self-assessment is the business identifying its own risks, rating them before and after controls, and owning the gap. Run badly it's a spreadsheet nobody reads. Run well it's the only forward-looking view of operational risk you have.

   Then walk it

   1. Start from processes, not from a risk list. Map the end-to-end process, find the failure points, and derive risks from those. Starting from a generic taxonomy produces generic risks that nobody recognises as theirs.
   2. For each risk, rate inherent likelihood and impact, then identify the controls, test whether they actually work, and rate residual risk. The distinction between design effectiveness and operating effectiveness matters: a beautifully designed control that is performed late every month is not effective.
   3. Then compare residual risk to appetite. Anything above appetite needs an action with an owner and a date, or a formal risk acceptance signed at the right level. That is the actual output; the ratings are just how you get there.
   4. Who does it: the first line owns it, the second line facilitates and challenges. If risk management fills in the RCSA, the business hasn't assessed anything and you've built a document rather than a control.
   5. Where it fails, and I'd say this without prompting. Everything gets rated amber, because nobody wants to own a red. Ratings never change year to year. The workshop runs after a fine rather than before. And it never reconciles against actual loss events, so a process with twelve losses last year is rated low risk.
   6. So the tests I'd apply to an RCSA: does it reconcile to the loss database, does it reconcile to audit findings, has anything moved since last year, and can a process owner explain their own top risk without reading the sheet.
   7. Practical numbers: for a mid-sized operation, expect 15 to 40 risks per process area. Hundreds means it's a control inventory dressed up as a risk assessment, and nobody will use it.

   Where candidates lose it

   Describing the template instead of the process. Two things separate a real answer: saying the first line must own it with the second line challenging, and naming the amber-everywhere failure mode. And reconciling the RCSA against actual loss data is the check almost no candidate mentions.

   Expect next

   • Who should own the RCSA?
   • How do you stop everything being rated amber?
   • How does the RCSA connect to your loss data?
3. 044Design three key risk indicators for a payments operation, and tell me what makes a KRI good.Operational riskIntermediatetechnicalOperational riskGlobal capability centres

   Say this

   A good KRI is leading, measurable without manual effort, and has a threshold that triggers a specific action. For payments I'd use the unreconciled item count and ageing, the manual intervention rate on straight-through processing, and the failed or returned payment rate by corridor.

   Then walk it

   1. Unreconciled items over two days old, by value and count. It's leading, because loss events start as breaks nobody chased, and it's cheap to produce from the reconciliation system.
   2. Manual touch rate on payments that should be straight-through. Every manual touch is a keystroke error waiting to happen, so this is a direct proxy for the frequency of process losses. A rise from 2 to 6 percent is a red flag before any loss appears.
   3. Failed and returned payment rate, split by corridor and by cause. It picks up upstream data quality problems, sanctions-screening false positives and correspondent bank issues, each of which needs a different fix.
   4. What makes a KRI good: leading not lagging, objectively measurable from a system rather than from a survey, sensitive enough that it actually moves, owned by someone with the authority to act, and attached to an amber and red threshold with a pre-agreed response.
   5. What makes a bad one: loss count, which is lagging and tells you the failure already happened. Headcount, which is context rather than risk. Anything requiring a manual monthly collection, because it degrades into a copy-paste exercise.
   6. Thresholds should be calibrated off the historical distribution, not picked round. Amber at roughly the 90th percentile of the last two years, red at the 99th, then reviewed annually. And each threshold needs a named action, or breaching it changes nothing.
   7. The failure mode to name: KRI inflation. A dashboard with 120 indicators gets ignored. Eight to twelve real ones per business, reviewed monthly by someone who can act, beats a hundred reported to nobody.

   Where candidates lose it

   Proposing lagging indicators. Loss count, number of incidents and audit findings are all after the fact, and they are what most candidates offer. A KRI is supposed to give you time to act, so lead with something that moves before the loss, and attach a threshold and an action to each.

   Expect next

   • How would you calibrate the thresholds?
   • What do you do when a KRI turns red?
   • Give me a KRI for cyber risk.
4. 045Explain the three lines of defence.Operational riskCorephone / first roundOperational riskGlobal capability centres

   Say this

   First line is the business, which owns and manages the risk it takes. Second line is risk and compliance, which sets the framework, sets limits and independently challenges. Third line is internal audit, which gives the board assurance that the first two are working.

   Then walk it

   1. The first line's ownership is the part that's usually wrong in practice. The trader owns the market risk, the lending officer owns the credit decision, the operations head owns the process risk. If the business thinks risk management owns risk, the model has already failed.
   2. Second line has two jobs that sit in tension: it advises the business and it challenges the business. That's why independence matters, and why the CRO reports to the board risk committee and not just to the CEO.
   3. Third line is independent of both and reports to the audit committee. It does not run controls, it tests whether they exist and work. Audit sitting in management meetings designing controls destroys its own assurance value.
   4. The interesting judgement calls: where does a desk-embedded risk analyst sit? Where does model validation sit relative to model development? Where does finance sit? Getting those boundaries wrong is how conflicts creep in.
   5. The standard criticisms, worth volunteering. It creates a compliance mindset where the first line assumes the second line will catch things. Responsibilities blur in the middle. And it can become three layers of reporting rather than three layers of control.
   6. That's why the IIA updated it in 2020 into a 'three lines model' with less rigid boundaries and more emphasis on governance and alignment. Knowing the model has been revised, and why, is usually more than the interviewer expects.

   Where candidates lose it

   Reciting the three lines without saying the first line owns the risk. That single point is what the question is testing. And if you can name a real ambiguity, like where model validation sits, you show you've seen the model collide with an actual org chart.

   Expect next

   • Where does model validation sit?
   • What's the main criticism of the model?
   • Who does the CRO report to, and why does it matter?
5. 046A trader has breached his VaR limit three times this month, and each time got approval after the fact. What do you do?Operational riskHardsuperdayOperational riskBank market risk

   Say this

   Three retrospective approvals isn't a limit breach problem, it's a control failure. The limit has effectively been replaced by a negotiation. I'd document the pattern, escalate it as a governance issue rather than three separate incidents, and force a decision: either the limit is wrong or the behaviour is.

   Then walk it

   1. First establish the facts precisely: what the limit is, the size and duration of each breach, who approved each one, whether the approver had authority, and whether the approvals were documented at the time or reconstructed afterwards. That last detail changes the nature of the issue completely.
   2. Then separate the two possible root causes. Either the limit is miscalibrated for a legitimate business, in which case the fix is a properly approved limit increase through the right committee. Or the trader is running more risk than the firm sanctioned, in which case it's a discipline matter.
   3. The crucial reframing: three ad hoc approvals in a month means the limit is no longer a control. A pre-approved excess is a limit; a post-approved excess is an apology. Say that sentence in the interview, because it's the point of the question.
   4. Escalation route: my head of risk and the market risk committee, not a quiet conversation with the desk head who has been signing the approvals. The approver is part of what needs reviewing, so escalating to them alone is the mistake.
   5. Then the pattern question. Look for other symptoms: end-of-day position reductions that reverse the next morning, P&L volatility inconsistent with reported risk, stale or hard-to-verify marks on illiquid positions. Limit breaches with cooperative approvals are a classic precursor, and every large rogue trading loss has this shape in hindsight.
   6. Consequences and record. In a bank this is reportable to the risk committee, it should appear in the operational risk event log, and it belongs in the trader's performance file. If nothing happens, the next breach is certain.
   7. And the systemic fix: hard-coded pre-trade blocks rather than post-trade reporting, a rule that excesses need pre-approval at a level above the desk, and an automatic escalation after a second breach in a rolling period.

   Where candidates lose it

   Treating it as three separate breaches to be logged. It's one control failure, and the interviewer is testing whether you'll escalate past the person who authorised it. The other failure is going straight to a disciplinary framing without checking whether the limit is simply miscalibrated for a legitimate business.

   Expect next

   • What if the approver is the head of the desk and outranks your boss?
   • What other red flags would you look for?
   • How would you redesign the limit framework so this can't happen?

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.