Senior Observability Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes: - Intro: "The Role Joining Moderna means ..." This is like About the role? Could be "About the role" or maybe "The Role". We'll treat as "About the role" heading. - "Here’s What You’ll Do" -> Responsibilities. - "The key Moderna Mindsets you'll need to succeed in the role:" maybe part of Requirements? Could be under "Requirements" or "Qualifications". But we have separate sections: "Here’s What You’ll Need (Minimum Qualifications)" and "Here’s What You’ll Bring to the Table (Preferred Qualifications)". Those are Requirements (minimum) and Preferred Qualifications (maybe Skills). Also "Our Working Model" maybe not a standard heading; could be omitted? It's about work model, maybe not needed. "Pay & Benefits" heading present: we have Benefits and Pay sections. The posting includes "Pay & Benefits" with description of benefits but no specific pay numbers. According to rules: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (list). It does not state specific pay numbers. So we can include Benefits section (since benefits are described). Pay section: no specific pay, so we should not create Pay heading. Schedule: not mentioned (except working model 70/30 in-office). That's schedule info? It mentions working model but not schedule like hours. Could treat as Schedule? The rule: only include Schedule if posting actually states them. It does state "70/30 work model" which is schedule-ish. Might be considered schedule. But we need to decide. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states benefits (list). It states working model (70/30 in-office). That could be considered schedule. However they also have "Our Working Model" paragraph. Might be appropriate to include Schedule section with that content. But we need to see if they want schedule like "Full-time", "Hybrid". The posting says "70% in-office structure". That is schedule info. So we can include Schedule. But we must avoid filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need to convert the bullet-like sentences into
• . The responsibilities are many sentences each starting with a verb. We'll wrap each as
• . Similarly for minimum qualifications list, preferred qualifications list, benefits list. We need to preserve all substantive information; do not invent or summarize away detail. So we must keep all details. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement and accommodation info. That's boilerplate; we should remove. Also remove "Our Working Model" maybe not boilerplate but it's substantive; we could keep as Schedule. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  ...

  Responsibilities

  • Own the enterprise observability platform, driving cost optimization, capacity planning, telemetry governance, and sustainable platform growth.
  ...

  Requirements

  • 7+ years of experience in site reliability engineering, observability engineering, platform engineering, or related technical disciplines.
  ...

  Preferred Qualifications

  • Experience working in biotech, pharmaceutical, healthcare, or other regulated environments (e.g.,GxP, HIPAA).
  ...

  Benefits

  • Competitive healthcare, plus voluntary benefit programs to support your unique needs
  • A holistic approach to well-being with access to fitness, mindfulness, and mental health support
  • Family building benefits, including fertility, adoption, and surrogacy support
  • Generous paid time off, including vacation, bank holidays, volunteer days, sabbatical, global recharge days, and a discretionary year-end shutdown
  • Savings and investments to help you plan for the future
  • Location-specific perks and extras
  Maybe also include a paragraph about benefits description: "At Moderna, we believe that when you feel your best, you can do your best work. That’s why our benefits and well-being resources are designed to support you—at work, at home, and everywhere in between." Could be a

  before list. Similarly for Schedule: we could have

  Schedule

  As we build our company, we have always believed an in-person culture is critical to our success. Moderna champions the significant benefits of in-office collaboration by embracing a 70/30 work model. This 70% in-office structure helps to foster a culture rich in innovation, teamwork, and direct mentorship.

  Also maybe include a paragraph about "Our Working Model" as schedule. We need to ensure we don't repeat job title as heading. Not doing. We need to not include Job ID/requisition numbers. We need to remove duplicated lines: there may be duplicated sentences? Not seeing. We need to remove application instructions: "If you want to make a difference and join a team that is changing the future of medicine, we invite you to visit modernatx.com/careers to learn more about our current opportunities. Moderna is a place where everyone can grow. If you meet the Basic Qualifications for the role and you would be excited to contribute to our mission every day, please apply!" That's application instructions; remove. Also remove EEO statement and accommodation info. Now craft final HTML. Check that we include all substantive info from responsibilities, mindsets? The mindsets could be part of Requirements or maybe a separate section "Key Mindsets". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put mindsets under Requirements or Qualifications. Since they are mindsets needed to succeed, could be under Requirements. We'll include them as bullet points under Requirements? Or maybe as a

  before the list. Better to add as a

  describing mindsets then list of qualifications. But we must not invent sections. We can include a

  under Requirements describing mindsets. Thus:

  Requirements

  The key Moderna Mindsets you'll need to succeed in the role: We act with dynamic range, driving strategy and execution at the same time at every step. We obsess over learning. We don’t have to be the smartest, we have to learn the fastest.

  • 7+ years of experience in site reliability engineering, observability engineering, platform engineering, or related technical disciplines.
  ...
  Similarly for Preferred Qualifications we could put under Skills? The heading list includes Skills. Could use Skills for preferred qualifications. But we already have Requirements and Qualifications. The list includes Qualifications as a heading. Could treat Minimum Qualifications as Requirements, Preferred Qualifications as Qualifications. Or we could have Requirements (minimum) and Qualifications (preferred). Let's map: - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. Thus we will have:

  Requirements

  ... mindsets ...

  ...

  Qualifications

  ...
  We also have Skills heading optional; we could omit if not needed. Now Benefits: we have a paragraph before list: "At Moderna, we believe that when you feel your best, you can do your best work. That’s why our benefits and well-being resources are designed to support you—at work, at home, and everywhere in between." We'll include as

  then list. Schedule: we have paragraph about working model. Now About the role: we need to include the introductory paragraphs up to "Here’s What You’ll Do". Actually the intro includes: "The Role Joining Moderna means advancing mRNA science to transform medicine. Work with exceptional global teams on a broad pipeline and build a career that makes a real difference for patients. Moderna is strengthening its international business services hub in Warsaw, supporting our growing global operations. We welcome professionals ready to help advance our mission and shape the future of mRNA medicines. This is an opportunity to define the future of enterprise observability by building a modern, AI-enabled observability platform that delivers scalable, resilient, and cost-efficient monitoring across Moderna's technology landscape. As a senior individual contributor, you will lead platform strategy, governance, and engineering while enabling intelligent operational insights across applications, infrastructure, cloud services, networks, containers, databases, and AI-powered systems. Working with open standards, automation, and emerging AI technologies, you will help improve reliability, operational excellence, and business outcomes across the region." We'll put that as

  under About the role. Now Responsibilities: start after "Here’s What You’ll Do". We'll list each sentence as

