Principal SRE Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About The Technology Organization, About The Team, Role Summary, What You'll Be Doing, How You Will Succeed, Your Basic Qualifications, What You Should Bring, Leadership Expectations, Additional Information (maybe includes schedule, benefits? Actually there is compensation info: "Actual compensation will depend on a candidate’s education, experience, skills, and geographic location. The anticipated wage for this position is $66,000 - $158,400". Also mentions "Full-time equivalent employees also will be eligible for a company bonus". So we have Pay info. Benefits? Not explicit. Schedule? "Availability to work flexible work hours is/may be required. This team supports continuous operations and may require non-standard work hours, including some work on weekends and holidays." So schedule info. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. So we need to map content to these headings. We have: - About the role: could be Role Summary? Or About The Technology Organization and About The Team? Might be "About the role" corresponds to Role Summary. We'll include a section with heading

About the role

and content from Role Summary paragraph. - Responsibilities: corresponds to "What You'll Be Doing" (list of duties). We'll output

• items. - Requirements: maybe "Your Basic Qualifications". We'll output list. - Qualifications: maybe "What You Should Bring" (preferred qualifications). Could be Skills? Actually "What You Should Bring" is preferred qualifications/skills. We'll treat as Skills. - Benefits: Not explicitly given besides bonus eligibility. There's mention of company bonus. Could be considered Benefits. We'll include Pay and Benefits separate? The instruction: include Pay and Schedule sections only if posting actually states them. Pay is stated: anticipated wage range. Benefits: mention of company bonus (maybe considered benefit). We'll include Benefits section with that info. - Schedule: mention flexible work hours, non-standard, weekends, holidays. So include Schedule. We must not include sections like "About the role" if we already have content? We'll include. We must not repeat job title. Not include ID etc. We must remove boilerplate: EEO, accommodation request, etc. Also remove "Additional Information" maybe not needed if we extracted schedule and benefits. But we can keep schedule and benefits. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections. Let's extract content precisely. Role Summary paragraph: "You build the self-healing automation, author the runbooks, and turn root-cause analysis into durable engineering fixes that let the production estate heal itself instead of paging a human. You work within the standards the Senior Principal SRE Engineer sets — SLOs, error budgets, observability — and you're the one who encodes them into working automation and documented procedure. This is a hands-on individual-contributor role focused on execution and codification rather than cross-estate reliability strategy. You decide, in partnership with the Senior Principal SRE Engineer, which recurring patterns warrant a self-healing investment versus a documented manual runbook, and you build whichever is right. You are an individual contributor. You do not manage people. You partner daily with the Senior Principal SRE Engineer, the agentic automation engineering team, and Operations on validating outcomes. Success is measured by self-healing coverage, runbooks authored and adopted, reduced recurrence of known failure modes, and the safety record of every automation you sign off." We'll put that as

  under About the role. Responsibilities (What You'll Be Doing) includes several bullet-like paragraphs. We need to convert each bullet into

• . The text includes headings like "Self-healing automation & resilience patterns", "Runbook authorship & validation", etc. We'll treat each as a list item with maybe the heading bold? But we just need
• containing the content. We'll preserve the detail. Let's list each bullet: - Self-healing automation & resilience patterns: "Design and build self-healing automation — circuit breakers, graceful degradation, automated remediation — for the failure modes that recur most across the estate. Run resilience or chaos testing to validate that self-healing patterns behave correctly before they're trusted in production. Continuously expand self-healing coverage as new failure modes are identified and proven safe to automate. Partner with the Senior Principal SRE Engineer on which failure modes justify self-healing investment versus a documented manual runbook." - Runbook authorship & validation: "Author and validate the remediation runbooks for the production estate: safe execution order, rollback steps, and exception handling for every documented fix. Keep the runbook library current as systems, dependencies, and failure modes evolve, retiring runbooks that no longer apply. Define and apply the graduation criteria that let a runbook move from human-executed to agent-assisted to autonomous." - RCA to durable fix: "Lead or contribute to root-cause analysis for significant incidents, and drive the blameless postmortem process to a durable engineering fix — not just a narrative. Convert recurring incident patterns into codified runbooks and, where appropriate, self-healing automation. Track fix effectiveness against recurrence, and escalate to the Senior Principal SRE Engineer when a fix needs broader engineering investment. Participate in high-severity incident response, including acting as incident commander for escalations within your area." - Partnership with agentic automation & operations: "Partner with the Agentic Automation Engineering team on which fixes are safe to hand off as agent-assisted remediations, and on the confidence thresholds and human-in-the-loop boundaries that keep them safe. Sign off on agent graduation criteria (accuracy over volume, zero P1/P2 caused) before an automation moves to a higher autonomy tier. Partner with Operations on outcome validation, feeding what's learned back into the runbook library and self-healing patterns." - Incident response & regulated-environment practice: "Ensure runbooks and self-healing automation meet Lilly's change-control, audit, and validated-environment standards. Document procedures so that audit evidence falls out of normal operation, not a special exercise. Mentor other reliability and automation engineers on runbook quality and self-healing design. Contribute proven patterns back to the broader reliability practice, in partnership with the Senior Principal SRE Engineer and Senior Architect." We'll put each as
• . Requirements (Your Basic Qualifications) list: - Bachelor's degree in Computer Science, Information Technology, or a related technical engineering discipline, including Software Engineering, Computer Engineering, Information Systems, Cybersecurity, Information Science, Network Engineering, Systems Engineering, Computer Information Systems (CIS), Management Information Systems (MIS), Cloud Computing, Data Science - 5+ years of progressive engineering experience, with meaningful time as a Site Reliability Engineer, Production Engineer, or equivalent, including hands-on ownership of self-healing automation or runbook-driven remediation for a multi-application production estate. - Production reliability experience in a regulated or audited environment (GxP, SOX, HIPAA, PCI, or equivalent), including familiarity with change-control discipline, audit evidence, and validated-system constraints. - Hands-on experience authoring and validating runbooks: safe execution order, rollback steps, and exception handling for real remediation procedures. - Demonstrated hands-on experience designing, implementing, and operating enterprise-scale SRE platforms, including observability solutions (Splunk, Datadog, New Relic, or Grafana/Prometheus), infrastructure-as-code with Terraform, CI/CD pipeline hardening, Kubernetes-based container platforms, and production workloads hosted on AWS, Azure, or GCP. - Experience designing self-healing patterns (circuit breakers, graceful degradation, automated remediation) and validating them before they're trusted in production. - Qualified applicants must be authorized to work in the United States on a full-time basis. Lilly will not provide support for or sponsor work authorization or visas for this role, including but not limited to F-1 CPT, F-1 OPT, F-1 STEM OPT,J-1, H-1B, TN, O-1, E-3, H-1B1, or L-1. We'll put each as
• . Skills (What You Should Bring) list: - Hands-on experience designing self-healing automation and running chaos engineering or resilience-testing programs (AWS Fault Injection Service, Gremlin, LitmusChaos, or equivalent) tied to measurable reliability gains. - Deep AWS fluency across reliability-relevant services (EKS, ECS, Lambda, CloudWatch, X-Ray, Systems Manager, Route 53), and familiarity with AWS Well-Architected Reliability Pillar. - Experience with AIOps or agent-assisted operations, including designing the guardrails, confidence thresholds, and human-in-the-loop boundaries that make automated remediation safe in production. - Experience defining or signing off on autonomy/graduation criteria for automation moving toward self-sufficiency. - Prior experience building or scaling a runbook library across multiple applications or teams. - Experience operating in pharma, healthcare, financial services, or other regulated industries. - Track record of contributing meaningfully to root-cause analysis and blameless postmortems, converting findings into durable engineering fixes measured by reduced recurrence rather than narrative quality. We'll put each as
• . Leadership Expectations list: - Treats every RCA as unfinished until it produces a durable fix, not just a narrative. - Combines engineering rigor with operational pragmatism in deciding what gets automated and what stays manual. - Leads through what they build and how they write, not through org-chart authority. - Comfortable telling a team that a fix isn't ready for autonomy yet, and showing them what's missing. - Treats runbook quality and knowledge-sharing as a first-class outcome, not an afterthought. We'll put each as
• . Pay: "Actual compensation will depend on a candidate’s education, experience, skills, and geographic location. The anticipated wage for this position is $66,000 - $158,400 Full-time equivalent employees also will be eligible for a company bonus (depending, in part, on company and individual". We'll capture that. Schedule: "Availability to work flexible work hours is/may be required. This team supports continuous operations and may require non-standard work hours, including some work on weekends and holidays." We'll put each as

  under respective headings. Benefits: maybe just the company bonus mention. We'll include Benefits section with that sentence. We must not include sections with filler like "commensurate with experience". Not present. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

  About the role

  ...Role Summary...

  Responsibilities

  • ...Self-healing automation & resilience patterns...
  • ...Runbook authorship & validation...
  • ...RCA to durable fix...
  • ...Partnership with agentic automation & operations...
  • ...Incident response & regulated-environment practice...

  Requirements

  • ...Bachelor's degree...
  • ...5+ years...
  • ...Production reliability experience...
  • ...Hands-on experience authoring and validating runbooks...
  • ...Demonstrated hands-on experience designing, implementing, and operating enterprise-scale SRE platforms...
  • ...Experience designing self-healing patterns...
  • ...Qualified applicants must be authorized to work in the United States on a full-time basis. Lilly will not provide support for or sponsor work authorization or visas for this role, including but not limited to F-1 CPT, F-1 OPT, F-1 STEM OPT,J-1, H-1B, TN, O-1, E-3, H-1B1, or L-1.

  Skills