Support Lead, Americas
for headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate.
We need to extract content from posting.
First, "About Us" is not needed? It's about company; maybe we can include as part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include if posting has real specific content.
Let's parse.
About The Role: paragraph after "About The Role:" includes description. So we can put that in
About the role
with .
Responsibilities: There's a "Key Accountabilities" section with subheadings like PEAK support, Service Operations Leadership and Governance, etc. Also later "Key Responsibilities" bullet list. So we can combine responsibilities into a list.
Requirements: The posting includes "About You:" which lists required experience: "The successful candidate should have 5+ years of global enterprise accountability in: ..." That's requirements. Also "Required Skills And Capabilities" list. So we can treat those as Requirements and Skills maybe.
Qualifications: "Preferred Qualifications" list.
Skills: Could be from "Required Skills And Capabilities" maybe separate. But we already used that for Requirements. Might need separate Skills section. However we can decide to put Required Skills under Skills, and Requirements under Requirements (experience). Let's see.
The posting: "About You: The successful candidate should have 5+ years of global enterprise accountability in: IT Service Operations.Major Incident Management.Incident, Problem, Change, and Request Management.Service Integration and Management (SIAM).Supplier and vendor management.Operational governance and risk management.Enterprise service management.IT operations transformation.ServiceNow and IT service management tooling.Global technology support environments.AI-enabled service operations and automation initiatives."
That's like required experience/qualifications.
Then "Required Skills And Capabilities" list: Strong operational leadership capability.Deep knowledge of ITIL service management practices.Experience leading major incident response activities.Strong understanding of service integration principles.Good understanding of AIOps, observability, and operational analytics.Strong stakeholder and supplier management skills.Excellent written and verbal communication skills.Strong analytical and problem-solving abilities.Ability to influence without direct authority.Strong risk management and control mindset.Ability to remain effective and make sound decisions under pressure.
That's skills.
Then "Preferred Qualifications" list: ITIL Foundation or higher.SIAM Foundation or SIAM Professional.ServiceNow certification.Experience with ServiceNow AI capabilities.Experience with observability, monitoring, or event management platforms.Experience leading global operational teams.Experience implementing automation and AIOps solutions.
That's qualifications.
Benefits: There's a Benefits section with subpoints: Financial Benefits, Lifestyle Benefits, Health Benefits. So we can include Benefits.
Pay: Salary: $100,000-$125,000 annually + bonus opportunity. So Pay section.
Schedule: Not explicitly mentioned. There's mention of follow-the-sun, 24x7 operating model and may require participation in on-call arrangements or coverage during peak periods, weekends, and public holidays. That's schedule info. So we can include Schedule section with that detail.
Now we need to avoid boilerplate like EEO etc. Remove those.
Now produce HTML fragment.
Structure:
About the role
... (the paragraph)
Responsibilities
- ... list items from Key Accountabilities and Key Responsibilities maybe combined.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include each responsibility item as separate - . Let's extract.
From Key Accountabilities:
PEAK support Ensure Dyson's most business-critical services remain stable, available, performant, and fully supported throughout periods of exceptional business demand, minimizing operational risk and protecting revenue, employee productivity, and customer experience.
Responsibilities Include:
- Peak Readiness Planning
- Operational Command and Control
- Capacity and Performance Management
- Major Incident Management During Peak
- Supplier and Partner Coordination
- Business Stakeholder Engagement
- Monitoring, Reporting and Analytics
Service Operations Leadership and Governance Responsible for day-to-day leadership of production service operations.
Responsibilities Include:
- Maintain governance across service operations activities.
- Ensure operational risks are identified, owned, and managed.
- Coordinate cross-functional operational decision-making.
- Act as a senior escalation point for service issues and complaints.
- Drive operational consistency across internal and partner support functions.
- Promote operational excellence, clear ownership, and accountability.
Major Incident and Service Restoration Management Ensure rapid and controlled restoration of business services during operational disruption.
Responsibilities Include:
- Coordinate major incident management activities.
- Lead multi-team and multi-supplier service recovery efforts during critical incidents.
- Facilitate timely stakeholder communication during outages.
- Ensure incident ownership remains clear throughout restoration.
- Validate restoration actions, workarounds, and recovery plans.
- Drive post-incident reviews, learning, and remediation.
Operational Performance and Service Health Maintain clear visibility and control of operational performance.
Responsibilities Include:
- Monitor service performance, availability, and operational health.
- Review key performance indicators and service-level performance.
- Identify service degradation, recurring failure, and demand trends.
- Coordinate proactive remediation activities.
- Produce operational reporting, insights, and management information.
- Support executive and business service reviews.
AI-Enabled Operations and Automation Drive adoption of automation and AI capabilities across service operations.
Responsibilities Include:
- Define and prioritize an operational automation pipeline.
- Support implementation and operationalization of AIOps capabilities.
- Expand self-service, virtual agent, and knowledge automation adoption.
- Drive ticket eradication, deflection, and shift-left opportunities.
- Support automated remediation and intelligent workflow initiatives.
- Measure automation effectiveness, value realization, and operational risk.
Incident, Problem, Change and Request Process Governance Ensure operational processes remain effective, controlled, and compliant.
Responsibilities Include:
- Govern Incident Management execution and process exceptions.
- Drive effective Problem Management and root-cause follow-through.
- Support production Change Management decisions and operational acceptance.
- Ensure Service Request fulfilment remains efficient and user-focused.
- Identify process compliance issues and control gaps.
- Drive process maturity and continual improvement.
Supplier and Service Integration Management Ensure internal teams and suppliers collaborate effectively to deliver end-to-end service outcomes.
Responsibilities Include:
- Coordinate operational supplier activities and dependencies.
- Facilitate multi-supplier service restoration and decision-making.
- Challenge supplier performance, ownership, and behaviours where required.
- Support operational governance and performance reviews.
- Escalate material supplier risks and service concerns.
- Promote end-to-end service accountability across the delivery ecosystem.
Continual Improvement and Service Transformation Drive ongoing improvement of service operations capabilities.
Responsibilities Include:
- Identify service improvement opportunities using operational data and user insight.
- Analyze performance, incident, problem, event, and demand trends.
- Drive implementation and tracking of improvement initiatives.
- Promote predictive analytics, observability, and proactive operations.
- Support operational transformation programmes and new service introductions.
- Benchmark capabilities against leading industry practice.
Then later "Key Responsibilities" list:
- Lead day-to-day service operations activities.
- Coordinate major incident management and service recovery.
- Govern Incident, Problem, Change, and Request processes.
- Manage operational escalations and process exceptions.
- Drive operational automation, AIOps, and AI initiatives.
- Produce operational reporting and actionable insights.
- Manage operational supplier performance and integration.
- Facilitate service reviews and governance forums.
- Support business-critical service continuity and resilience requirements.
- Drive operational excellence across global support functions.
- Promote continual improvement and service optimisation.
And "Key Deliverables" list (maybe not responsibilities but deliverables). Could be included under Responsibilities? Might be considered responsibilities but they are deliverables. The instruction: preserve ALL substantive information. Could include them under Responsibilities as well, but they are deliverables. Might be better to include them under Responsibilities as they are part of role. However we already have many items; adding deliverables may be redundant but still substantive. We'll include them as part of Responsibilities.
Key Deliverables:
- Global Service Operations Reporting.
- Major Incident Governance Framework.
- Operational Performance Dashboards.
- Service Health Reviews.
- AI Operations Adoption Roadmap.
- Automation Opportunity Register and Value Pipeline.
- Service Improvement Plans.
- Operational Risk Register.
- Supplier Performance Reviews.
- Major Incident Post-Incident Review Reports.
- Executive Operational Reporting.
- Annual Service Operations Improvement Plan.
We'll include these as list items.
Now Requirements: from About You list.
We need to preserve each item as separate
- . The list is comma-separated but we can split.
Items:
- IT Service Operations
- Major Incident Management
- Incident, Problem, Change, and Request Management
- Service Integration and Management (SIAM)
- Supplier and vendor management
- Operational governance and risk management
- Enterprise service management
- IT operations transformation
- ServiceNow and IT service management tooling
- Global technology support environments
- AI-enabled service operations and automation initiatives
We'll list each.
Skills: from Required Skills And Capabilities list.
Items:
- Strong operational leadership capability.
- Deep knowledge of ITIL service management practices.
- Experience leading major incident response activities.
- Strong understanding of service integration principles.
- Good understanding of AIOps, observability, and operational analytics.
- Strong stakeholder and supplier management skills.
- Excellent written and verbal communication skills.
- Strong analytical and problem-solving abilities.
- Ability to influence without direct authority.
- Strong risk management and control mindset.
- Ability to remain effective and make sound decisions under pressure.
Qualifications: Preferred Qualifications list.
Items:
- ITIL Foundation or higher.
- SIAM Foundation or SIAM Professional.
- ServiceNow certification.
- Experience with ServiceNow AI capabilities.
- Experience with observability, monitoring, or event management platforms.
- Experience leading global operational teams.
- Experience implementing automation and AIOps solutions.
Benefits: we have Financial Benefits, Lifestyle Benefits, Health Benefits with subitems.
We need to preserve all substantive information. So we can create a
with sub-items maybe nested? But instruction: Use - for any list of duties/requirements/benefits. So we can just list each benefit as a top-level
- . Could also group but okay.
Financial Benefits:
- 401K with up to a 4% match
- Company paid Life Insurance and AD&D
- Flexible Savings Account (FSA) and Health Savings Account (HSA)
Lifestyle Benefits:
- Competitive Paid Time Off Benefits including Separate Holiday, Sick, and Vacation Time
- Pre-tax Commuter Benefits (applicable areas only)
- Generous Child Care Leave Program
- Wellness Program
- Employee Assistance Program
- Dyson Product Discounts
Health Benefits:
- Multi-Level Healthcare Coverage Options
- Vision & Dental Coverage
- Company paid Short-Term and Long-Term Disability
We'll list each as
- .
Pay: Salary: $100,000-$125,000 annually + bonus opportunity.
Schedule: mention follow-the-sun, 24x7 operating model and may require participation in on-call arrangements or coverage during peak periods, weekends, and public holidays.
Now ensure we don't include boilerplate like EEO etc.
Now produce HTML.
We need to output only HTML fragment, no /, no markdown.
Let's craft.
We'll start with
About the role
... paragraph
Paragraph: The Support Lead, Americas is responsible for the governance, coordination, operation, and continual improvement of D
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. We need to extract content from posting. First, "About Us" is not needed? It's about company; maybe we can include as part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include if posting has real specific content. Let's parse. About The Role: paragraph after "About The Role:" includes description. So we can put that in
About the role
with. Responsibilities: There's a "Key Accountabilities" section with subheadings like PEAK support, Service Operations Leadership and Governance, etc. Also later "Key Responsibilities" bullet list. So we can combine responsibilities into a list. Requirements: The posting includes "About You:" which lists required experience: "The successful candidate should have 5+ years of global enterprise accountability in: ..." That's requirements. Also "Required Skills And Capabilities" list. So we can treat those as Requirements and Skills maybe. Qualifications: "Preferred Qualifications" list. Skills: Could be from "Required Skills And Capabilities" maybe separate. But we already used that for Requirements. Might need separate Skills section. However we can decide to put Required Skills under Skills, and Requirements under Requirements (experience). Let's see. The posting: "About You: The successful candidate should have 5+ years of global enterprise accountability in: IT Service Operations.Major Incident Management.Incident, Problem, Change, and Request Management.Service Integration and Management (SIAM).Supplier and vendor management.Operational governance and risk management.Enterprise service management.IT operations transformation.ServiceNow and IT service management tooling.Global technology support environments.AI-enabled service operations and automation initiatives." That's like required experience/qualifications. Then "Required Skills And Capabilities" list: Strong operational leadership capability.Deep knowledge of ITIL service management practices.Experience leading major incident response activities.Strong understanding of service integration principles.Good understanding of AIOps, observability, and operational analytics.Strong stakeholder and supplier management skills.Excellent written and verbal communication skills.Strong analytical and problem-solving abilities.Ability to influence without direct authority.Strong risk management and control mindset.Ability to remain effective and make sound decisions under pressure. That's skills. Then "Preferred Qualifications" list: ITIL Foundation or higher.SIAM Foundation or SIAM Professional.ServiceNow certification.Experience with ServiceNow AI capabilities.Experience with observability, monitoring, or event management platforms.Experience leading global operational teams.Experience implementing automation and AIOps solutions. That's qualifications. Benefits: There's a Benefits section with subpoints: Financial Benefits, Lifestyle Benefits, Health Benefits. So we can include Benefits. Pay: Salary: $100,000-$125,000 annually + bonus opportunity. So Pay section. Schedule: Not explicitly mentioned. There's mention of follow-the-sun, 24x7 operating model and may require participation in on-call arrangements or coverage during peak periods, weekends, and public holidays. That's schedule info. So we can include Schedule section with that detail. Now we need to avoid boilerplate like EEO etc. Remove those. Now produce HTML fragment. Structure:
About the role
... (the paragraph)
Responsibilities
- ... list items from Key Accountabilities and Key Responsibilities maybe combined.
- with sub-items maybe nested? But instruction: Use
- for any list of duties/requirements/benefits. So we can just list each benefit as a top-level
- . Could also group but okay. Financial Benefits: - 401K with up to a 4% match - Company paid Life Insurance and AD&D - Flexible Savings Account (FSA) and Health Savings Account (HSA) Lifestyle Benefits: - Competitive Paid Time Off Benefits including Separate Holiday, Sick, and Vacation Time - Pre-tax Commuter Benefits (applicable areas only) - Generous Child Care Leave Program - Wellness Program - Employee Assistance Program - Dyson Product Discounts Health Benefits: - Multi-Level Healthcare Coverage Options - Vision & Dental Coverage - Company paid Short-Term and Long-Term Disability We'll list each as
- .
Pay: Salary: $100,000-$125,000 annually + bonus opportunity.
Schedule: mention follow-the-sun, 24x7 operating model and may require participation in on-call arrangements or coverage during peak periods, weekends, and public holidays.
Now ensure we don't include boilerplate like EEO etc.
Now produce HTML.
We need to output only HTML fragment, no /, no markdown.
Let's craft.
We'll start with
About the role
... paragraph
Paragraph: The Support Lead, Americas is responsible for the governance, coordination, operation, and continual improvement of D