Why pre-screen capacity planners before the S&OP panel interview
Pre-screening capacity planners saves your S&OP panel from candidates who cannot show their numbers. Applicants arrive from demand planning, industrial engineering, workforce management, and analyst pools, and every resume lists Excel, SAP, and forecasting. A resume cannot tell you the units, sites, or headcount they planned, the horizon they owned, or whether anyone tracked their accuracy. A ten minute screen surfaces the systems they actually touched, the bias in their own forecasts, and whether sales and finance signed the plan they built.
What actually matters when screening Capacity Planner candidates
- 01
Execution and reliability
Check the scale and horizon they planned to, the systems they used, and how their forecasts actually performed.
- 02
Improving the process
Test what they changed about the planning process itself, not just the numbers they produced.
- 03
Judgement and autonomy
Assess how they decide when demand signals conflict and committing early costs money either way.
- 04
Communication
Judge how they get sales, operations, and finance to agree on one plan rather than three.
Pre-screening questions to ask Capacity Planner candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Scale and systems
4 questions01What is your previous experience in capacity planning, and what scale and horizon did you plan to?
Listen forConcrete units and horizon: cases per week across four plants, 900 agent FTE at 30 minute intervals, or an 18 month machine hour plan.
They describe duties and job titles without ever naming volumes, sites, headcount, or the planning horizon they owned.
02Which ERP systems have you worked with for capacity planning, and what did you actually do inside them?
Listen forNamed modules and tasks: SAP PP/DS or IBP, Oracle ASCP, Kinaxis RapidResponse, or Anaplan, with the specific runs or reports they owned.
They list ERP names they only read output from, or cannot describe a single transaction, module, or planning run.
03Walk us through the capacity planning tools and software you use day to day.
Listen forA practical toolchain: ERP for master data, SQL or Power BI for analysis, Excel or a planning platform for scenario models, and how data moves between them.
Tools described only as buzzwords, with no view of where the data comes from or how it is validated.
04How proficient are you with business intelligence tools for identifying and analysing capacity issues?
Listen forSpecific dashboards or queries they built in Power BI, Tableau, or SQL, and the capacity signal each one was designed to catch early.
They consume reports built by an analytics team and have never written a query or built a view themselves.
Forecasting and analysis
3 questions05Describe a time you built a demand forecast plan that worked, and tell us how accuracy was measured.
Listen forA stated metric such as MAPE, WMAPE, or forecast bias, the baseline it improved on, and what they changed after the misses.
No measurement of accuracy at all, or credit claimed for a plan whose performance they never tracked.
06Which analytical techniques or models have you used in capacity planning, and when did you choose each one?
Listen forMethod matched to situation: time series for stable SKUs, Erlang C for contact volumes, regression on drivers, scenario or Monte Carlo for capital decisions.
Method names recited with no link to a business situation, or an admission that every forecast was a moving average.
07Tell us about a time you identified a capacity issue and what solution you put in place.
Listen forThe signal they spotted, the constraint (labour, tooling, cube, licences), the options costed, and the outcome in throughput, service level, or cost.
They only flagged the problem to someone else and cannot say what was implemented or whether it worked.
Judgement under pressure
3 questions08Walk us through a time you had to respond to an emergency capacity requirement.
Listen forA fast triage sequence: what they reprioritised, overtime or outsourcing decisions, who they escalated to, and the trade-off they accepted knowingly.
Pure firefighting with no decision framework, or blaming sales and forecast error without any recovery action of their own.
09How do you handle an unexpected demand spike when committing capacity early costs money either way?
Listen forThey quantify both sides: cost of idle capacity versus lost service, then propose a hedge, a trigger point, or a staged commitment with review dates.
They always default to adding capacity or always to holding, with no cost comparison or defined decision trigger.
10How have you balanced short-term operational adjustments against long-term strategic capacity plans?
Listen forTwo distinct cadences described: weekly or monthly rebalancing plus an annual or multi-year capital and footprint plan, and how one feeds the other.
They collapse both into one activity, or have only ever worked inside a weekly execution window.
Stakeholder alignment
2 questions11Share an example of presenting capacity planning data so non-technical stakeholders acted on it.
Listen forA named audience, the artefact they used (one page scenario comparison, constraint chart), the decision it triggered, and how they framed assumptions.
They send raw dashboards or dense spreadsheets and treat stakeholder confusion as the audience's problem.
12Tell us how you got sales, operations, and finance to commit to one capacity plan rather than three.
Listen forA defined consensus process: S&OP or pre-meeting cadence, documented assumptions, exception reviews, and who owned the final signed number.
They averaged conflicting inputs, or maintained separate plans per function to avoid the disagreement entirely.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Execution and reliability
35%5Has planned at real scale with measured forecast accuracy, and knows where their model was consistently wrong.
Improving the process
25%5Has redesigned a planning process or cadence, with measured effect on accuracy, stock, or utilisation.
Judgement and autonomy
25%5Decides under conflicting signals with the trade-off stated explicitly, and revisits the call when data lands.
Communication
15%5Drives a single agreed plan across sales, operations, and finance, and surfaces risk before it becomes a shortage.
Capacity planners have to defend a number to sceptical operations and finance leaders. Async video lets you hear how they explain a forecast assumption out loud, before you book the panel.
Try it on HirevireScreening FAQ
Process basics
What should a capacity planner screening cover in ten minutes?
Cover four things: the scale and planning horizon they owned, the systems they worked in (SAP APO or IBP, Oracle, Kinaxis, Anaplan, o9, or workforce tools such as NICE or Verint), how their forecast accuracy was measured, and one example of getting operations and finance to accept a single plan.
Should I screen for statistical modelling skills or systems experience first?
Screen for systems and measured outcomes first. Most capacity planning roles run on ERP and BI platforms where the method is already embedded, so fluency in SAP, Kinaxis, Power BI, or SQL plus a tracked accuracy metric predicts performance better than naming ARIMA or Holt-Winters without context.
Evaluating answers
How do I tell a real forecasting answer from a rehearsed one?
Real answers carry numbers and direction. Listen for a horizon (weekly, 13 week, 18 month), a unit (cases, machine hours, agent FTE, servers), an accuracy or bias figure, and what they changed after a miss. Rehearsed answers stay at the level of process description with no measurement attached.
What is a red flag when a capacity planner describes stakeholder conflict?
The red flag is a planner who resolved conflict by averaging inputs or deferring entirely to whoever pushed hardest. Strong candidates describe a documented consensus step, the assumptions they made visible, the scenario they costed, and who owned the final commitment when sales and finance still disagreed.
























