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. 059A bank reports CET1 of 11 percent against a 9 percent requirement. Is it safe?Regulatory capitalHardsuperdayRegulatory reportingBank credit risk

   Say this

   Not from that number alone. A capital ratio tells you about solvency under the RWA model, and banks fail from liquidity and from concentration, not from a ratio. I'd want to know the composition of the denominator, the funding profile and the trajectory before answering.

   Then walk it

   1. First, what's the 9 percent made of? Pillar 1 minimum, plus the conservation buffer, plus Pillar 2, plus any systemic surcharge. If the 9 percent is mostly buffer, breaching it restricts dividends rather than triggering resolution, which is a different kind of 2 percent of headroom.
   2. Second, interrogate the denominator. RWA density against total assets, how much is IRB-modelled, and single-name and sector concentration. An 11 percent ratio on a book with 25 percent in one sector is far weaker than the same ratio on a granular one, and the IRB formula won't show it.
   3. Third, the trajectory, which is what actually matters. Was it 13 percent two years ago? Is it falling through loan growth, buybacks or rising provisions? The direction and the stress path matter more than the level.
   4. Fourth, and this is the real answer, liquidity. SVB had a capital ratio comfortably above requirement the week it failed. Look at LCR, NSFR, deposit concentration, the uninsured deposit share, and unrealised losses in held-to-maturity securities that don't touch CET1 until they're sold.
   5. Fifth, asset quality and provision adequacy. Coverage ratio, NPL ratio, Stage 2 share, and whether provisioning looks light relative to peers. A thin provision stock means the capital ratio is borrowing from the future.
   6. Sixth, the stress result. What does CET1 do in the adverse ICAAP or supervisory scenario? If it drops to 8 percent, the 2 percent buffer is already spoken for and the bank is effectively at its constraint.
   7. So my answer would be: 11 against 9 is adequate headroom on a granular, well-funded, well-provisioned book with a stable trajectory, and thin on a concentrated book with a volatile funding base. And I'd say what I'd need to see rather than guess, because the interviewer is testing whether I'll commit to a number without the information.

   Where candidates lose it

   Answering yes or no. There isn't enough information, and the interviewer is testing whether you know that solvency ratios don't capture liquidity or concentration. SVB is the example that proves it, and naming unrealised held-to-maturity losses is the detail that lands.

   Expect next

   • What would you want to see to be comfortable?
   • SVB had a fine capital ratio. Why did it fail?
   • Does breaching the buffer requirement mean the bank fails?
2. 065A bank funds long-dated fixed-rate securities with uninsured corporate deposits. Walk me through everything that can go wrong.Liquidity risk and ALMHardcase studyTreasury and ALMBank market risk

   Say this

   That's the Silicon Valley Bank structure, and it fails in a specific sequence: rates rise, the asset side loses economic value without showing it in the accounts, depositors leave because they have better options, and selling the assets to pay them crystallises the loss and destroys the capital.

   Then walk it

   1. Step one, the duration mismatch. Long fixed-rate assets and overnight liabilities means economic value of equity falls hard when rates rise, even while net interest income looks fine for a while because deposit rates lag.
   2. Step two, the accounting shield that becomes a trap. Securities classified as held-to-maturity aren't marked through capital, so the loss is invisible in the reported ratios. SVB had roughly $15bn of unrealised HTM losses against about $16bn of equity at the end of 2022. The capital ratio said nothing was wrong.
   3. Step three, the depositor incentive. Uninsured corporate treasurers are rate-sensitive and professional. When T-bills yield 5 percent and your account pays 0.5, they leave for economic reasons before there's any fear. That's a slow outflow that forces asset sales.
   4. Step four, the crystallisation. Selling HTM securities to fund outflows moves the loss from a footnote into the income statement and the capital ratio. Worse, selling any of the portfolio can force reclassification of the whole HTM book under the accounting rules, which is why banks resist it until they can't.
   5. Step five, the run. Once the loss is public, uninsured depositors with a 100 percent loss-given-failure have every incentive to leave first, and they can now do it in an afternoon from a phone with a group chat coordinating them. SVB lost about $42bn in a single day.
   6. Step six, concentration as the accelerant. A depositor base drawn from one industry with shared advisers and shared venture investors is not a diversified funding book. It's one depositor with many accounts.
   7. What the risk function should have done: report EVE alongside NII and escalate the gap, treat unrealised HTM losses as economic capital regardless of accounting, model uninsured deposits with far faster run-off, set a concentration limit on depositor type, and hedge the duration with swaps. The last one is the cheapest and SVB had almost none on.
   8. And the governance point: SVB had no chief risk officer for part of 2022 and its interest rate stress scenarios had reportedly been changed to be less severe. The measurement failure was downstream of a governance failure, which is almost always the case.

   Where candidates lose it

   Describing it as a liquidity problem only, or a rate problem only. It's the interaction, plus an accounting classification that hid the loss, plus a concentrated and professional depositor base. Candidates who name the HTM accounting treatment and the depositor concentration show they've read the post-mortem rather than the headline.

   Expect next

   • Why didn't the capital ratio show the problem?
   • What single hedge would have changed the outcome?
   • How would you set a depositor concentration limit?
