Disaster Recovery Specialist

Most days mix focused DR work in your assigned domain — testing specific systems, maintaining specific runbooks, supporting specific business functions, or owning particular vendor resilience reviews. You'll often work as part of a DR team or resilience function, partnering with infrastructure, application owners, and the business teams whose recovery depends on the systems. The cadence follows the test and assessment calendar more than incident-driven sprints.

What's harder than people expect is the cross-functional coordination the work requires. A recovery test that involves three application teams, an infrastructure team, and the business owners requires real project-management muscle. Earning credibility with technical teams who own the systems is often the most leveraged thing the role does, since their participation determines whether a test surfaces real findings or just confirms the plan looks fine.

People who tend to thrive here are technically grounded, collaborative, and patient with the slow rhythms of DR program work. The role tends to be a strong foothold into senior specialist, DR manager, or technical risk and resilience positions. The trade-off is that the work can feel specialized without being decisive, and growth often comes from broadening into manager-level work or deeper technical specialization.