IB Interview Technical Questions Template: DCF Walkthrough Cheat Sheet

In a superday debrief, the associate did not ask whether the candidate knew DCF. He asked whether the candidate could explain why the model moved equity value, and the room went quiet when the answer turned into a formula dump. That is the real test. The problem is not that candidates forget a step. The problem is that they cannot show judgment inside the step.

A DCF walkthrough is not a math recital. It is a filter for whether you understand the logic of valuation, the sequence of the model, and the parts of the answer that deserve confidence versus skepticism. In one Q3 hiring committee discussion, an MD cut off the debate after 90 seconds because the candidate kept naming line items but never explained the bridge from operating performance to terminal value. That candidate looked prepared and still failed the signal check.

If you want the blunt verdict, it is this: interviewers are not grading your memory. They are grading whether you can think like someone who would not embarrass the team in front of a client. Not memorized steps, but defensible judgment. Not a clean spreadsheet story, but a clear investment story.

What do interviewers actually want from a DCF walkthrough?

They want proof that you understand valuation, not proof that you can recite a model from a training deck. In a first-round banking interview, the candidate who starts with enterprise value, explains the cash flow drivers, and then bridges to equity value sounds like someone who has actually worked through the logic. The candidate who opens with “EBITDA, then WACC, then terminal value” sounds like someone reading section headers off a screen.

The first counter-intuitive truth is that a polished DCF can hurt you if it sounds too automatic. In one debrief, a VP rejected a candidate who delivered a perfect sequence because the answer never changed tone when assumptions changed. The VP said the candidate had memorized the walk-through, but not the meaning of the walk-through. That is the distinction banks care about. Not correctness alone, but adaptability under pressure.

Your opening sentence should make the model feel like a valuation process, not a modeling exercise. A clean script is: “I would start with enterprise value from unlevered free cash flow, discount those flows at WACC, and then bridge to equity value by adjusting for debt, cash, and other non-operating items.” That sentence works because it reveals structure. It does not try to impress with jargon. It shows you know where the answer is going before you start walking.

The analyst who gets hired usually sounds slightly slower than the analyst who gets nervous. That is not because speed is bad. It is because speed without control reads as fragility. The room is listening for whether you can teach the model back to them, not whether you can outrun the question.

How should I open the walkthrough without sounding memorized?

Open with the bridge, then explain the engine. That order makes you sound like someone who understands what the interviewer is actually asking. In a live interview, the candidate who begins with operating assumptions often drifts into modeling trivia before the valuation logic is established.

The second counter-intuitive truth is that the safest opening is not the most technical one. It is the one that creates a map. A strong line is: “I’d begin with unlevered free cash flow because this DCF is valuing the business before financing, then I’d discount those cash flows with WACC and reconcile to equity value at the end.” That is not flashy. It is correct, and it gives the interviewer a reason to trust the rest of the answer.

Scene matters here. In one associate debrief, the hiring manager pushed back because the candidate launched straight into revenue growth assumptions before ever clarifying why the DCF was an enterprise value model. The manager did not care that the assumptions were technically reasonable. He cared that the candidate had not framed the problem. That is a common banker judgment: not wrong inputs, but wrong sequencing.

A useful script if the interviewer interrupts early is: “If helpful, I can keep this at the high level first and then drill into the sensitivities.” That line buys you control. It also signals that you know the difference between a headline answer and a modeling deep dive. Not every answer needs to be exhaustive. It needs to be navigable.

Which DCF assumptions do they actually probe?

They probe the assumptions that change value the most, not the ones that are easiest to explain. WACC, terminal value, revenue growth, margins, capex, and working capital are the usual pressure points because they expose whether you understand what drives the model rather than what fills it. The candidate who talks only about formula structure is usually the one who gets trapped when the interviewer asks, “Why is this assumption credible?”

The third counter-intuitive truth is that terminal value is not a closing step. It is often the real valuation. In one debrief, an interviewer discarded a candidate’s answer because the candidate treated terminal value as a mechanical plug instead of the central judgment call. That is exactly backward. A banker does not want a terminal value that looks neat. A banker wants one that survives scrutiny when someone asks why perpetual growth is justified, or why the exit multiple matches the business cycle.

This is where many candidates make the same error. They think the answer is to recite the formula for WACC, but the room wants to know how leverage, beta, and tax shield affect the discount rate. They think the answer is to name a perpetuity growth rate, but the room wants to know why that rate belongs below long-term nominal GDP growth and how that judgment changes by industry. Not the formula, but the sensitivity. Not the label, but the consequence.

You can say, “I would treat WACC and terminal value as the two main levers, and I’d defend both with market data and business-specific logic.” That line is useful because it invites discussion instead of defensiveness. It also gives the interviewer permission to push. In banking interviews, that push is not a trap. It is the test.

