Why pre-screen IT capacity managers before the interview
Nobody notices capacity management until a service falls over at quarter end, and by then the decision that caused it was made months earlier by someone who did not have the numbers. The job is to produce those numbers early enough to matter and to be checked afterwards. Managers worth hiring know what their forecasts missed by. A short screen asks for that figure and for the shortage they had to manage through.
What actually matters when screening IT Capacity Manager candidates
- 01
Technical proficiency
Check hands-on command of capacity tooling: Prometheus or Grafana dashboards, vRealize Operations, SolarWinds, CloudWatch, plus queueing theory, utilisation baselines, and Python or SQL for trend modelling.
- 02
Systems and trade-offs
Probe trade-offs between over-provisioning cost and SLA risk: reserved instances versus autoscaling, storage tiering, mainframe MIPS or VM sprawl, and refresh cycle timing.
- 03
Evidence and rigour
Test forecasting rigour: how they built capacity plans from business demand inputs, validated against actuals, and load tested peak events like month end or Black Friday.
- 04
Collaboration and communication
Assess how they work with application owners, finance, and service management: capacity plan sign off, CAB input, chargeback reporting, and escalating impending exhaustion.
Pre-screening questions to ask IT Capacity Manager 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.
A shortage they handled
3 questions01Tell us about a time when you managed a critical capacity shortage.
Listen forA real shortage with what was done immediately and what changed afterwards to prevent a repeat.
Shortages described as somebody else's decision, or no incident they were personally in.
02Describe a situation where you had to adjust capacity planning due to unforeseen demand.
Listen forA demand change detected early from monitoring rather than reported by users after the fact.
Changes discovered when a service degraded, or no early warning in place at all.
03Describe your method of handling capacity risks and challenges.
Listen forRisks quantified with lead times attached, so procurement or scaling starts before the constraint bites.
Risks tracked in a register with no lead time, or thresholds set with no action attached.
Forecast against outturn
4 questions04Could you describe an occasion when your capacity forecast was not accurate?
Listen forA specific miss with the size of the error and what they changed in the method afterwards.
No forecast ever compared with the outturn, or errors blamed entirely on the business.
05What methods do you typically use for capacity planning?
Listen forTrend analysis combined with business input on planned changes, rather than extrapolation alone.
Planning from historical utilisation only, with no input from product or commercial teams.
06Can you explain your process for analysing data for capacity planning?
Listen forPeak and growth analysed separately, with seasonality and known events treated distinctly.
Averages used for planning, or peak behaviour not analysed at all.
07How familiar are you with performance modelling, benchmarking and simulation?
Listen forModelling used where the system is nonlinear, with results validated against real load.
Linear extrapolation applied to systems that queue, or models never checked against reality.
Capacity as cost
2 questions08Do you have experience with cloud platforms, and how does it change capacity management?
Listen forThe shift from a hard limit to a cost curve understood, with commitment and scaling decisions made deliberately.
Cloud treated as unlimited capacity, or cost forecasting not part of the role as they describe it.
09Do you have experience managing hybrid environments across on-premise and cloud?
Listen forBoth sides planned together, with the placement decision driven by cost and constraint rather than habit.
Each environment planned in isolation, or workload placement never revisited.
Trade-offs explained
3 questions10How do you communicate capacity information to non-technical stakeholders?
Listen forCost against risk presented as a decision for the business to make, with the consequence of waiting stated.
Utilisation percentages escalated with no decision attached, or requests framed as technical necessity.
11Explain your approach to monitoring and ensuring effective use of existing capacity.
Listen forIdle and over-provisioned resource identified and reclaimed, with the saving quantified in pounds.
Monitoring focused only on growth, or no reclamation of unused capacity.
12How do you prioritise allocation of resources in high pressure situations?
Listen forPrioritisation against agreed service levels, with the decision escalated rather than made unilaterally.
Allocation decided by who asked loudest, or service levels not used to arbitrate.
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.
Technical proficiency
35%5Names the monitoring stack they ran, explains headroom thresholds they set, and models growth with real utilisation and workload data.
Systems and trade-offs
25%5Quantifies both sides, citing cost per unit of headroom and the service breach scenario each buffer was sized to prevent.
Evidence and rigour
25%5Shows forecast versus actual accuracy over multiple cycles and describes revising the model when a projection missed.
Collaboration and communication
15%5Describes turning utilisation trends into a budget case or upgrade decision that non technical stakeholders approved.
Nobody notices capacity until a service falls over at quarter end. A one-way video screen asks what their forecast missed by.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish a real shortage they handled, test their forecasting method, and check how they present trade-offs.
How has cloud changed what to screen for?
It converts capacity into a cost problem. Nothing runs out, the bill grows instead. Ask about cost forecasting and commitment decisions, not just utilisation thresholds.
Evaluating answers
What is the strongest signal when screening this role?
A forecast that was wrong and what they learned. Managers who measure their own accuracy have that story. Anyone whose forecasts were never checked has been producing documents.
How do I judge how they work with the business?
Ask how they explain a capacity decision to a non-technical executive. Sound answers present cost against risk as a choice. Anyone who escalates a utilisation percentage will not get funding.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
