Why pre-screen IT service delivery managers before the interview
Service delivery has a measurement trap that catches weak managers. Every target can be met while users describe the service as unusable, because the targets measure the queue and not the experience. Managers who see through that look at what users actually wait for and fix it. A short screen surfaces whether someone has improved a service or has been reporting on one, and it surfaces how they behave when something is genuinely down.
What actually matters when screening IT Service Delivery Manager candidates
- 01
Execution and reliability
Check they have owned service delivery against signed SLAs: ask for uptime figures, P1 response times, ticket backlog reduction in ServiceNow or Jira Service Management, and monthly service review packs.
- 02
Improving the process
Probe continual service improvement work: problem management to remove recurring incidents, shift-left to self-service or knowledge base, automation of joiner-mover-leaver, and measured cost or handling-time savings.
- 03
Judgement and autonomy
Test major incident and escalation judgement: when they invoked MIM bridge calls, held or overrode a change in CAB, and how they handled a vendor breaching contracted response times.
- 04
Communication
Assess how they run service reviews with business owners and third-party suppliers: incident comms during outages, post-incident reports, and translating CSAT or availability data for non-technical directors.
Pre-screening questions to ask IT Service Delivery 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.
Services they ran
4 questions01What is your experience with IT service delivery management?
Listen forServices, user numbers and team size named, with what they owned rather than what the department delivered.
Scale left undescribed, or a role that turns out to be reporting on services someone else ran.
02What processes or methodologies do you use in delivering IT services?
Listen forFramework practices applied selectively with a view on which add value and which add ceremony at their scale.
A framework applied in full regardless of size, or processes named with no adaptation described.
03Can you explain your experience with IT service management tools?
Listen forTools configured to fit the process rather than the reverse, with a change they made that reduced handling time.
Tool used as delivered with no configuration, or process shaped entirely by what the tool defaults to.
04How do you measure the success or failure of delivered services?
Listen forUser experience measured alongside queue metrics, with an example where targets were met and users were still unhappy.
Success reported entirely from ticket metrics, or no measure of what users think of the service.
Behaviour in a failure
3 questions05How would you deal with a critical service failure, especially with deadlines at stake?
Listen forCommunication started early on a stated cadence, with restoration prioritised over diagnosis and evidence preserved.
Stakeholders updated only once resolved, or a technical fix pursued while nobody tells users anything.
06Describe an instance where you had to deal with an unexpected IT issue and how you handled it.
Listen forA specific incident with their own decisions, including what they escalated and when, and what changed afterwards.
Incident described from a runbook, or no structural change following a significant failure.
07Explain how you identify and deal with potential risks in IT service delivery.
Listen forSpecific risks they identified in advance, such as single points of failure or expiring contracts, and what was done.
Risk maintained as a register with no action, or risks noticed only after they materialised.
Improvement delivered
3 questions08How have you managed cost control in IT service management?
Listen forA cost they reduced with the figure and the trade-off, including what service level was affected if any.
Cost savings claimed with no figure, or reductions that degraded a service without anyone deciding to accept that.
09How have you ensured continuous service improvement in your previous roles?
Listen forRecurring incidents analysed and eliminated, with a specific problem class that stopped appearing.
Improvement described as a review meeting, or the same incidents recurring throughout their tenure.
10Can you describe a time when you implemented a solution that significantly improved service delivery?
Listen forA change with before and after numbers, and evidence it held after their attention moved on.
Improvements claimed with no measurement, or a change that reverted once it stopped being pushed.
Managing the team
2 questions11How do you handle underperforming team members?
Listen forA direct conversation with specific expectations and a follow-up, including a case that ended in an exit.
Work routed around the person instead, or performance issues raised only at an annual review.
12What steps do you take in managing stakeholder expectations?
Listen forCommitments made only where deliverable, with a case where they said no to a business request and how it landed.
Expectations managed by agreeing to everything, or dates given without checking with the team.
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%5Quotes real SLA targets and attainment percentages, names the toolset, and shows sustained backlog and P1 volume reduction over quarters.
Improving the process
25%5Describes a specific CSI initiative with before and after metrics, such as repeat incidents cut by a third through root cause fixes.
Judgement and autonomy
25%5Gives concrete escalation calls with reasoning, including one where they pushed back on a supplier or business stakeholder and documented the outcome.
Communication
15%5Writes and presents clear outage comms and post-incident reviews; keeps executives informed without jargon and holds suppliers to account politely.
Every target can be green while users call the service unusable, because targets measure the queue. A one-way video screen asks what they actually improved.
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 the services and scale they ran, hear one critical failure, and check what they improved rather than reported.
How much should framework certification matter?
As evidence of vocabulary, not capability. Service management frameworks are widely certified and describe what good looks like. The screen tests whether someone has changed a service, which certification cannot show.
Evaluating answers
What is the strongest signal when screening this role?
A service that met its targets while users were unhappy, and what they did about it. Managers who notice that gap fix real problems. Anyone who reports green dashboards has been managing the measurement.
How do I judge their handling of a major failure?
Listen for communication before resolution. Users tolerate outages and not silence. A manager who describes updating stakeholders on a stated cadence while the team works has run a real incident.
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