3. 066What does it mean if an estimator is BLUE?Statistics and quant foundationsHardtechnicalUBSRisk Management · Zurich · 2021

   Say this

   Best Linear Unbiased Estimator. Among all estimators that are linear in the data and unbiased, it has the smallest variance. That's the Gauss-Markov result: ordinary least squares is BLUE provided a specific set of assumptions holds.

   Then walk it

   1. Unpack each word, because that's what the question is testing. Linear in the observations. Unbiased, so its expected value equals the true parameter. Best, meaning minimum variance within that class.
   2. The Gauss-Markov conditions: correct linear specification, errors with zero conditional mean, homoskedasticity, no autocorrelation, and no perfect multicollinearity. Notice normality is not required for BLUE. You need normality for the t and F tests in small samples, not for OLS to be efficient.
   3. The restriction that matters is 'linear'. A biased or non-linear estimator can easily beat OLS on mean squared error. Ridge and lasso are deliberately biased and often predict better, and James-Stein shrinkage famously dominates the sample mean. So BLUE is optimality within a box, not optimality.
   4. In finance the assumptions fail routinely. Returns are heteroskedastic and volatility clusters, so OLS stays unbiased but the standard errors are wrong, which means your t-statistics lie. That's the practical consequence and it's the one to lead with when asked what breaks.
   5. The fixes: White or Newey-West robust standard errors for heteroskedasticity and autocorrelation, generalised least squares if you know the error structure, and instrumental variables if the regressor is endogenous. Endogeneity is the serious one, because it destroys unbiasedness rather than just efficiency.
   6. The distinction to keep straight: heteroskedasticity and autocorrelation cost you efficiency and valid inference. Omitted variables, measurement error in a regressor and simultaneity cost you unbiasedness. Those are different problems needing different fixes.
   7. So the answer I'd close with: BLUE is a useful benchmark and a weak guarantee. In a risk model I care more about whether the specification is right and whether the relationship is stable than about being efficient within the linear unbiased class.

   Where candidates lose it

   Expanding the acronym and stopping, or claiming normality is a Gauss-Markov requirement. It isn't. The two answers that separate candidates are that 'best' is only within linear unbiased estimators, so biased shrinkage estimators can beat it, and that in finance the binding violation is heteroskedasticity making your standard errors wrong.

   Expect next

   • Is normality required for OLS to be BLUE?
   • Which Gauss-Markov assumption fails most often in financial data?
   • Can a biased estimator ever be preferable?

   Reported by candidates at UBS (Risk Management, Zurich, 2021). Source: Wall Street Oasis.

