Jobs · Information Technology

Sr. Incident Commander

Docusign · United States · 4 wk ago
RemoteRemoteInformation Technology$165k–$266k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Company Overview", "What you'll do", "Responsibility", "What you bring", "Wage Transparency", "Benefits", "Life at Docusign", "Accommodation", etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly. We must not repeat job title as heading. We should include sections only if posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Accommodation", "Life at Docusign" maybe not needed? The instruction says use headings for certain categories; we can include sections like About the role (company overview + what you'll do), Responsibilities, Requirements (what you bring basic), Qualifications (maybe preferred?), Skills, Benefits, Pay, Schedule. We need to decide what content goes where. Let's extract: Company Overview: Docusign brings agreements to life... (description). This could be "About the role" or maybe "About the company". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe includes company overview and what you'll do). But we also have a separate "What you'll do" section describing duties. That could go under Responsibilities. Responsibility section: list of duties (Serve as a subject matter expert..., Partner..., etc). That's responsibilities. What you bring: Basic and Preferred qualifications. That can be split into Requirements (basic) and Qualifications (preferred) or Skills. We need to include Benefits: they listed Global benefits provide options for the following: Paid Time Off, Paid Parental Leave, Full Health Benefits Plans, Retirement Plans, Learning and Development, Compassionate Care Leave. Pay: Wage Transparency section includes pay ranges per location and bonus info, stock RSUs. Schedule: The posting mentions "Participate in a rotational shift 24 x 7 x 365" and "on-call responsibilities outside business hours and weekends". Also "Job Designation Remote". So schedule info: rotational shift 24/7/365, on-call, remote. We should not include placeholder text like "commensurate with experience". Not present. We must not include boilerplate like EEO, accommodation, etc. Remove "Accommodation", "Life at Docusign", "Applicant and Candidate Privacy Notice", "States Not Eligible for Employment", "Equal Opportunity Employer", "EEO Know Your Rights poster". Also remove "Job Designation Remote: ..."? That's schedule info, we can keep but maybe incorporate into Schedule section. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

Company overview: Docusign brings agreements to life. Over 1.5 million customers and more than a billion people in over 180 countries use Docusign solutions to accelerate the process of doing business and simplify people’s lives. With intelligent agreement management, Docusign unleashes business-critical data that is trapped inside of documents. Until now, these were disconnected from business systems of record, costing businesses time, money, and opportunity. Using Docusign’s Intelligent Agreement Management platform, companies can create, commit, and manage agreements with solutions created by the #1 company in e-signature and contract lifecycle management (CLM).

What you'll do: The Senior Incident Commander is part of the SRE Incident Response team at Docusign. The role is around leading and facilitating incidents and incident management processes around our products and security. The role involves strategic project management, effective communication with stakeholders including executive leadership, and handling challenging incidents independently. They play a pivotal role in developing Docusign’s overall service excellence practice by creating standard operating procedures, training material, operationalizing action items and provide valuable metrics for improvement. The role also requires daily incident management support across various Docusign infrastructures globally, ensuring the maintenance of service levels. The role will facilitate resolution for all major incidents, and handling communications via bridge calls and emails. The role includes on-call responsibilities outside business hours and weekends, daily reporting, ticket administration, and general production assurance duties. The ideal candidate is self-motivated and responsible, with the ability to prioritize under heavy workloads and operate under time constraints. Adherence to established procedures and detailed documentation of incidents and resolution steps is essential. This position is an individual contributor role reporting to the Senior Director, Site Reliability Engineering.

But we might split "What you'll do" into Responsibilities section. However we already have Responsibilities separate. To avoid duplication, maybe About the role just company overview, and Responsibilities includes the "What you'll do" plus the responsibility list. Let's do:

About the role

Company overview: Docusign brings agreements to life. Over 1.5 million customers and more than a billion people in over 180 countries use Docusign solutions to accelerate the process of doing business and simplify people’s lives. With intelligent agreement management, Docusign unleashes business-critical data that is trapped inside of documents. Until now, these were disconnected from business systems of record, costing businesses time, money, and opportunity. Using Docusign’s Intelligent Agreement Management platform, companies can create, commit, and manage agreements with solutions created by the #1 company in e-signature and contract lifecycle management (CLM).

Responsibilities

