AIOps & Observability Lead
for section headings. Use - for lists. Use
for prose. Do not repeat job title. No Job ID. Remove boilerplate. Need to preserve all substantive info.
We need to parse the posting: It includes Role Summary, Key Responsibilities, Required Qualifications, Preferred Qualifications, Success Profile, base salary range, benefits description, About Bessemer Trust, Key Facts, About Our Employee Rewards And Benefits, etc.
We need to decide which sections to include: About the role? The posting has "Role Summary". Could map to "About the role". Responsibilities: "Key Responsibilities". Requirements/Qualifications: "Required Qualifications". Skills? Not explicit but could be part of qualifications. Benefits: there is benefits description. Pay: salary range. Schedule? Not mentioned. So we may not include Schedule.
We need to include sections only when posting has real specific content. So we can have:
- About the role (from Role Summary)
- Responsibilities (Key Responsibilities)
- Requirements (Required Qualifications)
- Preferred Qualifications (maybe as Skills? but we can include as a separate section "Preferred Qualifications" if we want; but headings list includes Skills, Benefits, Pay, Schedule. Not Preferred Qualifications. However we could put preferred qualifications under Skills or Requirements? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive. So we can add other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But we can also include other headings if needed? Safer to stick to those. We can map Preferred Qualifications under Skills or Qualifications. Could combine Required and Preferred under Qualifications? But they said "Qualifications" heading. Could have Required Qualifications under Qualifications, and Preferred under Skills? Might be okay.
Better: Use "Qualifications" for Required Qualifications. Use "Skills" for Preferred Qualifications (since they are skills/experience). Use "Benefits" for benefits description. Use "Pay" for salary range. Use "About the role" for Role Summary. Use "Responsibilities" for Key Responsibilities. Possibly also include "Success Profile" maybe under About the role? Could be separate but not in list. Could incorporate into About the role as prose.
We must not invent sections with filler. So we need to ensure each heading has substantive content.
Let's extract content:
Role Summary paragraph: "We are building a new Operations function and need a hands-on, technical leader to set the direction for our AIOps and observability strategy. This is a player-coach role, weighted toward player: someone who works directly in the tools, not just the roadmap. Our new Splunk Observability implementation is a foundation of a broader automated operational intelligence ecosystem. We will lean on managed-service partners to act as first-line "eyes on glass" for the alerts and events it generates — but this role owns the strategy, architecture, and quality behind what those partners are watching. The goal is not just detection; it's ensuring issues can be discovered, triaged, and resolved through tooling and automation, reducing L3 engineer escalations wherever possible. The role could expand over time into desktop/endpoint observability, including a Nexthink implementation."
That's substantive.
Key Responsibilities: list of bullet points (each starts with a verb). We need to put them in - . Let's extract each bullet:
- Define and own the observability and event management strategy, stack, and processes, including how major incidents are detected, triaged, and resolved.
- Lead the rollout of Splunk Observability across our application and infrastructure portfolio, driving onboarding, instrumentation, and coverage expansion.
- Lead implementation of event management tooling — such as, BigPanda, Splunk ITSI, or PagerDuty — to correlate, prioritize, and route alerts from Splunk Observability.
- Coach and enable the Automation team to become proficient in the observability and event intelligence platform, including alert logic, dashboard creation, event enrichment, correlation workflows, triggered automations, MCP-style integrations, and runbook automation.
- Partner with the Infrastructure Architect to build a roadmap toward first-class, enterprise-grade observability.
- Develop and execute an AIOps strategy that turns telemetry into HITL-automated, self-healing operations — evaluating and building on tooling in Splunk, AWS, or elsewhere as appropriate.
- Stand up and mature an AIOps/SRE capability: automated remediation, intelligent alert correlation, and reduced manual triage.
- Direct managed-service partners providing "eyes on glass" monitoring — defining what they watch, how they escalate, and holding them accountable to SLAs.
- Design escalation paths so that issues resolvable via tooling are handled there first, protecting L3 engineering time for what truly needs it.
- Establish standards for event classification, severity, ownership, suppression, and closure across the environment.
- Assess and help scope the expansion into desktop/endpoint observability, including a Nexthink implementation.
- Ensure dashboards, alerts, and event workflows are built around operational decisions, not just technical visibility.
- Align observability, event management, incident, problem, change, knowledge, and escalation workflows with ITIL/ITSM practices and ServiceNow processes.
That's many items.
Required Qualifications: list:
- Strong, hands-on experience with observability, monitoring, and event management platforms (e.g., Splunk, Splunk ITSI, BigPanda, PagerDuty).
- Proven experience designing and implementing AIOps or event-intelligence capabilities — alert correlation, noise reduction, and automation.
- Experience defining incident management processes, including major incident response and escalation design.
- Comfortable operating as both strategic lead and hands-on technical contributor — able to shape direction and work directly in the tools.
- Scripting or automation experience (e.g., Python, PowerShell, REST APIs) to support event enrichment and automated remediation.
- Strong communication skills, with the ability to align infrastructure, application, and operations teams around a shared observability strategy.
Preferred Qualifications:
- Experience with AWS or other cloud-native observability and automation tooling.
- Experience with endpoint/desktop observability platforms such as Nexthink.
- ITIL/ITSM familiarity, particularly incident, problem, and change management.
- Experience managing or directing managed-service/outsourced monitoring partners.
- Experience in regulated, high-availability, or large-scale enterprise environments.
Success Profile: paragraph: "The right person has been in the room during major incidents, knows what a noisy, low-trust alerting environment looks like, and knows what it takes to fix it. They can set a multi-year observability direction and also configure the tool themselves when needed. Success looks like fewer incidents reaching L3, faster time-to-resolution, and an Operations function that trusts its own data."
Pay: "The base salary range for this position is $140,000 - $180,000 per year. This range reflects the minimum and maximum base salary we reasonably expect to pay for this role. In addition, this position may be eligible to participate in the relevant business unit’s incentive compensation plan, and other compensation programs as applicable."
Benefits: "Eligible employees may participate in a 401(k) program with a generous profit-sharing contribution, medical, prescription dental, and vision coverage; life insurance; disability coverage; paid holidays; vacation; and sick time, subject to plan terms and Company policies."
Then there is "About Bessemer Trust" and "Key Facts" and "About Our Employee Rewards And Benefits". Those are company description; could be considered "About the company" but not in headings list. Might be optional to include? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The headings list is just examples; we could add "About the company" if we want, but better to stick to given headings. However we have substantive content about company; maybe we can include under "About the role"? Not appropriate. Could we add a section "About the company"? Not in list but maybe allowed as e.g. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive. So we could add other headings like "About the company". But to be safe, we could incorporate that info into "About the role" or maybe omit as not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company description. If we omit a heading for it, we lose that info. So we need a heading for it. Could use "About the company". That seems reasonable.
Similarly "Key Facts" and "About Our Employee Rewards And Benefits" could be merged into "About the company" or separate "Company Overview" and "Benefits". But we already have Benefits heading for employee benefits. The company description about Bessemer Trust is separate from benefits. So we need a section for company overview.
Thus headings: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, About the company (or Company Overview). Schedule not present, omit.
We must not repeat job title. No Job ID.
Now format:
About the role
Role Summary paragraph.
Responsibilities
- ... each bullet
Qualifications
- Required Qualifications bullets
Skills
- Preferred Qualifications bullets
Benefits
Benefits paragraph.
Pay
Pay paragraph.
About the company
About Bessemer Trust paragraph(s) plus Key Facts and About Our Employee Rewards And Benefits? Actually the latter is about benefits again; we already have Benefits heading for employee benefits. The "About Our Employee Rewards And Benefits" repeats benefits info; we could include that under Benefits as well, but we already have benefits paragraph. Might duplicate. Better to combine: Benefits section includes both the earlier benefits paragraph and the "About Our Employee Rewards And Benefits" content. But we must not invent filler; we can combine them.
Thus Benefits section: combine the two paragraphs about benefits.
Let's extract benefits paragraphs:
First: "Eligible employees may participate in a 401(k) program with a generous profit-sharing contribution, medical, prescription dental, and vision coverage; life insurance; disability coverage; paid holidays; vacation; and sick time, subject to plan terms and Company policies."
Second: "We provide exceptional rewards and benefits that are among the best in the industry, giving our people access to a wide range of options, including: Competitive base salary plus discretionary annual bonus for select positions A 401(k) plan with a generous annual profit-sharing contribution Personalized development and career opportunities, including tuition reimbursement support Comprehensive medical, dental, and vision plans with zero contributions for employee coverage Employee assistance (EAP) and wellness programs Hybrid work environment: 60% in office, 40% remote for most positions Paid time off and paid parental leave Employer-paid life insurance and short- and long-term disability coverage Legal services and financial wellness plans at no cost to employees Bessemer Trust is committed to creating a diverse and inclusive environment and is proud to be an equal opportunity employer. We encourage candidates of diverse backgrounds to apply."
We should keep all that.
Now About the company: Bessemer Trust description and Key Facts.
Extract Bessemer Trust paragraph: "About Bessemer Trust Bessemer Trust is a family office, overseeing $250 billion in assets for over 3,000 individuals and families of substantial wealth.
for prose. Do not repeat job title. No Job ID. Remove boilerplate. Need to preserve all substantive info. We need to parse the posting: It includes Role Summary, Key Responsibilities, Required Qualifications, Preferred Qualifications, Success Profile, base salary range, benefits description, About Bessemer Trust, Key Facts, About Our Employee Rewards And Benefits, etc. We need to decide which sections to include: About the role? The posting has "Role Summary". Could map to "About the role". Responsibilities: "Key Responsibilities". Requirements/Qualifications: "Required Qualifications". Skills? Not explicit but could be part of qualifications. Benefits: there is benefits description. Pay: salary range. Schedule? Not mentioned. So we may not include Schedule. We need to include sections only when posting has real specific content. So we can have: - About the role (from Role Summary) - Responsibilities (Key Responsibilities) - Requirements (Required Qualifications) - Preferred Qualifications (maybe as Skills? but we can include as a separate section "Preferred Qualifications" if we want; but headings list includes Skills, Benefits, Pay, Schedule. Not Preferred Qualifications. However we could put preferred qualifications under Skills or Requirements? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive. So we can add other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But we can also include other headings if needed? Safer to stick to those. We can map Preferred Qualifications under Skills or Qualifications. Could combine Required and Preferred under Qualifications? But they said "Qualifications" heading. Could have Required Qualifications under Qualifications, and Preferred under Skills? Might be okay.
Better: Use "Qualifications" for Required Qualifications. Use "Skills" for Preferred Qualifications (since they are skills/experience). Use "Benefits" for benefits description. Use "Pay" for salary range. Use "About the role" for Role Summary. Use "Responsibilities" for Key Responsibilities. Possibly also include "Success Profile" maybe under About the role? Could be separate but not in list. Could incorporate into About the role as prose.
We must not invent sections with filler. So we need to ensure each heading has substantive content.
Let's extract content:
Role Summary paragraph: "We are building a new Operations function and need a hands-on, technical leader to set the direction for our AIOps and observability strategy. This is a player-coach role, weighted toward player: someone who works directly in the tools, not just the roadmap. Our new Splunk Observability implementation is a foundation of a broader automated operational intelligence ecosystem. We will lean on managed-service partners to act as first-line "eyes on glass" for the alerts and events it generates — but this role owns the strategy, architecture, and quality behind what those partners are watching. The goal is not just detection; it's ensuring issues can be discovered, triaged, and resolved through tooling and automation, reducing L3 engineer escalations wherever possible. The role could expand over time into desktop/endpoint observability, including a Nexthink implementation."
That's substantive.
Key Responsibilities: list of bullet points (each starts with a verb). We need to put them in - . Let's extract each bullet:
- Define and own the observability and event management strategy, stack, and processes, including how major incidents are detected, triaged, and resolved.
- Lead the rollout of Splunk Observability across our application and infrastructure portfolio, driving onboarding, instrumentation, and coverage expansion.
- Lead implementation of event management tooling — such as, BigPanda, Splunk ITSI, or PagerDuty — to correlate, prioritize, and route alerts from Splunk Observability.
- Coach and enable the Automation team to become proficient in the observability and event intelligence platform, including alert logic, dashboard creation, event enrichment, correlation workflows, triggered automations, MCP-style integrations, and runbook automation.
- Partner with the Infrastructure Architect to build a roadmap toward first-class, enterprise-grade observability.
- Develop and execute an AIOps strategy that turns telemetry into HITL-automated, self-healing operations — evaluating and building on tooling in Splunk, AWS, or elsewhere as appropriate.
- Stand up and mature an AIOps/SRE capability: automated remediation, intelligent alert correlation, and reduced manual triage.
- Direct managed-service partners providing "eyes on glass" monitoring — defining what they watch, how they escalate, and holding them accountable to SLAs.
- Design escalation paths so that issues resolvable via tooling are handled there first, protecting L3 engineering time for what truly needs it.
- Establish standards for event classification, severity, ownership, suppression, and closure across the environment.
- Assess and help scope the expansion into desktop/endpoint observability, including a Nexthink implementation.
- Ensure dashboards, alerts, and event workflows are built around operational decisions, not just technical visibility.
- Align observability, event management, incident, problem, change, knowledge, and escalation workflows with ITIL/ITSM practices and ServiceNow processes.
That's many items.
Required Qualifications: list:
- Strong, hands-on experience with observability, monitoring, and event management platforms (e.g., Splunk, Splunk ITSI, BigPanda, PagerDuty).
- Proven experience designing and implementing AIOps or event-intelligence capabilities — alert correlation, noise reduction, and automation.
- Experience defining incident management processes, including major incident response and escalation design.
- Comfortable operating as both strategic lead and hands-on technical contributor — able to shape direction and work directly in the tools.
- Scripting or automation experience (e.g., Python, PowerShell, REST APIs) to support event enrichment and automated remediation.
- Strong communication skills, with the ability to align infrastructure, application, and operations teams around a shared observability strategy.
Preferred Qualifications:
- Experience with AWS or other cloud-native observability and automation tooling.
- Experience with endpoint/desktop observability platforms such as Nexthink.
- ITIL/ITSM familiarity, particularly incident, problem, and change management.
- Experience managing or directing managed-service/outsourced monitoring partners.
- Experience in regulated, high-availability, or large-scale enterprise environments.
Success Profile: paragraph: "The right person has been in the room during major incidents, knows what a noisy, low-trust alerting environment looks like, and knows what it takes to fix it. They can set a multi-year observability direction and also configure the tool themselves when needed. Success looks like fewer incidents reaching L3, faster time-to-resolution, and an Operations function that trusts its own data."
Pay: "The base salary range for this position is $140,000 - $180,000 per year. This range reflects the minimum and maximum base salary we reasonably expect to pay for this role. In addition, this position may be eligible to participate in the relevant business unit’s incentive compensation plan, and other compensation programs as applicable."
Benefits: "Eligible employees may participate in a 401(k) program with a generous profit-sharing contribution, medical, prescription dental, and vision coverage; life insurance; disability coverage; paid holidays; vacation; and sick time, subject to plan terms and Company policies."
Then there is "About Bessemer Trust" and "Key Facts" and "About Our Employee Rewards And Benefits". Those are company description; could be considered "About the company" but not in headings list. Might be optional to include? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The headings list is just examples; we could add "About the company" if we want, but better to stick to given headings. However we have substantive content about company; maybe we can include under "About the role"? Not appropriate. Could we add a section "About the company"? Not in list but maybe allowed as e.g. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive. So we could add other headings like "About the company". But to be safe, we could incorporate that info into "About the role" or maybe omit as not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company description. If we omit a heading for it, we lose that info. So we need a heading for it. Could use "About the company". That seems reasonable.
Similarly "Key Facts" and "About Our Employee Rewards And Benefits" could be merged into "About the company" or separate "Company Overview" and "Benefits". But we already have Benefits heading for employee benefits. The company description about Bessemer Trust is separate from benefits. So we need a section for company overview.
Thus headings: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, About the company (or Company Overview). Schedule not present, omit.
We must not repeat job title. No Job ID.
Now format:
About the role
Role Summary paragraph.
Responsibilities
- ... each bullet
Qualifications
- Required Qualifications bullets
Skills
- Preferred Qualifications bullets
Benefits
Benefits paragraph.
Pay
Pay paragraph.
About the company
About Bessemer Trust paragraph(s) plus Key Facts and About Our Employee Rewards And Benefits? Actually the latter is about benefits again; we already have Benefits heading for employee benefits. The "About Our Employee Rewards And Benefits" repeats benefits info; we could include that under Benefits as well, but we already have benefits paragraph. Might duplicate. Better to combine: Benefits section includes both the earlier benefits paragraph and the "About Our Employee Rewards And Benefits" content. But we must not invent filler; we can combine them.
Thus Benefits section: combine the two paragraphs about benefits.
Let's extract benefits paragraphs:
First: "Eligible employees may participate in a 401(k) program with a generous profit-sharing contribution, medical, prescription dental, and vision coverage; life insurance; disability coverage; paid holidays; vacation; and sick time, subject to plan terms and Company policies."
Second: "We provide exceptional rewards and benefits that are among the best in the industry, giving our people access to a wide range of options, including: Competitive base salary plus discretionary annual bonus for select positions A 401(k) plan with a generous annual profit-sharing contribution Personalized development and career opportunities, including tuition reimbursement support Comprehensive medical, dental, and vision plans with zero contributions for employee coverage Employee assistance (EAP) and wellness programs Hybrid work environment: 60% in office, 40% remote for most positions Paid time off and paid parental leave Employer-paid life insurance and short- and long-term disability coverage Legal services and financial wellness plans at no cost to employees Bessemer Trust is committed to creating a diverse and inclusive environment and is proud to be an equal opportunity employer. We encourage candidates of diverse backgrounds to apply."
We should keep all that.
Now About the company: Bessemer Trust description and Key Facts.
Extract Bessemer Trust paragraph: "About Bessemer Trust Bessemer Trust is a family office, overseeing $250 billion in assets for over 3,000 individuals and families of substantial wealth.
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive. So we could add other headings like "About the company". But to be safe, we could incorporate that info into "About the role" or maybe omit as not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company description. If we omit a heading for it, we lose that info. So we need a heading for it. Could use "About the company". That seems reasonable.
Similarly "Key Facts" and "About Our Employee Rewards And Benefits" could be merged into "About the company" or separate "Company Overview" and "Benefits". But we already have Benefits heading for employee benefits. The company description about Bessemer Trust is separate from benefits. So we need a section for company overview.
Thus headings: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, About the company (or Company Overview). Schedule not present, omit.
We must not repeat job title. No Job ID.
Now format:
About the role
Role Summary paragraph.
Responsibilities
- ... each bullet
Qualifications
- Required Qualifications bullets
Skills
- Preferred Qualifications bullets
Benefits
Benefits paragraph.
Pay
Pay paragraph.
About the company
About Bessemer Trust paragraph(s) plus Key Facts and About Our Employee Rewards And Benefits? Actually the latter is about benefits again; we already have Benefits heading for employee benefits. The "About Our Employee Rewards And Benefits" repeats benefits info; we could include that under Benefits as well, but we already have benefits paragraph. Might duplicate. Better to combine: Benefits section includes both the earlier benefits paragraph and the "About Our Employee Rewards And Benefits" content. But we must not invent filler; we can combine them. Thus Benefits section: combine the two paragraphs about benefits. Let's extract benefits paragraphs: First: "Eligible employees may participate in a 401(k) program with a generous profit-sharing contribution, medical, prescription dental, and vision coverage; life insurance; disability coverage; paid holidays; vacation; and sick time, subject to plan terms and Company policies." Second: "We provide exceptional rewards and benefits that are among the best in the industry, giving our people access to a wide range of options, including: Competitive base salary plus discretionary annual bonus for select positions A 401(k) plan with a generous annual profit-sharing contribution Personalized development and career opportunities, including tuition reimbursement support Comprehensive medical, dental, and vision plans with zero contributions for employee coverage Employee assistance (EAP) and wellness programs Hybrid work environment: 60% in office, 40% remote for most positions Paid time off and paid parental leave Employer-paid life insurance and short- and long-term disability coverage Legal services and financial wellness plans at no cost to employees Bessemer Trust is committed to creating a diverse and inclusive environment and is proud to be an equal opportunity employer. We encourage candidates of diverse backgrounds to apply." We should keep all that. Now About the company: Bessemer Trust description and Key Facts. Extract Bessemer Trust paragraph: "About Bessemer Trust Bessemer Trust is a family office, overseeing $250 billion in assets for over 3,000 individuals and families of substantial wealth.