Cutover SaaS Admin

Position Title: Application Runbook Administrator (Cutover SaaS)

• Role Summary: The Application Runbook Administrator is responsible for administering and operationalizing Client’s Cutover SaaS platform to plan, build, govern, and execute runbooks for application recovery, environment changes, and key operational events. This role ensures runbooks are accurate, standardized, auditable, and aligned to change management and IT resilience practices, enabling predictable cutovers and reduced operational risk.
• Reporting/Alignment: Aligned to the IT Resilience Team (Disaster Recovery Team), partnering closely with application owners, infrastructure/Cloud teams, QA, InfoSec, and Service Management.
• Primary Focus: Cutover runbook lifecycle management (build, maintain, execute, improve).
• Core Value: Improve execution consistency, visibility, and auditability for resilience validation and critical events.
• Scope: Enterprise applications, shared services, and cross-team dependencies where coordinated task execution is required.

Key Responsibilities

• The Application Runbook Administrator owns day-to-day Cutover administration and enables delivery teams to produce high-quality runbooks that are ready for controlled execution.
• Administer Cutover workspaces, runbook templates, user access/roles, and configuration in alignment with Client’s policies.
• Build and maintain standardized runbook templates (e.g., DR test, migration events) including phase structure, task types, and required metadata.
• Partner with application and platform teams to capture end-to-end cutover steps, dependencies, owners, prerequisites, validation checks, and rollback procedures.
• Ensure runbooks meet governance standards: completeness, naming conventions, task clarity, time estimates, sequencing, and required approvals.
• Coordinate cutover readiness reviews and dry runs; confirm execution owners, communications plan, and validation criteria are in place.
• Lead or facilitate runbook execution in Cutover: launch events, manage task progression, monitor blockers, maintain real-time status, and ensure timely escalations.
• Integrate Cutover usage with broader release/change processes (e.g., change records, release calendars, maintenance windows) and maintain traceability for audits.
• Manage Cutover reporting and dashboards: runbook status, completion metrics, cycle time, missed steps, and post-event outcomes.
• Maintain runbook documentation and knowledge articles; provide training and coaching for new teams adopting Cutover.
• Drive continuous improvement via post-implementation reviews (PIRs), lessons learned, and template/process enhancements.
• 1) Intake: Receive request for a new/updated runbook and confirm scope, timeline, and stakeholders.
• 2) Build: Draft or update runbook in Cutover using approved templates and required controls.
• 3) Review: Conduct readiness review with owners; ensure validations, communications, and rollback are defined.
• 4) Execute: Facilitate the event; track progress, handle escalations, and provide leadership updates.
• 5) Close: Capture results, evidence, and lessons learned; update templates and artifacts.
• Required Qualifications and Skills
• This role requires strong operational discipline, cross-functional coordination, and proficiency with runbook-driven execution in regulated environments.
• Experience administering or power-using Cutover.
• Hands-on experience with IT Resilience, Incident Management (ITIL), and production support practices.
• Ability to translate technical procedures into clear, executable, step-by-step tasks with well-defined ownership and acceptance criteria.
• Strong stakeholder management and facilitation skills (coordinating cross-team tasks).
• Knowledge of SDLC concepts, environment management, and deployment patterns (e.g., blue/green, rolling, canary) at a conceptual level.
• Familiarity with incident/problem management and post-event review practices.
• Strong attention to detail, documentation rigor, and an audit-ready mindset.
• Comfort working in fast-paced schedules, including after-hours maintenance windows when needed.

Examples

Requirements

• Knowledge of SDLC concepts, environment management, and deployment patterns (e.g., blue/green, rolling, canary) at a conceptual level.