Why pre-screen disaster recovery specialists before the interview
Almost every organisation has a recovery plan and very few have restored a critical system under time pressure. The gap shows up in specific ways: a backup that completes but cannot be restored, a dependency nobody documented, a recovery target agreed with nobody. Specialists worth hiring have run a test that failed and fixed what it exposed. A short screen asks for that test, which is the only honest evidence here.
What actually matters when screening IT Disaster Recovery Specialist candidates
- 01
Technical depth
Check hands-on command of replication and failover tooling: Zerto, Veeam, Azure Site Recovery, SRM, plus how they derive RTO and RPO targets from a business impact analysis.
- 02
Real incidents and findings
Probe actual invocations and tests: ransomware recovery, datacentre power loss, a failed failover, plus the DR test schedule they owned and what the post-test report flagged.
- 03
Risk judgement
Assess how they rank applications by criticality, defend acceptable data loss to application owners, and handle dependency mapping gaps such as unrecovered Active Directory or DNS.
- 04
Getting things fixed
Look for evidence they closed test findings: updated runbooks, ISO 22301 or SOC 2 audit remediation, backup verification, and pushing app teams to fix untested restores.
Pre-screening questions to ask IT Disaster Recovery Specialist 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 recovery they ran
3 questions01Can you describe a successful recovery you have been part of?
Listen forA real recovery with the timeline, what was restored first and how long the service was down.
Recoveries described from a plan, or no incident they were personally involved in.
02Describe a time when a recovery plan failed and how you resolved it.
Listen forA specific gap such as a missing dependency or an unusable backup, with what was changed afterwards.
No plan that has ever failed, or failures attributed entirely to other teams.
03What was the largest disaster recovery project you have worked on?
Listen forScope described in systems and dependencies, with their own responsibility stated clearly.
Project size described by budget, or involvement limited to documentation.
Restores tested
3 questions04What types of recovery testing matter most, and how often should they happen?
Listen forFull restores tested regularly, not just tabletop exercises, and run under production-like conditions.
Testing limited to walkthroughs, or restores tested only when a system is being replaced.
05How would you rate your skills with backup management systems?
Listen forRestores verified rather than backup jobs monitored, with backups isolated from the systems they protect.
Backup success treated as recoverability, or backups reachable with the same credentials as production.
06Can you discuss your experience with cloud-based recovery approaches?
Listen forCloud recovery tested end to end, including capacity availability and network configuration at failover.
Cloud assumed to provide recovery, or failover never exercised end to end.
Targets agreed
3 questions07How would you ensure critical business systems are recovered quickly?
Listen forRecovery sequenced by dependency with critical services identified by the business, not by IT.
Everything treated as critical, or recovery order decided by technical convenience.
08What are the most critical components of an effective recovery plan?
Listen forRecovery time and data loss targets, dependency mapping and communications, all agreed with owners.
Plans centred on technology, or targets set without a business owner agreeing them.
09Can you describe your experience writing recovery plans for IT infrastructure?
Listen forPlans written to be usable under pressure by someone who did not write them.
Long documents nobody has read, or plans that assume specific people are available.
People who know the plan
3 questions10How have you helped businesses maintain continuity during IT outages?
Listen forManual workarounds agreed with the business for the period a system is unavailable.
Continuity treated as a technology problem, or no plan for operating without the system.
11What role does staff training and rehearsal play in recovery?
Listen forRehearsals run with the people who would actually be involved, including out of hours.
Training treated as circulating a document, or rehearsals limited to the IT team.
12What is your experience dealing with cybersecurity incidents and their recovery?
Listen forRecovery from a compromise treated differently, with evidence preserved and backups verified as clean.
Systems restored immediately after a compromise, or backups restored without checking them.
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 depth
35%5Names specific tooling and tiering, quotes real RTO and RPO figures per application, and explains replication versus backup trade-offs precisely.
Real incidents and findings
30%5Describes a real invocation or full failover test with timings, what broke, and the runbook changes that followed.
Risk judgement
20%5Prioritises by business impact rather than server count, and calls out hidden dependencies others missed before a test.
Getting things fixed
15%5Tracks findings to closure with owners and dates, and shows a measurable drop in recovery time between successive tests.
Almost everyone has a plan and very few have restored a critical system under pressure. A one-way video screen asks about the test that failed.
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 recovery, test their approach to testing, and check whether targets were agreed with the business.
How does this differ from a backup administrator screen?
Backups are one input. This role owns the recovery of a business service, which means dependencies, sequencing and communications, not just whether the data came back.
Evaluating answers
What is the strongest signal when screening this role?
A test that failed. Specialists who test properly have one and can describe the gap it exposed. Anyone whose tests always pass is running an exercise designed to pass.
How do I judge their recovery targets?
Ask who agreed the recovery time objective. Real answers name a business owner who signed it. Anyone who set it in an IT document has a target nobody will accept during an 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