• . Need to ensure we capture all responsibilities sentences. Let's extract responsibilities sentences from the text: "Own the enterprise observability platform, driving cost optimization, capacity planning, telemetry governance, and sustainable platform growth." "Manage and evolve Moderna's observability platform using technologies including OpenTelemetry, Prometheus, Grafana, VictoriaMetrics, and other modern observability solutions." "Lead platform governance, agent lifecycle management, architecture standards, roadmap development, and platform best practices." "Collaborate with technology vendors and open-source communities to influence product roadmaps and maximize platform value." "Design and build scalable, resilient, and cost-efficient observability architectures supporting applications, databases, hosts, containers, cloud services, networks, distributed systems, and AI/LLM-based workloads." "Develop and optimize telemetry pipelines for metrics, traces, and logs across hybrid cloud and on-premises environments." "Establish enterprise standards for monitoring, alerting, Service Level Objectives (SLOs), Service Level Indicators (SLIs), and proactive incident detection." "Enable self-service observability capabilities that accelerate troubleshooting, operational visibility, and platform reliability." "Design and implement observability capabilities for AI agents, LLM-powered applications, and agentic workflows, including monitoring prompts, responses, execution flows, latency, errors, taken consumption, and operational costs." "Define enterprise standards for AI observability, monitoring model performance, user interactions, reliability, and cost efficiency." "Implement AI observability solutions using Langfuse or similar technologies, enabling prompt analytics, optimization, intelligent alerting, debugging, and failure pattern detection." "Leverage AI and LLM technologies to support anomaly detection, operational insights, and root cause analysis." "Lead the enterprise logging strategy as a core pillar of the observability platform." "Design, build, and scale cost-efficient logging solutions using Grafana Loki and other modern open-source technologies." "Define enterprise logging standards, including centralized log ingestion, parsing, querying, retention policies, storage optimization, and query performance." "Partner with Security teams to ensure compliance, audit readiness, and forensic capabilities." "Integrate observability capabilities with incident management platforms such as PagerDuty to improve operational responsiveness." "Optimize on-call processes by ensuring alerts are meaningful, actionable, and routed effectively while supporting rapid incident resolution." "Provide real-time telemetry during incidents and contribute to root cause analysis activities." "Develop automation using Python, Terraform, Ansible, CI/CD pipelines, and infrastructure-as-code practices." "Implement self-healing capabilities and automated remediation to improve operational resilience." "Integrate the observability platform with enterprise technologies including ServiceNow, Jira, and other operational systems." "Develop dashboards and executive reporting that provide visibility into platform adoption, telemetry coverage, MTTA, MTTR, alert quality, reliability, operational performance,