Senior Enterprise Incident Manager/Commander
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role, Responsibilities, Qualifications (maybe combine min and preferred). Also Pay and Benefits sections if present. The posting includes compensation description and benefits details. So we need Pay section with salary range and maybe note about bonuses. Benefits section with listed benefits. Also Schedule: they mention shifting to fully in-person schedule up to 5 days a week. So we can include Schedule section.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove "About USDS TikTok USDS Joint Venture LLC..."? That is company description; maybe keep as part of About the role? Actually "About USDS TikTok USDS Joint Venture LLC is dedicated..." is about the company, not the role. Could be considered boilerplate? It's not about the role but maybe we can keep as part of About the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive? Might be considered part of the posting but not required for role. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not those. Might keep it under About the role? But we already have About the role section for role description. Could add a separate section like "About the Company" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit company description maybe under About the role? But About the role already has role description. Could we add a paragraph about company under About the role? Might be okay.
We must not create sections with filler like "commensurate with experience". Pay section: we have salary range. Benefits: we have details. Schedule: we have in-person schedule up to 5 days a week.
We need to use - for any list of duties/requirements/benefits. So Responsibilities list as
- . Qualifications maybe also list? Could be list but we can also use
for prose. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for qualifications we could list as
- . Benefits also list.
We must not include headings with empty content. Ensure each heading has real content.
Let's extract content.
About the role: The paragraph after "About the Role" (first paragraph) plus maybe the company description? Let's take the first paragraph: "The Senior Enterprise Incident Manager is responsible for leading the response to high-severity enterprise and operational incidents that may affect business continuity, customer trust, regulatory obligations, or executive priorities. This role combines strong incident command, technical depth, and executive communication. The ideal candidate brings substantial experience in the technology industry, a proven record of hands-on technical investigation and response, and the judgment to coordinate cross-functional teams during fast-moving, high-stakes events. This position partners closely with Security, Engineering, Infrastructure, Product, Legal, Compliance, Public Policy, Communications, and executive stakeholders to drive effective incident response, clear decision-making, and continuous improvement."
That's substantive.
Responsibilities: bullet list after "Responsibilities -". We'll extract each bullet.
Qualifications: Minium Qualifications (typo) and Preferred Qualifications. We'll combine maybe under Qualifications heading with two sub-sections? But we only allowed headings list; we could still have Qualifications heading and inside we can have paragraphs for minimum and preferred. Could also split into Requirements and Qualifications but we have only Qualifications. We'll put min qualifications as
- and preferred as another
- maybe under same heading but we need to differentiate. Could use
to label "Minimum Qualifications:" then list. That's okay.
Pay: compensation description. We'll put as
with salary range and note about bonuses.
Benefits: list of benefits: medical, dental, vision insurance, 401(k) match, paid parental leave, short-term and long-term disability, life insurance, wellbeing benefits, 10 paid holidays, 10 paid sick days, 17 days Paid Personal Time (prorated). Also note that benefits may vary etc. We'll include as list.
Schedule: "As such, the company is shifting from a hybrid work model to a fully in-person schedule up to 5 days a week." We'll put as
.
We must not include duplicated lines. Also remove "Job Information 【For Pay Transparency】Compensation Description (Annually)" maybe just keep the content.
Let's craft HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Qualifications
Minimum Qualifications:
- ...
...
Preferred Qualifications:
- ...
...
Pay
The base salary range for this position is $199,800 - $374,400 annually. Compensation may vary depending on qualifications, skills, experience, and location. Base pay is part of the Total Package and may be eligible for additional discretionary bonuses/incentives and restricted stock units.
Benefits
- Medical, dental, and vision insurance (day‑one access)
- 401(k) savings plan with company match
- Paid parental leave
- Short‑term and long‑term disability coverage
- Life insurance
- Wellbeing benefits
- 10 paid holidays per year
- 10 paid sick days per year
- 17 days of Paid Personal Time (prorated upon hire with increasing accruals by tenure)
Schedule
The role requires a fully in‑person schedule, up to 5 days per week.
Check for any missing substantive info: The "About USDS TikTok USDS Joint Venture LLC" paragraph about mission etc. Could we include under About the role? Might be considered company description. Could add another paragraph after About the role? But we have no heading for company. Could we add a under About the role after the role description? That would mix. Might be okay to include as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." Adding company description under About the role may be okay.
Let's add a second paragraph under About the role: "USDS Joint Venture LLC is dedicated to the safety and security of millions of Americans who create, discover, and connect with what they love on the apps we operate. The Joint Venture has been established in compliance with the Executive Order signed by President Trump on September 25, 2025. Our foundation is a comprehensive data privacy and cybersecurity program we operate under defined safeguards to protect national security and secure U.S. user data, apps and the algorithm. We safeguard the U.S. content ecosystem, holding decision‑making authority for trust and safety policies and moderation. USDS Joint Venture helps ensure Americans can continue to express their creativity, discover new hobbies and interests, and build thriving communities and businesses on a global scale. On‑site presence across teams allows the company to operate with greater speed, alignment, and agility — especially in areas like real‑time decision‑making, team development, and integrated execution."
That's substantive.
Now ensure we didn't include boilerplate like "Diversity & Inclusion", "USDS Reasonable Accommodation", "Job Information", "For Los Angeles County..." etc. Those are boilerplate/legal; we should remove.
Also remove "Why Join Us", "Inspiring creativity..." etc. That's also boilerplate? Might be considered company culture but could be considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Join Us" is not exactly those but could be considered fluff. Safer to remove.
Thus final HTML fragment.
Check for any missing responsibilities: list them all.
Let's extract responsibilities bullets:
- Lead end-to-end command and coordination for high-severity enterprise incidents, including triage, escalation, stakeholder alignment, mitigation tracking, and resolution management.
- Serve as the central incident leader during complex or high-stakes events, ensuring the right technical and business teams are engaged quickly and operating against a clear response structure.
- Work hands-on with technical teams to investigate active incidents, analyze system behavior, review logs, validate hypotheses, identify dependencies, and support effective containment and recovery actions.
- Coordinate response activities across Engineering, Site Reliability, Security, Infrastructure, Product, Support, Legal, Compliance, Communications, and leadership teams.
- Drive high-quality executive communications during incidents, including concise status updates, decision memos, risk summaries, and post-incident briefings.
- Prepare and deliver incident reporting for executive leadership, board-level audiences, and government stakeholders when required, ensuring accuracy, clarity, and alignment with legal and regulatory expectations.
- Contribute to and adhere to incident playbooks, severity frameworks, escalation paths, communications standards, and operational playbooks.
- Facilitate incident reviews and postmortems, ensuring root causes, contributing factors, lessons learned, and remediation plans are clearly documented and tracked to completion.
- Identify trends across incidents and near misses to improve resilience, readiness, observability, escalation quality, and cross-functional response maturity.
- Improve the quality and speed of incident response by refining tooling, workflows, and metrics that support detection, coordination, reporting, and leadership visibility.
- Act as a trusted advisor during sensitive events where technical, business, regulatory, and reputational considerations must be balanced in real time.
Now qualifications:
Minimum Qualifications bullets:
- Bachelor’s degree or equivalent practical experience.
- Significant experience in the technology industry, with direct exposure to production operations, enterprise platforms, infrastructure, cybersecurity, or large-scale service environments. Demonstrated experience leading or coordinating major incident response in complex technical organizations.
- Strong hands-on technical experience investigating, responding to, and coordinating high-stakes incidents, including the ability to work effectively with engineers and technical operators. Experience analyzing incident data such as system events, operational signals, service dependencies, logs, timelines, and recovery actions to support response leadership and decision-making.
- Proven experience communicating incident status, business impact, and remediation plans to executive leadership, including senior operational or corporate stakeholders. Experience preparing or presenting incident-related updates, risk summaries, or formal reporting to boards and government stakeholders.
- Excellent written and verbal communication skills, with the ability to translate complex technical developments into clear business language for a range of audiences.
- Strong judgment, composure, and decision-making ability in ambiguous and time-sensitive situations. Experience building cross-functional trust and influencing technical and non-technical stakeholders without direct authority.
- Strong team management and operational discipline, including the ability to drive action items, owners, deadlines, and follow-through after incidents.
Preferred Qualifications bullets:
- Working knowledge of modern infrastructure, distributed systems, cloud environments, identity systems, networking, and security response concepts in enterprise incident management, cyber incident response, site reliability, production operations, or related technical risk functions.
- Familiarity with regulated or highly scrutinized operating environments where reporting quality, traceability, and stakeholder management are critical.
- Experience supporting crisis management programs, business continuity, or executive response frameworks. Track record of designing or improving incident management processes, operating models, governance structures, and executive briefing mechanisms.
Now benefits list as above.
Pay: include base salary range
- . Qualifications maybe also list? Could be list but we can also use
for prose. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for qualifications we could list as
- . Benefits also list.
We must not include headings with empty content. Ensure each heading has real content.
Let's extract content.
About the role: The paragraph after "About the Role" (first paragraph) plus maybe the company description? Let's take the first paragraph: "The Senior Enterprise Incident Manager is responsible for leading the response to high-severity enterprise and operational incidents that may affect business continuity, customer trust, regulatory obligations, or executive priorities. This role combines strong incident command, technical depth, and executive communication. The ideal candidate brings substantial experience in the technology industry, a proven record of hands-on technical investigation and response, and the judgment to coordinate cross-functional teams during fast-moving, high-stakes events. This position partners closely with Security, Engineering, Infrastructure, Product, Legal, Compliance, Public Policy, Communications, and executive stakeholders to drive effective incident response, clear decision-making, and continuous improvement."
That's substantive.
Responsibilities: bullet list after "Responsibilities -". We'll extract each bullet.
Qualifications: Minium Qualifications (typo) and Preferred Qualifications. We'll combine maybe under Qualifications heading with two sub-sections? But we only allowed headings list; we could still have Qualifications heading and inside we can have paragraphs for minimum and preferred. Could also split into Requirements and Qualifications but we have only Qualifications. We'll put min qualifications as
- and preferred as another
- maybe under same heading but we need to differentiate. Could use
to label "Minimum Qualifications:" then list. That's okay. Pay: compensation description. We'll put as
with salary range and note about bonuses. Benefits: list of benefits: medical, dental, vision insurance, 401(k) match, paid parental leave, short-term and long-term disability, life insurance, wellbeing benefits, 10 paid holidays, 10 paid sick days, 17 days Paid Personal Time (prorated). Also note that benefits may vary etc. We'll include as list. Schedule: "As such, the company is shifting from a hybrid work model to a fully in-person schedule up to 5 days a week." We'll put as
. We must not include duplicated lines. Also remove "Job Information 【For Pay Transparency】Compensation Description (Annually)" maybe just keep the content. Let's craft HTML. Structure:
About the role
...
Responsibilities
- ... ...
Qualifications
Minimum Qualifications:
- ... ...
Preferred Qualifications:
- ... ...
Pay
The base salary range for this position is $199,800 - $374,400 annually. Compensation may vary depending on qualifications, skills, experience, and location. Base pay is part of the Total Package and may be eligible for additional discretionary bonuses/incentives and restricted stock units.
Benefits
- Medical, dental, and vision insurance (day‑one access)
- 401(k) savings plan with company match
- Paid parental leave
- Short‑term and long‑term disability coverage
- Life insurance
- Wellbeing benefits
- 10 paid holidays per year
- 10 paid sick days per year
- 17 days of Paid Personal Time (prorated upon hire with increasing accruals by tenure)
Schedule
The role requires a fully in‑person schedule, up to 5 days per week.
Check for any missing substantive info: The "About USDS TikTok USDS Joint Venture LLC" paragraph about mission etc. Could we include under About the role? Might be considered company description. Could add another paragraph after About the role? But we have no heading for company. Could we add aunder About the role after the role description? That would mix. Might be okay to include as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." Adding company description under About the role may be okay. Let's add a second paragraph under About the role: "USDS Joint Venture LLC is dedicated to the safety and security of millions of Americans who create, discover, and connect with what they love on the apps we operate. The Joint Venture has been established in compliance with the Executive Order signed by President Trump on September 25, 2025. Our foundation is a comprehensive data privacy and cybersecurity program we operate under defined safeguards to protect national security and secure U.S. user data, apps and the algorithm. We safeguard the U.S. content ecosystem, holding decision‑making authority for trust and safety policies and moderation. USDS Joint Venture helps ensure Americans can continue to express their creativity, discover new hobbies and interests, and build thriving communities and businesses on a global scale. On‑site presence across teams allows the company to operate with greater speed, alignment, and agility — especially in areas like real‑time decision‑making, team development, and integrated execution." That's substantive. Now ensure we didn't include boilerplate like "Diversity & Inclusion", "USDS Reasonable Accommodation", "Job Information", "For Los Angeles County..." etc. Those are boilerplate/legal; we should remove. Also remove "Why Join Us", "Inspiring creativity..." etc. That's also boilerplate? Might be considered company culture but could be considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Join Us" is not exactly those but could be considered fluff. Safer to remove. Thus final HTML fragment. Check for any missing responsibilities: list them all. Let's extract responsibilities bullets: - Lead end-to-end command and coordination for high-severity enterprise incidents, including triage, escalation, stakeholder alignment, mitigation tracking, and resolution management. - Serve as the central incident leader during complex or high-stakes events, ensuring the right technical and business teams are engaged quickly and operating against a clear response structure. - Work hands-on with technical teams to investigate active incidents, analyze system behavior, review logs, validate hypotheses, identify dependencies, and support effective containment and recovery actions. - Coordinate response activities across Engineering, Site Reliability, Security, Infrastructure, Product, Support, Legal, Compliance, Communications, and leadership teams. - Drive high-quality executive communications during incidents, including concise status updates, decision memos, risk summaries, and post-incident briefings. - Prepare and deliver incident reporting for executive leadership, board-level audiences, and government stakeholders when required, ensuring accuracy, clarity, and alignment with legal and regulatory expectations. - Contribute to and adhere to incident playbooks, severity frameworks, escalation paths, communications standards, and operational playbooks. - Facilitate incident reviews and postmortems, ensuring root causes, contributing factors, lessons learned, and remediation plans are clearly documented and tracked to completion. - Identify trends across incidents and near misses to improve resilience, readiness, observability, escalation quality, and cross-functional response maturity. - Improve the quality and speed of incident response by refining tooling, workflows, and metrics that support detection, coordination, reporting, and leadership visibility. - Act as a trusted advisor during sensitive events where technical, business, regulatory, and reputational considerations must be balanced in real time. Now qualifications: Minimum Qualifications bullets: - Bachelor’s degree or equivalent practical experience. - Significant experience in the technology industry, with direct exposure to production operations, enterprise platforms, infrastructure, cybersecurity, or large-scale service environments. Demonstrated experience leading or coordinating major incident response in complex technical organizations. - Strong hands-on technical experience investigating, responding to, and coordinating high-stakes incidents, including the ability to work effectively with engineers and technical operators. Experience analyzing incident data such as system events, operational signals, service dependencies, logs, timelines, and recovery actions to support response leadership and decision-making. - Proven experience communicating incident status, business impact, and remediation plans to executive leadership, including senior operational or corporate stakeholders. Experience preparing or presenting incident-related updates, risk summaries, or formal reporting to boards and government stakeholders. - Excellent written and verbal communication skills, with the ability to translate complex technical developments into clear business language for a range of audiences. - Strong judgment, composure, and decision-making ability in ambiguous and time-sensitive situations. Experience building cross-functional trust and influencing technical and non-technical stakeholders without direct authority. - Strong team management and operational discipline, including the ability to drive action items, owners, deadlines, and follow-through after incidents. Preferred Qualifications bullets: - Working knowledge of modern infrastructure, distributed systems, cloud environments, identity systems, networking, and security response concepts in enterprise incident management, cyber incident response, site reliability, production operations, or related technical risk functions. - Familiarity with regulated or highly scrutinized operating environments where reporting quality, traceability, and stakeholder management are critical. - Experience supporting crisis management programs, business continuity, or executive response frameworks. Track record of designing or improving incident management processes, operating models, governance structures, and executive briefing mechanisms. Now benefits list as above. Pay: include base salary range
- maybe under same heading but we need to differentiate. Could use
- and preferred as another
- . Benefits also list.
We must not include headings with empty content. Ensure each heading has real content.
Let's extract content.
About the role: The paragraph after "About the Role" (first paragraph) plus maybe the company description? Let's take the first paragraph: "The Senior Enterprise Incident Manager is responsible for leading the response to high-severity enterprise and operational incidents that may affect business continuity, customer trust, regulatory obligations, or executive priorities. This role combines strong incident command, technical depth, and executive communication. The ideal candidate brings substantial experience in the technology industry, a proven record of hands-on technical investigation and response, and the judgment to coordinate cross-functional teams during fast-moving, high-stakes events. This position partners closely with Security, Engineering, Infrastructure, Product, Legal, Compliance, Public Policy, Communications, and executive stakeholders to drive effective incident response, clear decision-making, and continuous improvement."
That's substantive.
Responsibilities: bullet list after "Responsibilities -". We'll extract each bullet.
Qualifications: Minium Qualifications (typo) and Preferred Qualifications. We'll combine maybe under Qualifications heading with two sub-sections? But we only allowed headings list; we could still have Qualifications heading and inside we can have paragraphs for minimum and preferred. Could also split into Requirements and Qualifications but we have only Qualifications. We'll put min qualifications as
- for any list of duties/requirements/benefits, and