How do I handle edge cases like negative FCF, mid-year convention, or circularity?

You handle them by showing that the model still works when the story stops being clean. Negative free cash flow is not a fatal issue if you can explain why the company is still investable. Mid-year convention is not a trivia question if you can explain why timing affects present value. Circularity is not a spreadsheet nuisance if you can explain how bankers usually break the loop without losing the logic of the model.

The fourth counter-intuitive truth is that messy situations often help your answer more than perfect ones. In one interview, the candidate was given a growth company with negative FCF, and the strongest answer came from explaining why the negative cash flow was a function of capex and working capital build rather than a failure of the business. That candidate sounded like someone who had actually seen a model break and knew how to interpret the break.

A good response is: “If free cash flow is negative early on, I would focus on whether the business is investing ahead of future cash generation rather than assuming the DCF is invalid.” That is a judgment statement, not a hedge. Another useful line is: “For mid-year convention, I would use it when cash flows are generated evenly through the year, because it better reflects timing.” The point is not to impress the interviewer with formulas. The point is to show you know when the simplification is acceptable.

If the interviewer asks about circularity, do not pretend it is elegant. Say, “I’d usually solve it by iterating the debt schedule until interest expense stabilizes, then I’d sanity-check whether the simplicity changes the valuation meaningfully.” That answer sounds real because it is real. Not perfect spreadsheet purity, but controlled approximation.

What should I say in the final 30 seconds?

You should close with the one sentence that proves you know what matters most. In a banker’s mind, the last 30 seconds are not for repetition. They are for synthesis. The candidate who ends with a polished recap of formulas sounds trained. The candidate who ends with a valuation judgment sounds hireable.

A clean closing script is: “The DCF is only as strong as the assumptions behind WACC, terminal value, and long-term operating margins, so I would anchor on what is most defensible for this company rather than trying to make every line item look precise.” That sentence is valuable because it tells the interviewer you understand model risk. Not every assumption deserves equal confidence. Some deserve scrutiny. Some deserve skepticism. That hierarchy is what separates a trainee from a junior banker.

In one MD debrief, the final note on the candidate was simple: “Too procedural, not enough ownership.” That is the hidden standard. The room does not want someone who can walk through a template. It wants someone who can own the template when the assumptions get challenged by a client, a VP, or a live deal team. Not explaining every line, but defending the lines that move the outcome.

If you need one final line to leave behind, use this: “I’d expect the terminal value and discount rate to drive most of the debate, so I’d spend my time defending those assumptions first.” That is the kind of answer bankers remember because it mirrors how they talk in actual meetings.

Preparation Checklist

Rehearse the full DCF in one uninterrupted pass, then do it again with interruptions from memory.
Start your answer with enterprise value, then bridge to equity value before you touch assumptions.
Memorize the three pressure points: WACC, terminal value, and working capital.
Practice one negative case, one high-growth case, and one mature cash-flow case so you can adapt on the fly.
Work through a structured preparation system (the PM Interview Playbook covers debrief-style reasoning and structured walkthrough examples, which maps well to the way interviewers pressure-test judgment).
Write out two exact scripts for interruptions: one for a high-level reset, one for a deeper technical follow-up.
Time yourself speaking for 2 minutes, then 5 minutes, because the pacing changes under stress.

Mistakes to Avoid

The worst mistakes are not technical errors. They are judgment errors dressed up as technical language.

BAD: “I start with EBITDA because that is what the model has.” GOOD: “I start with enterprise value because the DCF is valuing the business before financing, then I bridge to equity value.” The first answer sounds like file navigation. The second sounds like valuation logic.
BAD: “I assume 10% WACC because that is standard.” GOOD: “I defend WACC by tying leverage, beta, risk-free rate, and tax shield to the company’s risk profile.” The first answer is a placeholder. The second shows you can explain why the number belongs in the model.
BAD: “I only use perpetuity growth because it is simpler.” GOOD: “I use perpetuity growth as the primary view and exit multiple as a cross-check, then I explain which one is more defensible for this business.” The first answer hides uncertainty. The second shows you know where the uncertainty lives.

FAQ

Should I start the DCF walkthrough with free cash flow or enterprise value? Start with enterprise value. The interviewer wants the valuation bridge first, not the line-item mechanics. If you begin with cash flow too early, you sound like you are reading a model instead of explaining it.
Is it okay to say I would use a range for WACC or terminal growth? Yes, and it is often better than pretending precision you do not have. The stronger answer is to explain why the range exists and what business facts would push you to the high or low end.
What is the most common reason candidates fail this question? They recite steps without showing judgment. The interview is not testing whether you know that WACC comes before discounting. It is testing whether you know why that choice matters and where the model is most fragile.amazon.com/dp/B0GWWJQ2S3).