Why pre-screen IT directors before the executive interview
Directors are usually hired into a situation rather than a steady state: an estate that has drifted, a team that has lost people, a budget nobody can explain. Running a well-functioning function and turning around a struggling one require different things, and both candidates describe leading an IT department with responsibility for strategy, budget and delivery. A short screen asks what they inherited and what they changed, which separates them faster than an hour on management philosophy.
What actually matters when screening IT Director candidates
- 01
Record of outcomes
Check what they owned: ERP migrations, M365 or cloud consolidations, uptime and MTTR figures, helpdesk SLA attainment, and IT budgets they held with headcount numbers.
- 02
Strategic judgement
Probe how they set technology roadmaps: build versus buy calls, licensing renegotiations, technical debt retirement, disaster recovery posture, and their stance on AI or SaaS sprawl.
- 03
Building and leading teams
Assess how they built the IT function: hiring sysadmins, security analysts and service desk leads, on-call rotations, retention during outages, and coaching engineers into managers.
- 04
Influence across the business
Look for evidence of influence outside IT: board reporting on cyber risk, SOX or ISO 27001 audits, department heads adopting new systems, and negotiations with vendors like Microsoft or Cisco.
Pre-screening questions to ask IT Director 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.
Estate outcomes
3 questions01Can you describe a complex technical programme you oversaw from start to finish?
Listen forScope, budget and duration stated, with the decisions they personally owned and the point where the plan had to change.
Describes the programme with no personal decisions named, or a delivery record with no difficulties at all.
02What strategies do you use for budget management within your department?
Listen forBudget size they held with a real reallocation decision, plus where the estimate proved wrong and what they cut or re-forecast.
Budget described with no figure, or no experience of managing an overrun or a mid-year reduction.
03What changes have you brought to a previous organisation's technology function?
Listen forA change that held after they left, with the state they inherited described honestly and what improved measurably.
Changes described as initiatives launched, or improvements that reverted once they moved on.
Decisions on evidence
3 questions04What is your approach to deciding on new technology?
Listen forEvaluation against defined requirements with a proof of concept, and a decision to reject something popular for a stated reason.
Decisions driven by analyst rankings or vendor relationships, or no technology they have declined to adopt.
05What is your strategy for vendor management and negotiation?
Listen forA supplier they exited with the switching cost understood, alongside renewal negotiation and how they avoided lock-in.
Vendor management described as renewals only, or an estate dependent on suppliers they could not realistically leave.
06What is your approach to technology risk management?
Listen forRisks they actually carried, such as end-of-life systems or single points of failure, with what they accepted and why.
Risk described as a register maintained, or no risk they consciously accepted with a documented reason.
Building and correcting
3 questions07How do you handle underperformance within your team?
Listen forA specific case with the standard named, support offered, and a clear point at which they moved to a formal process.
Avoids the conversation, or restructures around a problem rather than addressing it directly.
08What are your strategies for building a technology team?
Listen forReal hiring and retention decisions, including a role they left unfilled rather than lowering the bar, and how they kept people.
Team building described as culture and morale, or vacancies filled quickly with no account of quality.
09How do you deal with conflict within your team?
Listen forA real conflict, often technical disagreement between senior people, with how it was resolved without one side simply overruled.
Conflicts resolved by seniority, or no experience of a disagreement between strong technical people.
Holding a position
3 questions10Can you describe a difficult decision that benefited the company in the long run?
Listen forA decision that cost something visible in the short term, with how they explained it upward and whether it was accepted.
Difficult decisions described as cost savings, or no decision they had to defend against executive resistance.
11How proficient are you with technology governance frameworks, and why do they matter?
Listen forGovernance used to make decisions traceable rather than to slow them, with a control they removed because it added no value.
Governance described as compliance, or frameworks adopted wholesale with no adaptation to the organisation's size.
12How do you determine the technology needs of a business?
Listen forTime spent with operational teams before proposing anything, with a request they declined because the underlying problem was different.
Needs determined from executive requests alone, or a roadmap built with no contact with the people doing the work.
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.
Record of outcomes
35%5Names specific programmes (for example Azure migration, Netsuite rollout) with before and after uptime, ticket volume, and cost figures they personally owned.
Strategic judgement
25%5Explains a roadmap decision with the rejected alternative, the cost model behind it, and how the outcome was later reviewed.
Building and leading teams
25%5Describes specific promotions and structural changes, plus how they handled an underperformer or reduced burnout on an on-call rota.
Influence across the business
15%5Gives concrete examples of winning budget or driving adoption despite resistance, with named stakeholders, audit outcomes, or contract savings.
Running a stable function and turning around a struggling one are different jobs with identical resumes. A one-way video screen asks what a candidate inherited.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for an IT director take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish estate scale, budget and headcount owned, and hear what they inherited and changed before an executive interview.
What should the screen establish beyond scope?
Whether they have handled underperformance. Every director claims to build strong teams; far fewer can describe managing someone out or correcting a senior technical person. That conversation predicts a great deal about the first year.
Evaluating answers
What is the strongest signal when screening an IT director?
A decision that went against an executive. Directors who protect the estate can name a time they refused a system, a vendor or a timeline, and explain how the relationship survived. Those who cannot have been executing decisions rather than making them.
How do I judge vendor management answers?
Ask what they exited. Renewal negotiations are routine; removing an entrenched supplier is not, and it is where the real cost sits. A director who has migrated off something expensive can describe the switching cost and how they got it approved.
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
