Senior Disaster Recovery Analyst

Days tend to involve leading DR strategy work, designing test scenarios, partnering with infrastructure and application teams on runbooks, and mentoring junior analysts. You might be reviewing RTO/RPO requirements Monday, leading a failover test design Tuesday, and presenting test results to leadership Thursday. The work tends to live in DR planning tools, infrastructure documentation, and the steady cadence of testing and remediation.

The harder part is often the gap between paper plans and actual recovery capability. Systems evolve, dependencies shift, and runbooks decay quickly; testing reveals truth. Driving honest tests rather than scripted demos is a real skill. Variance across employers is real — regulated industries run frequent, rigorous tests; less-regulated environments often run lighter cadences with less scrutiny. Cross-team coordination during a test can be more demanding than the test itself.

People who tend to thrive here are technically deep, methodical, and comfortable surfacing uncomfortable truths about recovery readiness. They tend to enjoy the analytical puzzle of mapping dependencies and the satisfaction of a clean test. The trade-off can be the political weight of failed tests — proving the program isn't ready can be career-uncomfortable for the people who built it.