4. 068Correlation versus dependence. Why does correlation fail exactly when you need it?Statistics and quant foundationsHardsuperdayBank market riskModel validation

   Say this

   Pearson correlation measures only the linear component of dependence, and it's a single average number. Dependence is the whole joint distribution. So two variables can be uncorrelated and completely dependent, and correlation tells you nothing about whether they move together in the tail.

   Then walk it

   1. The clean counterexample: Y equals X squared with X symmetric around zero. Perfectly dependent, zero linear correlation. Any non-monotonic relationship defeats Pearson.
   2. It's also not invariant to non-linear transforms, which matters because option payoffs are non-linear transforms of the underlying. Rank measures like Kendall's tau and Spearman's rho are invariant and are what you should use for dependence.
   3. The failure that costs money is that correlation is an average over the whole distribution, dominated by the many ordinary days. Tail dependence, the probability that both variables are extreme together, is a separate property that Pearson does not capture at all.
   4. Two distributions can share the same correlation matrix and have utterly different joint tails. A Gaussian copula has zero asymptotic tail dependence: extreme joint events are asymptotically independent. A t copula has positive tail dependence. Same correlation, completely different stress behaviour.
   5. Then correlations are non-stationary and they rise in a crisis. Equity pair correlations that sit around 0.3 in calm markets go to 0.8 in a sell-off. Diversification built on the calm number evaporates precisely when you were counting on it.
   6. Part of that rise is a statistical artefact worth knowing about: conditioning on large moves mechanically increases measured correlation even with a stable underlying joint distribution. So not all of the observed increase is a regime change, and that subtlety is a genuinely strong thing to say.
   7. What I'd do instead: use rank correlations for dependence, look at exceedance correlations conditional on large moves, use a copula with tail dependence when I need a joint distribution, and stress correlations to one in the scenario rather than trusting the estimate.
   8. Real cost: the 2007 quant equity deleveraging and the 2008 structured credit losses were both failures of dependence assumptions rather than of the individual marginal distributions.

   Where candidates lose it

   Saying 'correlation goes to one in a crisis' as the whole answer. That's true and it's the easy half. The deeper point is that correlation and dependence are different objects, that two joint distributions can share a correlation matrix and differ entirely in the tail, and that part of the observed crisis rise is a conditioning artefact.

   Expect next

   • What is tail dependence?
   • Why do Gaussian and t copulas differ if they have the same correlation?
   • How would you stress correlations in a scenario?
5. 069What is a copula, and what went wrong with the Gaussian copula in 2008?Statistics and quant foundationsHardsuperdayModel validationBank credit risk

   Say this

   A copula separates the marginal distributions from the dependence structure. Sklar's theorem says any joint distribution can be written as a copula applied to its marginals, so you can model each variable's tail properly and then choose how they move together. The 2008 failure was choosing a Gaussian copula, which has no tail dependence, for a problem that is entirely about tail dependence.

   Then walk it

   1. Mechanically: transform each variable to a uniform through its own cumulative distribution, then model the joint behaviour of those uniforms. That's the copula. It's a clean separation of 'how fat is each tail' from 'do they go bad together'.
   2. Gaussian copula: parameterised by a correlation matrix, and its asymptotic tail dependence is zero for any correlation below one. So as you go further into the tail, extreme joint events become asymptotically independent. That's the mathematical fact behind the failure.
   3. t copula: has positive tail dependence controlled by the degrees of freedom, so extremes cluster. Gumbel gives you upper tail dependence only, Clayton lower tail only, which is useful for credit where you care about joint defaults and not joint survivals.
   4. What actually happened with CDOs. David Li's Gaussian copula model let you price a tranche off a single correlation number, calibrated to historical data from a benign period, often 0.3 for mortgage pools. The senior tranche's value depends almost entirely on the probability that many defaults happen together, which is exactly the quantity the Gaussian copula sets too low.
   5. So the model said AAA was safe because widespread simultaneous default across regions was nearly impossible. In a national housing downturn, correlation went towards one and losses blew through tranches the model said were remote.
   6. The market knew before the maths admitted it. The base correlation skew, needing a different correlation for each tranche to fit observed prices, was the model telling you it was wrong, and it was read as a market quirk instead.
   7. The honest lesson, and the one to say: the failure was not really the copula. It was calibrating a tail parameter to data with no tail in it, using one number to describe dependence across a whole system, and treating a pricing convention as a risk model. A t copula with a bad correlation input would have failed too.
   8. Practical use today: copulas are standard in economic capital, portfolio credit models and multi-asset VaR. You'd use a t copula, calibrate dependence with attention to stress periods, and stress the dependence parameter rather than point-estimating it.

   Where candidates lose it

   Blaming 'the formula that killed Wall Street' without being able to say what property was missing. The specific answer is zero asymptotic tail dependence, plus a correlation parameter calibrated on benign data. And the mature closing point is that a better copula with the same bad calibration would also have failed.

   Expect next

   • Why does the Gaussian copula have zero tail dependence?
   • What was base correlation telling the market?
   • Would a t copula have prevented it?