What you'll do: The Senior Incident Commander is part of the SRE Incident Response team at Docusign. The role is around leading and facilitating incidents and incident management processes around our products and security. The role involves strategic project management, effective communication with stakeholders including executive leadership, and handling challenging incidents independently. They play a pivotal role in developing Docusign’s overall service excellence practice by creating standard operating procedures, training material, operationalizing action items and provide valuable metrics for improvement. The role also requires daily incident management support across various Docusign infrastructures globally, ensuring the maintenance of service levels. The role will facilitate resolution for all major incidents, and handling communications via bridge calls and emails. The role includes on-call responsibilities outside business hours and weekends, daily reporting, ticket administration, and general production assurance duties. The ideal candidate is self-motivated and responsible, with the ability to prioritize under heavy workloads and operate under time constraints. Adherence to established procedures and detailed documentation of incidents and resolution steps is essential. This position is an individual contributor role reporting to the Senior Director, Site Reliability Engineering.

  • Serve as a subject matter expert for Docusign’s incident management
  • Partner with the SRE team to manage complex and sensitive critical incidents to conclusion, identifying and resolving challenges to ensure timely resolution
  • Partner with Service Owners and SRE to craft quality RCA and drive improvements across the domain to minimize number of incidents and their severity
  • Monitor, evaluate and report on incident management programs, processes and statistics to assure continuous improvement, implementing automated procedures to capture such data consistently
  • Lead post-incident reviews (RCA) by working with Service Owners and SREs to identify root causes, propose actionable improvements, and implement processes that minimize the number and severity of future incidents
  • Leverage organizational data to analyze incident trends, operational success metrics, and key areas for improvement, enabling data-driven decision-making and proactive prevention strategies
  • Utilize advanced monitoring and automation tools to identify opportunities to reduce response times, and ensure swift mitigation of risks, enabling more efficient management of major incidents and preventing incident recurrence
  • Regularly interact with senior leaders to facilitate effective incident handling or project delivery, producing suitable communications
  • Generate communications for multiple audience types, both customer-facing and internal
  • Prioritize incidents based on impact and urgency and classify them based on customer and operational impact, ensuring efficient resource allocation and effective resolution
  • Engage resources to resolve major incidents and minimize customer/business impact, managing escalation path as necessary
  • Serve as an escalation point within the Incident Management process, contributing to and initiating Crisis Incident response processes and applying the escalation process when required
  • Analyze incident data for anomalies, correlations, and trends against operational success criteria to improve incident response and prevention strategies
  • Participate in a rotational shift 24 x 7 x 365
But note we already included rotational shift in responsibilities list; also schedule section could mention that. We need to avoid duplication: maybe keep rotational shift in Schedule section only. But it's also a responsibility. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we mention it only in Schedule, we still preserve it. It's okay to not duplicate. Let's move rotational shift to Schedule. Thus Responsibilities list excludes rotational shift. Now Requirements (basic qualifications) and Qualifications (preferred) and Skills. From "What you bring": Basic: - 8+ years of experience in Incident Management, including leadership of major incidents and high-severity situations - Experience in operating and implementing Incident Management tools - Experience with monitoring platforms and applications like Prometheus, Grafana, Azure Data Explorer, Incident.io - Experience with cloud and on-premise system architecture and design - Experience with troubleshooting techniques and problem-solving in a 24x7x365 environment Preferred: - Be Customer First - analyze incidents from customers perspective and drive through all phases to mitigation - Leadership during incident calls, confidently driving towards resolution while communicating progress effectively to all stakeholders - Strong cross-functional collaboration, coordinating with multiple internal teams to establish containment and remediation strategies are implemented and carried out - Ability to lead incident calls confidently and independently to a successful resolution - Ability to understand and work within complex, large enterprise business environments - Process improvement experience, including conducting process analysis, identifying inefficiencies, and implementing recommended solutions - Experience managing complex security and privacy investigations - Excellent oral and written communication skills, with the ability to tailor messages for technical and non-technical audiences - Ability to work well interpersonally across various levels and disciplines, as well as influence and manage without direct authority - Skilled in understanding infrastructure dependencies and system integrations to perform troubleshooting in public/private cloud environments - Applied mitigation experience with microservices architecture, CI/CD pipelines, network architecture, data storage solutions, and virtualization across hybrid environments, ensuring rapid incident resolution, effective rollback practices, and minimized downtime in highly distributed systems We could map Basic to Requirements, Preferred to Qualifications, and maybe Skills separate? But we could also put Skills as a combined list of both basic and preferred? The instruction: prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But they ask to use headings like Requirements, Qualifications, Skills. We can include all three if they have content. We could put Requirements = basic, Qualifications = preferred, Skills = maybe a subset like "Experience with monitoring platforms..." but that's already in requirements. Might be redundant. Better to have Requirements (basic) and Qualifications (preferred) and maybe Skills not needed. But we need to follow instruction: use headings for those categories if we have content. It's okay to omit a heading if no real specific content. So we can have Requirements and Qualifications sections, and maybe skip Skills. Now Benefits: list as ul. Pay: include wage transparency details and bonus/stock. Schedule: include rotational shift 24/7/365, on-call responsibilities outside business hours and weekends, daily reporting, ticket administration? Actually daily reporting etc are responsibilities. Schedule: rotational shift 24/7/365, on-call responsibilities outside business hours and weekends, remote work designation (Job Designation Remote). Also

Similar jobs

Sr. Incident Commander

DocusignUnited States· 4 mo ago
RemoteInformation Technologyapply on careers.docusign.com

Incident Commander

Surefox North AmericaSan Francisco, CA· 3 mo ago
Information Technologyapply on logsite.wd12.myworkdayjobs.com

Incident Commander

SwitchUnited States· 5 days ago
RemoteInformation Technologyapply on grnh.se

Incident Commander

Northern TrustTempe, AZ· 2 mo ago
$79k–$134k/yrapply on ntrs.wd1.myworkdayjobs.com

Incident Commander

New York City Office of Technology & InnovationBrooklyn, NY· 2 mo ago
Information Technologyapply on cityjobs.nyc.gov