Service Continuity Manager

Days tend to involve maintaining service-level continuity plans, coordinating exercises, partnering with IT operations and application teams, supporting incident response, and reporting to leadership on continuity posture. You might be leading a service failover test Monday, updating recovery procedures Tuesday, and supporting an actual incident response Thursday. The work tends to live in runbooks, exercise materials, IT operations dashboards, and the relationships with infrastructure and application teams.

The harder part is often maintaining program discipline as services and dependencies change. IT changes constantly; runbooks decay; assumptions go stale. Driving the maintenance cycle is a daily skill. Variance across employers is real — regulated industries run formal continuity programs; less-regulated orgs depend on the manager's persistence. Post-incident learning can be where the role earns its credibility.

People who tend to thrive here are technically grounded, calm under pressure, and patient with the slow institutional rhythm of continuity work. They tend to enjoy the rare moment when a tested plan actually gets used and works. The trade-off can be the on-call demands — service incidents don't honor business hours, and continuity is often the call list.