Question 1
Difficulty: medium
How do you build a reliable demand forecast when historical data is limited or inconsistent?
Sample answer
When history is limited or messy, I start by breaking the problem into smaller, more usable signals. I look at whatever data does exist, then supplement it with sales input, customer pipeline, seasonality patterns, promotion plans, and any market or category trends that can support the forecast. I also check for anomalies so I do not let one-off spikes distort the view. If the business is launching a new product, I usually build a bottom-up forecast using comparable items, assumed conversion rates, and launch curves, then refine it with sales and marketing feedback. I am careful to document assumptions clearly so everyone understands what is driving the number. Most importantly, I treat the forecast as a living model, not a one-time answer. I review it frequently, compare it to actuals, and adjust quickly when new information becomes available.
Question 2
Difficulty: medium
Tell me about a time you improved forecast accuracy. What did you change?
Sample answer
In my previous role, forecast accuracy was especially weak in the mid-term horizon because the team relied too heavily on intuition and not enough on structured inputs. I started by segmenting SKUs into different planning buckets based on volatility, margin, and customer impact. That helped us avoid using the same approach for every item. I also introduced a monthly demand review with sales, marketing, and supply chain so that promotions, customer losses, and launch timing were captured earlier. On the technical side, I cleaned up the historical baseline by removing outliers and separating true demand from supply-driven shortages. That made the trend much more trustworthy. Within a few cycles, we saw better alignment between forecast and actuals, and the team had fewer surprises in inventory planning. The biggest win was not just the accuracy improvement, but the stronger planning discipline across departments.
Question 3
Difficulty: medium
How do you handle conflicting inputs from sales, marketing, and operations when creating a forecast?
Sample answer
Conflicting inputs are normal, and I do not see them as a problem as long as there is a clear process to resolve them. I start by making sure everyone is looking at the same baseline and the same assumptions. Then I separate the data-driven forecast from the judgmental adjustments, so we can see where people are agreeing or disagreeing. If sales expects a big lift from a key account but there is no evidence yet, I ask for specifics: timing, volume, probability, and whether the customer has actually committed. If marketing wants to push a promotion, I check historical lift from similar campaigns and whether supply can support the demand. Operations usually helps ground the discussion in capacity and inventory risk. My goal is not to pick one department over another, but to build a forecast that reflects reality and is supported by evidence. That approach usually reduces tension and builds trust.
Question 4
Difficulty: easy
What forecasting methods or tools have you used, and how do you decide which one to apply?
Sample answer
I have worked with time-series methods, moving averages, seasonal indices, regression-based approaches, and collaborative forecasting processes. In practice, I do not believe there is one perfect method for every product or business. I choose based on the demand pattern, data quality, and business context. For stable, high-volume items, a time-series method can work well because the historical pattern is meaningful. For items affected by promotions, customers, or market changes, I prefer a model that includes outside drivers. For new launches, I rely more on comparable products and expert input than on pure history. I also use Excel, ERP systems, and planning tools to organize and monitor forecasts, but I am careful not to let the tool drive the process. I focus first on the logic, then use the system to scale it. The best method is the one that is understandable, repeatable, and improves decision-making.
Question 5
Difficulty: medium
Describe a situation where demand suddenly changed. How did you respond?
Sample answer
In one case, demand for a key product spiked unexpectedly after a competitor had a supply issue. Because the change happened quickly, the usual monthly planning cycle was too slow. I immediately pulled current sales orders, open pipeline, and inventory positions to understand whether the increase was a short-term surge or a more durable shift. I worked with sales to confirm which customers were actually converting and with supply chain to check whether we could support the volume without creating shortages elsewhere. I then adjusted the forecast in the near term and separated the temporary uplift from the core baseline so we did not overstate demand going forward. I also flagged the risk to leadership so they could make faster decisions on replenishment and allocation. What I learned from that situation is that responsiveness matters as much as model quality. A good demand planner has to react quickly while still keeping the forecast disciplined and transparent.
Question 6
Difficulty: hard
How do you use data to identify forecast bias?
Sample answer
I look at bias as the gap between how we forecast and what actually happens over time, and I analyze it by product, time horizon, and planner or business segment. A forecast can look accurate on the surface but still be biased if it consistently overstates or understates demand. I usually compare forecast versus actuals across multiple periods, not just one month, to see whether the error is directional. If I find a pattern, I dig into the cause. For example, we may be overstating promotional lift, underestimating seasonality, or carrying too much optimism in the sales input. I also like to separate bias from volatility, because a noisy category can look bad even when the process is sound. Once I identify a bias, I work with the team to correct assumptions or recalibrate the model. My goal is to make the forecast more balanced, so the business can trust it for inventory, capacity, and financial planning.
Question 7
Difficulty: medium
How do you prioritize SKUs or product lines when time and resources are limited?
Sample answer
I prioritize by business impact and planning risk. Not every SKU needs the same level of attention, so I usually segment products by revenue, margin, demand volatility, service risk, and strategic importance. High-volume or high-margin items deserve closer monitoring because small changes can have a big operational impact. I also pay special attention to items with long lead times, substitution risk, or heavy promotion exposure. For slower-moving items, I use simpler planning rules and focus on exceptions rather than spending too much time on detail that will not move the business. This approach helps me use my time where it matters most. I also revisit the segmentation regularly because product relevance changes over time. A planning process that worked last quarter may not be the best one now. Prioritization is really about making sure the team’s effort is aligned with service, inventory, and financial outcomes.
Question 8
Difficulty: easy
How do you collaborate with supply chain and finance as a demand planner?
Sample answer
I see demand planning as a connector role between commercial teams and operational planning, so collaboration with supply chain and finance is essential. With supply chain, I focus on making sure demand assumptions are realistic and actionable. That means sharing changes early, explaining the drivers behind the forecast, and understanding constraints like capacity, lead time, and inventory coverage. With finance, I make sure the demand plan supports revenue targets and that the assumptions behind growth, price, and promotional activity are consistent with the broader business plan. I have found that trust comes from transparency. If a number changes, I explain why it changed and what evidence supports the new view. I also try to speak each team’s language: service levels and stock risk with supply chain, and margin and revenue implications with finance. When those teams are aligned, the entire planning process becomes more credible and much easier to execute.
Question 9
Difficulty: hard
What would you do if leadership wanted a forecast that looked more aggressive than the data supports?
Sample answer
I would handle that carefully and professionally. First, I would make sure I fully understood the business reason behind the aggressive target. Sometimes leadership is responding to a real opportunity, such as a new customer win, a pricing change, or a major launch, and the data may not yet reflect it. In that case, I would build a scenario that shows both the committed baseline and the upside case, with assumptions clearly documented. If the aggressive number is not supported by evidence, I would be honest about the risk and explain the likely impact on inventory, service, and financial planning if we overforecast. I think a demand planner should be a partner, not just a validator of unrealistic expectations. My goal would be to give leadership a clear view of trade-offs so they can make an informed decision. Being direct, but constructive, usually works better than simply saying no.
Question 10
Difficulty: medium
How do you measure whether a demand planning process is working well?
Sample answer
I measure success with a mix of forecast quality and business outcomes. Forecast accuracy is important, but I do not rely on that alone because accuracy can hide bias or good luck in one period. I also look at forecast bias, service level, inventory turns, stockouts, obsolete inventory, and how often the forecast changes late in the cycle. A strong process should improve decision-making, not just produce a cleaner spreadsheet. I also pay attention to planner productivity and cross-functional alignment. If teams are constantly debating the forecast or making late corrections, that usually means the process needs work. I like to review metrics at regular intervals and use them to identify where the process is breaking down, whether that is data quality, assumption discipline, or poor collaboration. For me, a good demand planning process is one that is repeatable, transparent, and clearly tied to better supply chain and financial outcomes.