6. 071Here is a book of credit exposures and a default history. Analyse it using dynamic probability metrics.Statistics and quant foundationsHardtechnicalJane StreetCredit Risk · London · 2025

   Say this

   Dynamic means the probabilities have to be conditional and updating, not a static average. So I'd build a hazard-rate view: probability of default in the next period given survival so far, conditioned on observable state, and then update it as new information arrives.

   Then walk it

   1. Start with the data audit before any modelling. Definition of default, observation window, censoring, survivorship, and whether exposures enter and leave the sample. Most of the wrong answers in credit analytics come from the panel being constructed badly, not from the maths.
   2. Then the right framing: survival analysis rather than a single-period classification. Estimate a hazard function, the instantaneous default rate conditional on having survived, using a Cox proportional hazards or discrete-time hazard model. That handles censoring properly and gives you a term structure of default rather than one number.
   3. Make it conditional on state. Time-varying covariates: rating migration, spread level, utilisation, macro variables. A default probability that changes when the world changes is what 'dynamic' means here.
   4. Then update sequentially. Bayesian updating, or a Kalman-filtered latent credit factor, so each new month of data revises the estimate rather than triggering a full refit. For sparse default data, a Bayesian approach with an informative prior from external data is far more stable than maximum likelihood on twelve observations.
   5. Dependence, which is what makes a credit book different from a set of single names. Estimate a common factor and its loading, because portfolio loss is driven by correlation, not by average PD. Report the loss distribution, the 99th percentile and expected shortfall, not just expected loss.
   6. Validation appropriate to sparse data: time-series calibration tests, a binomial or Vasicek test given the low default counts, discriminatory power via a time-dependent AUC, and a comparison against market-implied hazard rates from CDS where they exist.
   7. Then say what you'd report. Not a single PD. A term structure of conditional default probabilities, the portfolio loss distribution with tail measures, the top contributors to tail loss, and an explicit statement of how much of the answer is driven by the correlation assumption.
   8. And the honest limitation: with a short history and few defaults, the tail of the loss distribution is an assumption rather than an estimate. I'd say that up front rather than present a confident 99.9th percentile.

   Where candidates lose it

   Reaching for a classifier and reporting AUC. The word 'dynamic' is doing the work in the question: it's asking for conditional, time-varying, updating probabilities, which means hazard models and Bayesian updating, not a static logistic fit. And in a credit book the correlation assumption drives the tail more than the PD does.

   Expect next

   • How would you handle the sparsity of defaults?
   • How would you estimate the common factor loading?
   • How would you present the uncertainty in the tail?

   Reported by candidates at Jane Street (Credit Risk, London, 2025). Source: Wall Street Oasis.

7. 079Estimate next year's credit cost for a mid-sized Indian bank's unsecured personal loan book.Indian regulationHardcase studyIndian bank risk and treasuryBank credit risk

   Say this

   I'd build it bottom-up from vintage delinquency. For a mid-sized Indian unsecured book, I'd expect credit cost somewhere in the 3 to 5 percent range of the book, and I'd build to that number rather than assert it, then say which assumption moves it most.

   Then walk it

   1. Structure: credit cost equals flow rate into default times loss given default, applied to the average book, plus the change in provision stock on existing stages. Keep it as a flow, because a stock-based estimate hides the growth effect.
   2. Size the book and its mix. Say 20,000 crore of unsecured personal loans, average ticket 3 lakh, tenor three to four years, so roughly a third of the book amortises each year and new origination is a large share. A fast-growing book has a young average vintage, which understates delinquency until it seasons.
   3. Flow rate: start from observed 30-plus delinquency and apply roll rates. If 30-plus is 4 percent and roughly 60 to 70 percent of 30-plus rolls to 90-plus over the following quarters, forward flow into NPA is roughly 2.5 to 3 percent annualised. Bureau data and RBI's Financial Stability Report give you a system benchmark to sanity-check against.
   4. LGD: unsecured, so recovery is low. Collections and settlements might recover 15 to 25 percent over two years, so LGD of 75 to 85 percent. Multiply: 3 percent flow times 80 percent LGD gives roughly 2.4 percent, then add the provision build on the growing performing book and you get to 3 to 4 percent.
   5. Then the adjustments that actually decide the answer. Seasoning: if origination grew 40 percent last year, next year's delinquency is set by that cohort, and personal loan defaults peak 12 to 24 months after disbursal. Vintage curves, not current delinquency, are the honest input.
   6. Macro and policy overlay: RBI raised risk weights on unsecured consumer credit to 125 percent in late 2023 specifically because growth was running far ahead of secured lending. That slows origination and tightens underwriting, which improves next year's cohort and worsens the growth denominator.
   7. Segment sensitivity: new-to-credit borrowers, fintech-sourced and app-based loans, and small-ticket loans run multiples of the delinquency of salaried, bureau-scored, existing-customer lending. A weighted average across a book with a rising fintech share drifts upward even if each segment is stable.
   8. So I'd give the range, name my two swing assumptions, roll rate and the fintech-sourced share, and say what I'd need to tighten it: vintage curves by origination channel and the bureau's segment-level delinquency trend.

   Where candidates lose it

   Producing a single confident number. The interviewer wants a structure, two or three named assumptions and a range, plus awareness that a fast-growing unsecured book looks artificially clean because the loans haven't seasoned. Vintage analysis is the concept that has to appear.

   Expect next

   • Why does a fast-growing book look clean?
   • What did RBI's risk weight increase actually change?
   • How would you split this by origination channel?
