Principal Site Reliability Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "A Day In The Life" description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We have content: description of role (A Day In The Life) could be "About the role" or "Responsibilities". The posting includes many bullet-like responsibilities. We can put under Responsibilities. Also there is "What You’ll Need" which includes requirements/qualifications/skills. We can split: Requirements (experience), Qualifications (education/certifications), Skills (technical). Also "Compensation & Benefits" includes Pay and Benefits. Schedule: remote info (When & Where You’ll Work) indicates remote fully remote, equipment provided, training virtual. That's schedule/location info. So we can include Schedule section. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, etc. Also remove "Learn more at tandemdiabetes.com", "Stay Awesome", etc. Also remove "Other duties as assigned." maybe keep? It's generic but could be considered boilerplate; better to drop. We must preserve all substantive information. So we need to capture all responsibilities listed, requirements, qualifications, skills, compensation, benefits, schedule. We must not invent or summarize away detail. Must not include filler like "commensurate with experience". Not present. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which content goes where. Let's extract sections: About the role: maybe a brief overview: "The Principal Site Reliability Engineer (SRE) is responsible for the reliability, availability, and performance of the company's production systems. This role leads day-to-day production support and incident response and progressively replaces reactive firefighting with engineered SRE practice: SLOs, observability, on-call design, runbooks, and automation. It also advances infrastructure automation (Terraform/IaC), CI/CD reliability, disaster recovery, and security and compliance readiness in partnership with cross-functional teams. The role works with a distributed team that includes offshore consulting partners and is expected to raise their capability and independence; success is measured as much by what the team can do without the Principal SRE as by what the Principal SRE delivers personally." That's prose. Responsibilities: list of duties broken into categories: Production Support & Incident Management, Reliability Engineering & Observability, Infrastructure Automation & CI/CD, Operational Governance and Compliance, Leadership, Mentorship & Collaboration, Contributing Responsibilities (partners With Other Owners). We can combine into a single list or keep subheadings? The instruction: use

  for section headings,

  • for any list of duties/requirements/benefits. It didn't forbid subheadings inside sections, but we should avoid extra headings not in allowed list? Probably okay to have

    but not required. Safer to just have one Responsibilities section with a big

    containing all duties as list items. But we need to preserve all detail; we can keep each duty as separate
    • . Could group but still list. Requirements: maybe "What You’ll Need" includes experience requirements: Demonstrated experience leading production support and incident management for production systems, including incident command during high-severity events. Strong grounding in SRE principles: SLIs/SLOs, blameless postmortems, toil reduction, and treating reliability as an engineering discipline rather than a purely operational function. Demonstrated experience owning on-call strategy, including rotation design, alert tuning, and escalation. Expertise with Terraform or comparable IaC at scale: module design, state management, and policy-as-code guardrails. Hands-on experience building CI/CD pipelines with reliability guardrails using tools such as GitHub Actions, Octopus Deploy, or Azure DevOps. Deep experience with at least one major cloud platform (AWS, Azure, or GCP; [ preferred]) and with containerization and orchestration (Docker/Kubernetes). Working knowledge of observability tooling (e.g., Prometheus, Grafana, Datadog, CloudWatch, ELK/OpenSearch) and using it to drive SLO-based alerting. Experience designing and testing disaster recovery, including backup/restore, failover, and RTO/RPO validation. Working knowledge of cloud security and compliance practices (IAM, network segmentation, encryption, vulnerability and patch management) and cloud cost optimization. Proficiency in at least one scripting or programming language (e.g., Python, Go, Bash) for automation and tooling. Experience in FDA and ISO regulated industries and with agile methodologies preferred. We could treat these as Requirements. Qualifications: "Extra Awesome" includes B.S. in Computer Science or equivalent, relevant cloud certifications preferred, 10+ years in SRE/DevOps/infrastructure engineering, including specific experiences, 2+ years mentoring or technically leading other engineers. We could split: Qualifications (education/certifications) and Requirements (experience). But the instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide mapping. Skills: maybe technical skills like Terraform, CI/CD, cloud platforms, observability, scripting, etc. But many of those overlap with requirements. Could treat "Skills" as technical proficiencies list. Better: Use Requirements for experience-based items (years, leading production support, incident management, on-call, etc). Qualifications for education/certifications (B.S., cloud certs). Skills for technical proficiencies (Terraform, IaC, CI/CD, cloud platforms, containerization, observability, scripting, etc). However there is overlap; but we must not invent or summarize away detail; we can split but ensure we don't lose any detail. Let's list all items from "What You’ll Need" and "Extra Awesome". What You’ll Need bullets: - Demonstrated experience leading production support and incident management for production systems, including incident command during high-severity events. - Strong grounding in SRE principles: SLIs/SLOs, blameless postmortems, toil reduction, and treating reliability as an engineering discipline rather than a purely operational function. - Demonstrated experience owning on-call strategy, including rotation design, alert tuning, and escalation. - Expertise with Terraform or comparable IaC at scale: module design, state management, and policy-as-code guardrails. - Hands-on experience building CI/CD pipelines with reliability guardrails using tools such as GitHub Actions, Octopus Deploy, or Azure DevOps. - Deep experience with at least one major cloud platform (AWS, Azure, or GCP; [ preferred]) and with containerization and orchestration (Docker/Kubernetes). - Working knowledge of observability tooling (e.g., Prometheus, Grafana, Datadog, CloudWatch, ELK/OpenSearch) and using it to drive SLO-based alerting. - Experience designing and testing disaster recovery, including backup/restore, failover, and RTO/RPO validation. - Working knowledge of cloud security and compliance practices (IAM, network segmentation, encryption, vulnerability and patch management) and cloud cost optimization. - Proficiency in at least one scripting or programming language (e.g., Python, Go, Bash) for automation and tooling. - Experience in FDA and ISO regulated industries and with agile methodologies preferred. Extra Awesome: - B.S. in Computer Science or an equivalent combination of education and applicable job experience, including technical school training and certifications in networks, servers, and cloud infrastructure; demonstrated production experience weighs more heavily than degree. - Relevant cloud certifications (e.g., AWS/Azure/GCP Professional or Architect level) preferred. - 10+ years in Site Reliability Engineering, DevOps, or infrastructure engineering, including: - Leading production support, incident management, and postmortem practice. - Managing production cloud infrastructure as code (Terraform or equivalent) at scale. - Operating and improving CI/CD pipelines in a production environment. - Designing, executing, and testing disaster recovery plans. - Partnering with security teams on production security and compliance posture. - 2+ years mentoring or technically leading other engineers, including engineers who are remote, offshore, or contracted through a partner organization. We need to avoid duplication. Some items repeat: leading production support etc appear both in What You’ll Need and Extra Awesome sub-bullets. We should keep each unique piece but not duplicate same sentence. We can combine. We'll create sections:

      About the role

      with prose from first paragraph(s) maybe also include "A Day In The Life" description.

      Responsibilities

      with
      list of duties from the bullet categories.

      Requirements

      with
      list of experience-based requirements (maybe from What You’ll Need and the 10+ years experience items). But we need to avoid overlapping with Skills. Better: Requirements: experience items (years, leading production support, incident management, on-call, etc). Qualifications: education/certifications (B.S., cloud certs). Skills: technical proficiencies (Terraform, IaC, CI/CD, cloud platforms, containerization, observability, scripting, etc). However many experience items also mention Terraform etc. Might be okay to have overlapping but we must not invent; we can keep them where they fit best. Let's decide: Requirements (
      ): - Demonstrated experience leading production support and incident management for production systems, including incident command during high-severity events. - Strong grounding in SRE principles: SLIs/SLOs, blameless postmortems, toil reduction, treating reliability as an engineering discipline. - Demonstrated experience owning on-call strategy, including rotation design, alert tuning, and escalation. - 10+ years in Site Reliability Engineering, DevOps, or infrastructure engineering. - 2+ years mentoring or technically leading other engineers (including remote, offshore, or contracted). - Experience in FDA and ISO regulated industries and with agile methodologies preferred. Qualifications (
      ): - B.S. in Computer Science or equivalent combination of education and applicable job experience (including technical school training and certifications in networks, servers, and cloud infrastructure); demonstrated production experience weighs more heavily than degree. - Relevant cloud certifications (e.g., AWS/Azure/GCP Professional or Architect level) preferred. Skills (
      ): - Expertise with Terraform or comparable IaC at scale: module design, state management, policy-as-code guardrails. - Hands-on experience building CI/CD pipelines with reliability guardrails using tools such as GitHub Actions, Octopus Deploy, or Azure DevOps. - Deep experience with at least one major cloud platform (AWS, Azure, or GCP) and with containerization and orchestration (Docker/Kubernetes). - Working knowledge of observability tooling (e.g., Prometheus, Grafana, Datadog, CloudWatch, ELK/OpenSearch) and using it to drive SLO-based alerting. - Experience designing and testing disaster recovery, including backup/restore, failover, and RTO/RPO validation. - Working knowledge of cloud security and compliance practices (IAM, network segmentation, encryption, vulnerability and patch management) and cloud cost optimization. - Proficiency in at least one scripting or programming language (e.g., Python, Go, Bash) for automation and tooling. Now Responsibilities: need to capture all duties from the sections: Production Support & Incident Management, Reliability Engineering & Observability, Infrastructure Automation & CI/CD, Operational Governance and Compliance, Leadership, Mentorship & Collaboration, Contributing Responsibilities. We'll create a comprehensive list. Let's extract each duty: Production Support & Incident Management: - Leads day-to-day production support: intake, triage, prioritization, escalation, queue health, and change execution. - Establishes consistent support practices across a distributed team, including shift handoffs, ticket quality standards, and clear ownership of open issues. - Leads incident management end-to-end: incident command, stakeholder communication, and blameless postmortems with corrective actions tracked to closure. - Participates in and coordinates response activities for production security incidents,