Describe two methods for generating prediction intervals or probabilistic forecasts
Tests uncertainty quantification for risk-adjusted decisions. Strong answers: (1) parametric intervals via forecast error variance and normal multipliers, (2) bootstrap residual resampling for empirical percentiles.
What's really being asked
The interviewer wants to see if you understand that point forecasts alone hide risk. They are testing your ability to generate prediction intervals, distinguish parametric from empirical uncertainty quantification, and connect statistical output to business decision-making under uncertainty.
The full answer
Two distinct methods in this order. First, parametric analytical intervals. Assume forecast errors follow a distribution, typically normal, and compute the interval as the point forecast plus or minus a multiplier c times the estimated standard deviation of the h-step forecast distribution. For 95 percent coverage, c is 1.96; for 80 percent, c is 1.28. You must note that sigma-h is horizon-specific because forecast variance usually grows as h increases. Second, bootstrap or simulation-based intervals. Resample historical residuals with replacement, add them to the fitted values, simulate thousands of future sample paths, and extract empirical percentiles. This avoids normality assumptions and captures skewness or bounds naturally. A great candidate also contrasts them: parametric is fast and clean when normality holds; bootstrap is robust but computationally heavier. Finally, translate to stakeholders by framing intervals as scenario ranges, for example, a 95 percent interval means demand will fall between X and Y nineteen times out of twenty.
The mistakes people make
Confusing confidence intervals with prediction intervals. Confidence intervals quantify uncertainty around a parameter estimate; prediction intervals quantify uncertainty around a future observation. Another red flag is assuming constant variance across all forecast horizons. A third is proposing to use the standard deviation of the raw time series rather than the standard deviation of the forecast errors.
What usually comes next
How does the width of the interval change as the forecast horizon lengthens? What would you do if the residuals are heavily skewed or the variable is bounded below by zero? How would you explain a prediction interval to a CFO who only cares about worst-case inventory risk?
A concrete example
Suppose your model forecasts next week sales at 1000 units with normally distributed errors. Using the parametric approach and an estimated h-step standard deviation of 150, the 95 percent prediction interval is roughly 1000 plus or minus 294, giving 706 to 1294 units. Alternatively, you bootstrap the last 104 weekly residuals, simulate 10000 future paths, and find the empirical 2.5th and 97.5th percentiles land at 720 and 1310. The slight asymmetry reveals right-skewed errors that the normal model smoothed over, which matters for stockout versus overstock risk.
Interview question
If historical forecast residuals are heavily right-skewed and the target variable is bounded below by zero, which method for generating a 95% prediction interval is most appropriate and why?
- a.Parametric intervals with a fixed standard deviation across all horizons to ensure consistent width scaling
- b.Confidence intervals on the mean forecast because they directly quantify future observation uncertainty
- c.Bootstrap residual resampling because it preserves empirical skewness and respects natural bounds through simulated sample pathsCorrect
- d.Parametric normal intervals because the central limit theorem ensures symmetric coverage for long horizons
Why? this is the answer
Bootstrap residual resampling builds empirical percentiles from simulated paths, naturally accommodating skewness and lower bounds without normality assumptions. Option B is tempting but wrong because confidence intervals quantify parameter uncertainty, not the range where a future observation will fall.
Just read this? Test yourself on what you have been reading.
Read the original → otexts.com
- #forecasting
- #prediction intervals
- #uncertainty quantification
- #time series
- #analytics
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on forecasting — each one lists the topics its interview covers.
See open roles