Financial Analysis interview preparation

Questions

100

Traced to a firm

42

Firms

28

Updated

September 2026

Asked at

All firmsMoody's7Bain Capital3SSState Street3AMAres Management2BLBlackRock2DED.E. Shaw2MSMorgan Stanley2Oaktree Capital Management2S&P Global2Bridgewater Associates1Citadel1FTFranklin Templeton1Golub Capital1HWHarris Williams1Houlihan Lokey1J.P. Morgan1Jane Street1MWMarshall Wace1Millennium Management1Morningstar1PIMCO1Sycamore Partners1TSTruist Securities1Two Sigma1Vanguard1WMWellington Management1Wells Fargo Securities1Wolverine Trading1

Topic

All topicsThree statements9Accounting policy and standards5Working capital and cash7Ratio analysis8Forecasting and budgeting9Variance and management reporting7Unit economics and costing8Capital budgeting7Cost of capital and valuation7Markets and rates5Modelling, Excel and data8Business partnering6Brainteasers and estimation4Fit and career10

Level

AnyCoreIntermediateHard

Type

AnyTechnicalCaseBrainteaserMarket viewFit

1. 034Top-down or bottom-up budget: which do you trust?Forecasting and budgetingIntermediatetechnicalCorporate FP&ABusiness finance

   Say this

   Neither on its own. Bottom-up gives you ownership and detail but is systematically sandbagged on revenue and padded on cost. Top-down gives you ambition and consistency but nobody in the business feels accountable for it. Run both and negotiate the gap.

   Then walk it

   1. The bias direction is predictable. If bonuses depend on beating the budget, business units submit conservative revenue and generous cost. I have seen a 6 to 10 percent gap between bottom-up submissions and what the same teams then delivered.
   2. Top-down has the opposite problem: it is arithmetically consistent with the board's growth target and operationally unowned, so nobody defends it in month four.
   3. So the process I would run is a top-down target as a frame, bottom-up build as the content, then a reconciliation that names each gap with an owner. The reconciliation table is the whole value of the exercise.
   4. What breaks the deadlock is drivers, not negotiation. If the top-down needs 14 percent growth and the bottom-up gives 9, the conversation is about headcount, capacity, price and pipeline, not about whose number is braver.
   5. I would also separate the plan from the commitment. A stretch target that drives behaviour and a realistic forecast the CFO uses for cash and covenants can be different numbers, and pretending they must be the same is how forecasts become unusable.
   6. The limitation: both approaches assume last year is a sensible base. Where the business model is changing, neither works and you have to rebuild from unit economics.

   Where candidates lose it

   Picking one and defending it as a matter of principle. The answer interviewers want is that you know the bias in each and run a reconciliation. Quantify the sandbagging gap if you can, because that proves you have seen a budget cycle.

   Expect next

   • How do you deal with a business head who always sandbags?
   • Should the target and the forecast be the same number?
   • How long should a budget cycle take?
2. 035What is a rolling forecast, and why would a company move off an annual budget?Forecasting and budgetingIntermediatetechnicalCorporate FP&AGCC finance centres

   Say this

   A rolling forecast always looks the same distance forward, usually four to six quarters, and gets re-cut every month or quarter by adding a new period as the old one drops off. You move to it because an annual budget is most wrong exactly when you need it most, in the second half of the year.

   Then walk it

   1. The structural flaw in annual budgets: by October you are steering with assumptions set the previous November. Decisions get anchored to a number that everyone privately knows is stale.
   2. A rolling forecast fixes the horizon rather than the calendar, so the planning quality does not decay through the year and you are never looking only three months ahead in Q4.
   3. It only works at a coarser grain. You cannot re-forecast 400 cost centres monthly and survive, so you re-forecast the 20 drivers that move the outcome and let the rest flow on ratios. That is the single most common implementation failure.
   4. Keep the budget for what it is good at: annual resource allocation, incentive targets and the board commitment. The rolling forecast is for steering. Companies that delete the budget entirely usually lose cost discipline.
   5. The cadence I would propose: monthly re-forecast of the current quarter, quarterly re-cut of the full rolling horizon, with a bridge each time from the previous version showing what changed and why. The bridge is what builds trust in the number.
   6. The honest cost is effort and forecast churn. If the number moves every month without explanation, business heads stop believing any of them, so version control and a change bridge are not optional.

   Where candidates lose it

   Describing the mechanics and skipping the granularity problem. Rolling forecasts fail because teams try to re-forecast at budget-level detail. Say that you re-forecast drivers, not line items, and keep the annual budget for targets.

   Expect next

   • What granularity would you re-forecast at?
   • How do you stop the number churning every month?
   • Would you keep the annual budget at all?