8. 082A new trading desk is being set up. How would you build its limit framework?Risk governance and appetiteHardsuperdayBank market risk

   Say this

   Start from the mandate, not from the metrics. Understand what the desk is supposed to do and how it makes money, then set limits that allow that strategy and block everything else. Then layer loss limits on top, because risk limits alone don't stop a desk bleeding.

   Then walk it

   1. First the mandate: which products, which currencies, which maturities, which counterparty types, and where the edge comes from. A market-making desk and a relative-value desk with identical VaR need completely different limits.
   2. Then the aggregate risk limit, usually VaR or expected shortfall, sized off the capital allocated and the expected return. A desk allocated 100 crore of economic capital with a target return might get 5 crore of VaR, and you sanity-check that the implied risk-return is credible.
   3. Then granular sensitivity limits, because aggregate VaR is nettable and hides structure. DV01 by curve bucket, gamma, vega by expiry and by strike bucket, credit spread sensitivity by rating, single-name concentration, and FX delta by pair. These are what a trader actually manages to.
   4. Then loss limits, which are separate and essential. A daily stop, a month-to-date and a year-to-date drawdown trigger, each with a defined action: reduce, review, or stop trading. Risk limits control exposure; loss limits control the bleed when the strategy is simply wrong.
   5. Then stress limits, because VaR won't catch the scenario that matters. A cap on loss under the prescribed stress scenarios, which is often the binding constraint for a desk selling tail options.
   6. Then the boundaries that aren't about size: a product whitelist, tenor caps, a concentration cap as a share of market open interest or average daily volume, and a liquidity limit on days-to-exit. New products need explicit approval, which is how you stop mandate creep.
   7. Calibration approach for a brand new desk with no history: use a comparable desk's profile, size conservatively, and review after three and six months against actual usage. A limit used at 20 percent is wasted capital; a limit at 95 percent every day is being managed to rather than respected.
   8. And the governance wrapper: who can approve an excess and at what level, pre-trade blocks where possible rather than post-trade reports, and an automatic escalation after a second breach in a rolling period. Say that, because it's where limit frameworks actually fail.

   Where candidates lose it

   Setting a VaR limit and calling it done. VaR nets, so a desk can sit inside it with enormous concentrated positions. The complete answer has aggregate, sensitivity, loss, stress and liquidity limits, plus a product whitelist. And the loss limit is the one candidates most often forget.

   Expect next

   • Why do you need loss limits if you already have VaR limits?
   • How would you calibrate the limits with no trading history?
   • The desk is at 95 percent of its limit every day. Good or bad?
