Tell me about a forecast you built that turned out to be noticeably wrong. What did you learn and change?

What the interviewer is looking for

• This question tests budgeting & forecasting. Explains drivers behind a forecast, how they gather input from budget owners, and how they re-forecast and learn when actuals move.
• Strong answers: Honest account of the miss, root cause in assumptions or drivers, and a concrete process change like driver-based inputs, scenarios or more frequent re-forecasting.
• Likely follow-up: How did you communicate the miss to the people relying on it?

Another way it may be asked: Think of a time your prediction missed. What caused it and what do you do differently now?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• If leadership wanted to move from an annual budget to a rolling forecast, how would you design and roll out that change?
• Can you walk me through how the income statement, balance sheet and cash flow statement connect to each other?
• How would you build a simple spreadsheet to track a small team's monthly spending against its budget?
• An hour before a report is due, you notice a number doesn't match the source system. What do you do?
• Walk me through how you would build a three statement model, and how you keep it easy for someone else to review.

Browse all questions