Staff Infrastructure Engineer

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID. Must preserve all substantive info, remove boilerplate (EEO, etc). Must not create sections with filler like "commensurate with experience". Must not invent or summarize away detail. We need to parse the posting. Content: - Intro paragraph: "We’re determined to make a difference and are proud to be an insurance company that goes well beyond coverages and policies. Working here means having every opportunity to achieve your goals – and to help others accomplish theirs, too. Join our team as we help shape the future." - Then description: "The Staff Infrastructure Engineer is responsible for leveraging agentic AI to quickly identify, assess, and resolve critical service issues and major incidents, ensuring swift detection and response. The successful candidate will demonstrate engineering-level technical depth in AI, cloud computing concepts, and infrastructure platforms, partnering with cross-functional teams for service restoration and continuously improving the event management process. This position is critical in enhancing enterprise resilience and implementing proactive AI-driven operations within the Technology Command Center." - Then: "This role will have a Hybrid work schedule, with the expectation of working in an office (Hartford, CT or Charlotte, NC) 3 days a week (Tuesday through Thursday)." - Then "Key Responsibilities" heading with bullet list. - Then "Partnership & Work Expectations" heading with bullet list. - Then "Schedule & Role Expectations" heading with bullet list. - Then "Required Qualifications" heading with bullet list. - Then "Compensation" paragraph with pay range and description. - Then EEO boilerplate to remove. We need sections: About the role (intro), Responsibilities (Key Responsibilities + Partnership & Work Expectations? Actually Partnership & Work Expectations maybe part of responsibilities but could be separate "Responsibilities" section. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: - About the role: intro paragraphs. - Responsibilities: combine Key Responsibilities and Partnership & Work Expectations? Might be better to have Responsibilities (Key Responsibilities) and maybe another section like "Partnership & Work Expectations" but not in list. Since only allowed headings are those listed, we should not create extra headings like Partnership & Work Expectations. So we should incorporate that content under Responsibilities or maybe under Requirements? Probably Responsibilities. - Requirements: maybe "Required Qualifications" is Requirements? Actually they have Required Qualifications. Could map to Requirements or Qualifications. The list includes both Requirements and Qualifications as possible headings. We need to decide. The posting has "Required Qualifications". Could map to Qualifications section. Requirements could be maybe "Required Qualifications" as well. But we have both Requirements and Qualifications headings available. We could put the qualifications under Qualifications, and maybe Requirements could be empty? But we must not emit a heading followed by filler/placeholder text. So we should only include sections that have real content. So we can include Qualifications (for Required Qualifications). For Requirements, maybe we could put something like "Required experience" but we don't have a separate section. Could we treat Required Qualifications as Requirements? The list includes both; we can choose to use Qualifications for the qualifications, and maybe Requirements for something else like "Required Qualifications"? But that would duplicate. Better to use Qualifications for the Required Qualifications, and maybe Requirements for something like "Required experience in monitoring and observability tools"? But that's also part of qualifications. Since we must not create empty sections, we should only include sections we have content for: About the role, Responsibilities, Qualifications, Pay, Schedule. Possibly also Benefits? Not mentioned. Skills? Not explicitly separate; could be part of Qualifications. But we could create a Skills section if we have specific skills listed: AI tool proficiency, prompt engineering, interrogation skills, familiarity with ITSM, understanding of event correlation, etc. Those could be skills. However the instruction: Prefer a few substantive sections over many thin ones. So maybe combine skills into Qualifications. Thus sections: About the role, Responsibilities, Qualifications, Pay, Schedule. We need to preserve all substantive information. Let's extract. About the role: combine the intro paragraphs and the description of role responsibilities high-level. Paragraphs: 1. "We’re determined to make a difference and are proud to be an insurance company that goes well beyond coverages and policies. Working here means having every opportunity to achieve your goals – and to help others accomplish theirs, too. Join our team as we help shape the future." 2. "The Staff Infrastructure Engineer is responsible for leveraging agentic AI to quickly identify, assess, and resolve critical service issues and major incidents, ensuring swift detection and response. The successful candidate will demonstrate engineering-level technical depth in AI, cloud computing concepts, and infrastructure platforms, partnering with cross-functional teams for service restoration and continuously improving the event management process. This position is critical in enhancing enterprise resilience and implementing proactive AI-driven operations within the Technology Command Center." We could keep them as separate

elements. Responsibilities: combine Key Responsibilities and Partnership & Work Expectations. Key Responsibilities bullet list: - Manage technical and executive communication for major incidents. - Perform alert triage, correlation, and initial impact assessment to separate actionable events from non-actionable noise. - Support major incident detection and escalation by validating symptoms, confirming affected services, and engaging resolver teams. - Use standard operating procedures, runbooks, and decision frameworks to investigate, prioritize, and escalate events. - Maintain situational awareness during active events; document event patterns and operational observations. - Promote events to incidents when thresholds are met; partner with internal and external teams during restoration activities. - Identify opportunities to improve monitoring effectiveness, event quality, automation, and operational readiness. Partnership & Work Expectations bullet list: - Collaborate with infrastructure, application, reliability engineering, service desk, and vendor teams to ensure effective event response and service restoration. - Support continuous improvement by identifying recurring alert issues, documenting operational insights, and recommending enhancements to monitoring, runbooks, and automation. Schedule & Role Expectations bullet list: - May require shift coverage, off-hours support, and escalation activities aligned to a 24x7 operational model and follow-the-sun support structure. We could incorporate that under Responsibilities as well, or maybe under Schedule section. Since we have a Schedule section for work schedule (Hybrid, 3 days). The shift coverage etc is more about expectations, could be part of Responsibilities or a separate Schedule section? The instruction list includes Schedule as a possible heading for work schedule details. The shift coverage is about operational expectations, not the regular schedule. Could be placed under Responsibilities as well. We'll put all those bullet points under Responsibilities. Qualifications: Required Qualifications bullet list: - 8+ years' experience in monitoring and observability tools such as Splunk, Dynatrace, ITSI, Moogsoft, ThousandEyes, or similar. - Experience in AI-driven data analysis and problem solving. - AI tool proficiency including prompt engineering and Interrogation skills - Familiarity with ITSM and ticketing platforms, including incident creation, categorization, escalation, and documentation. - Understanding of event correlation, alert prioritization, service impact analysis, and basic automation/workflow enablement. - Strong analytical thinking and operational judgment. - Ability to work under pressure during high-impact events. - Candidate must be authorized to work in the US without company sponsorship. - The company will not support the STEM OPT I-983 Training Plan endorsement for this position. We need to preserve all substantive info. The last two about work authorization and STEM OPT are substantive; keep them. Pay: Compensation paragraph: "The listed annualized base pay range is primarily based on analysis of similar positions in the external market. Actual base pay could vary and may be above or below the listed range based on factors including but not limited to performance, proficiency and demonstration of competencies required for the role. The base pay is just one component of The Hartford’s total compensation package for employees. Other rewards may include short-term or annual bonuses, long-term incentives, and on-the-spot recognition. The annualized base pay range for this role is: $116,800 - $175,200" We should keep that as

under Pay heading. Schedule: Hybrid work schedule paragraph: "This role will have a Hybrid work schedule, with the expectation of working in an office (Hartford, CT or Charlotte, NC) 3 days a week (Tuesday through Thursday)." We could also mention shift coverage etc but that's already in Responsibilities. We must not include EEO boilerplate. Now produce HTML fragment with

headings and

or

• . We must not include or . Just the fragment. Let's craft:

  About the role

  We’re determined to make a difference and are proud to be an insurance company that goes well beyond coverages and policies. Working here means having every opportunity to achieve your goals – and to help others accomplish theirs, too. Join our team as we help shape the future.

  The Staff Infrastructure Engineer is responsible for leveraging agentic AI to quickly identify, assess, and resolve critical service issues and major incidents, ensuring swift detection and response. The successful candidate will demonstrate engineering-level technical depth in AI, cloud computing concepts, and infrastructure platforms, partnering with cross-functional teams for service restoration and continuously improving the event management process. This position is critical in enhancing enterprise resilience and implementing proactive AI-driven operations within the Technology Command Center.

  Responsibilities

  • Manage technical and executive communication for major incidents.
  • Perform alert triage, correlation, and initial impact assessment to separate actionable events from non-actionable noise.
  • Support major incident detection and escalation by validating symptoms, confirming affected services, and engaging resolver teams.
  • Use standard operating procedures, runbooks, and decision frameworks to investigate, prioritize, and escalate events.
  • Maintain situational awareness during active events; document event patterns and operational observations.
  • Promote events to incidents when thresholds are met; partner with internal and external teams during restoration activities.
  • Identify opportunities to improve monitoring effectiveness, event quality, automation, and operational readiness.
  • Collaborate with infrastructure, application, reliability engineering, service desk, and vendor teams to ensure effective event response and service restoration.
  • Support continuous improvement by identifying recurring alert issues, documenting operational insights, and recommending enhancements to monitoring, runbooks, and automation.
  • May require shift coverage, off-hours support, and escalation activities aligned to a 24x7 operational model and follow-the-sun support structure.

  Qualifications

  • 8+ years' experience in monitoring and observability tools such as Splunk, Dynatrace, ITSI, Moogsoft, ThousandEyes, or similar.
  • Experience in AI-driven data analysis and problem solving.
  • AI tool proficiency including prompt engineering and Interrogation skills
  • Familiarity with ITSM and ticketing platforms, including incident creation, categorization, escalation, and documentation.
  • Understanding of event correlation, alert prioritization, service impact analysis, and basic automation/workflow enablement.
  • Strong analytical thinking and operational judgment.
  • Ability to work under pressure during high-impact events.
  • Candidate must be authorized to work in the US without company sponsorship.
  • The company will not support the STEM OPT I-983 Training Plan endorsement for this position.

  Pay

  The listed annualized base pay range is primarily based on analysis of similar positions in the external market. Actual base pay could vary and may be above