3. 036What is zero-based budgeting, and when does it actually work?Forecasting and budgetingIntermediatetechnicalCorporate FP&ABig Four

   Say this

   You build every cost line from zero and justify it against an activity, instead of taking last year plus inflation. It works on discretionary overhead where nobody owns the historical number, and it fails when applied to everything at once.

   Then walk it

   1. The mechanism: define cost packages, attach each to an activity and a service level, then fund them by priority against the available envelope. The question changes from 'why do you need more' to 'what would we stop doing'.
   2. Where it delivers: marketing, travel, consultancy, software licences, facilities, and the long tail of overheads that grew by accretion. Ten to 20 percent savings on those categories is a realistic outcome in the first pass.
   3. Where it does not: direct cost driven by volume, regulated or contracted spend, and anything where the answer is fixed by physics or law. Applying ZBB there wastes months to confirm the existing number.
   4. The real cost is organisational. It is slow, it is political, and it requires cost owners with the authority to say no. Done annually it collapses into incremental budgeting with extra paperwork.
   5. So my recommendation would be a rotating approach: full ZBB on a third of the overhead base each year, so every category is properly rebuilt every three years without the whole organisation stopping.
   6. And the failure mode to name: cutting cost without removing the activity. The cost comes back within two quarters, usually as contractors or as a service failure somewhere else.

   Where candidates lose it

   Selling it as a universal answer. Interviewers listen for whether you know it fits discretionary overhead, not volume-driven direct cost, and that cutting cost without removing activity just delays the spend.

   Expect next

   • Which cost lines would you exclude from ZBB?
   • How would you stop the cost coming back?
   • How does ZBB interact with a rolling forecast?
4. 038What is the difference between scenario analysis and sensitivity analysis, and when do you use each?Forecasting and budgetingIntermediatetechnicalCorporate FP&AFinancial modelling

   Say this

   Sensitivity moves one variable at a time to see which assumptions the answer is most exposed to. Scenario moves a coherent set of variables together to describe a state of the world. Sensitivity finds the levers; scenarios tell the story.

   Then walk it

   1. Sensitivity is mechanical: flex volume by plus or minus 10 percent, hold everything else, record the effect on EBITDA and on cash. Do that across ten assumptions and you get a tornado chart that shows you the three that matter.
   2. The point of sensitivity is triage. If a 10 percent move in raw material price changes EBITDA by 18 percent and a 10 percent move in overheads changes it by 2 percent, you know where to spend management attention and where to hedge.
   3. Scenario analysis is internally consistent by design. A recession case is not just lower volume, it is lower volume with discounting, worse mix, longer receivables, higher inventory and a tighter borrowing cost, all together, because that is how a recession actually arrives.
   4. So scenarios are for decisions and communication, sensitivities are for diagnosis. The board wants three scenarios with a probability view; the modeller needs the sensitivity table to know which three to build.
   5. Practically I run sensitivity first to find the drivers, then build two or three scenarios using only those drivers, and always include a breakeven case: how far can volume fall before we breach the covenant. That last one is the number treasury actually uses.
   6. The limitation of both is that they are still your assumptions. Neither tells you the probability of anything, and a Monte Carlo on made-up distributions just adds decimal places to the same guess.

   Where candidates lose it

   Using the two words interchangeably. The distinguishing feature is that scenarios move variables together and consistently. Also name the breakeven or covenant-breach case, because that is the version a CFO asks for first.

   Expect next

   • How many scenarios would you take to a board?
   • Would you assign probabilities to them?
   • Where does Monte Carlo add value and where does it not?

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.