9. 083A senior trader tells you your risk number is wrong, that you don't understand his book, and that you are blocking a profitable trade. What do you do?Risk governance and appetiteHardsuperdayBank market risk

   Say this

   Take the challenge seriously and hold the line separately. Those are two different things: he may genuinely be right about the number, and that doesn't change whether the trade is inside the limit. I'd work the number with him and escalate the limit question through the proper route.

   Then walk it

   1. First, assume he might be right. Traders often do understand their book better than the risk system does, and the most common cause of a disputed number is a real modelling issue: a mismapped risk factor, a stale correlation, a proxy that stopped working, a position booked in the wrong bucket.
   2. So I'd ask him to show me where the number is wrong, specifically. Which position, which factor, what the number should be. A trader who can point at it is doing me a favour. A trader who only says 'it's wrong' is negotiating, not correcting.
   3. Then separate the two questions out loud. Question one is whether the model is right, which I will investigate today. Question two is whether the trade is inside the limit as the approved model currently measures it. Until the model changes through governance, the limit applies to the number we have.
   4. I would not change a risk number under pressure in the moment. That's the whole point. If it's wrong, it gets fixed through a documented model change, which also fixes it for everyone else and leaves a record.
   5. I'd offer a route rather than just a no: a temporary limit increase through the market risk committee with the rationale documented, or a structure that achieves most of his economics inside the limit. Risk managers who only ever say no get worked around.
   6. On the tone: no escalating in public, no defending the number I can't explain, and no pretending to more certainty than I have. 'I don't know yet, I'll have it by four o'clock, and until then the limit stands' is a completely defensible position.
   7. And I'd escalate to my own management the same day, before it becomes a complaint about me. Not to report him, but because a senior trader disputing a control needs to be visible. If I lose the argument at the committee, that's a legitimate outcome I'll implement.
   8. The thing I'd say last, because it's what interviewers are listening for: the P&L of the trade is not my consideration. If the limit is wrong for the business, change the limit through governance. Profitable is not an exception.

   Where candidates lose it

   Either caving or digging in. Both fail. The answer they want separates the question of whether the model is right, which you investigate genuinely and fast, from whether the limit applies, which isn't negotiable in the moment. And you must say that profitability is not a reason to allow a breach.

   Expect next

   • What if you investigate and he's right?
   • What if your own boss tells you to let it through?
   • How do you build a working relationship with a desk that sees you as an obstacle?
10. 100Tell me about a time you raised a risk that nobody wanted to hear about.Fit and careerHardsuperdayOperational risk

    Say this

    Pick something where you were the inconvenient voice, say what it cost you socially or politically, and be honest about the outcome even if you lost. The version where you were right and everyone thanked you is the least believable story you can tell.

    Then walk it

    1. Set up the pressure honestly. Who didn't want to hear it and why: a deadline, a deal, a manager's commitment, a group that had already decided. Without that tension there's no story.
    2. Describe what you actually did, in order. Checked your own work first, because being wrong in public destroys your credibility for a year. Then raised it privately with the owner. Then escalated with evidence when that didn't move it.
    3. Be specific about the evidence you brought, because the difference between a nuisance and a risk manager is whether you arrived with a number. 'I showed that the assumption implied a 40 percent recovery rate against 15 percent observed in the comparable cases' is a risk conversation. 'I had a bad feeling' is not.
    4. Say what it cost. An uncomfortable meeting, a manager who was short with you for a week, being seen as difficult, being overruled. The cost is what makes the story credible, and its absence is why most versions of this answer sound invented.
    5. Then the outcome, honestly, including if you lost. 'I was overruled, the trade went ahead, and it was fine' is a perfectly good story if you can say what you learned: whether your analysis was wrong, or right and the risk simply didn't materialise. Distinguishing those two is a sophisticated thing to say.
    6. Close with what you do differently now. Usually it's about how you raise things rather than whether: earlier, in writing, with the number first, and to the person who can act rather than the person who's easiest to tell.
    7. And if you've never been in that position, say so and give the nearest real thing, an academic or team setting. Inventing a corporate story you can't defend under three follow-ups is worse than a smaller true one.

    Where candidates lose it

    The heroic version where you were right, everyone listened and disaster was averted. It doesn't happen that way and interviewers know it. Include the cost and the possibility that you were overruled, and be able to say whether being wrong later means your analysis was bad or just that the risk didn't land.

    Expect next

    • What would you have done if you'd been overruled and then been proved right?
    • How do you raise something without damaging the relationship?
    • Have you ever raised something and been wrong?

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.