Senior Principal SRE Engineering

About the technology organization

Role Summary:
As the Senior Principal SRE Engineering Lead, you are the senior-most engineering authority for the reliability of the supported production estate. You own the bar for what reliable means in this organization: service-level objectives, error-budget governance, observability standards, and the engineering practices that protect both production and the team's engineering time.

This role is the judgment layer between an agent's recommendation and a production change. You combine engineering rigor with operational pragmatism, and you decide which patterns surfaced from production warrant durable engineering investment. You hold the SRE engineering bar within the function — the cross-pillar reference architecture is owned by the Senior Architect, but the practice, standards, and engineering judgment of reliability at this site are yours.

You are a senior individual contributor. You do not manage people. You partner with the Reliability Leader, the Senior Principal Tech Shift Lead in the same pillar, the Senior Architect, and the senior engineering principals in the agentic automation team. Success is measured by organizational impact, sustained reliability outcomes, and the ability to scale reliability through systems and people, not heroics.

What you'll be doing:

1) Reliability strategy and SLO governance

• Define service-level objectives and indicators across the supported production estate, tiered by application risk and business impact.
• Govern error-budget burn: when to slow change, when to invest in durable fixes, when to accept the budget.
• Drive the adoption of reliability reporting and the disciplined operating cadence that makes SLOs real, not decorative.
• Hold the SLO and error-budget conversation with product and application owners — including the conversation about what their service needs to change to meet the bar.

2) Engineering standards, observability, and self-healing

• Establish observability and instrumentation standards as the contract every supported application must meet — and hold the line on them.
• Set the bar for infrastructure-as-code, continuous-delivery hardening, and deployment safety across the supported estate.
• Define the engineering work that flows from incidents and root-cause analyses into durable production change, and the architectural patterns (self-healing runbooks, graceful degradation, circuit breakers) that reduce repeat failure.

3) Incident learning, durable fixes, and partnership with agentic automation

• Drive blameless postmortem culture; ensure root-cause analyses produce engineering work, not just narrative.
• Govern which patterns from production warrant durable engineering investment, against the error-budget regime.
• Partner with the production operations team in the same pillar on which patterns from the field warrant engineering attention; partner with the agentic automation engineering team on which fixes become safe agent-assisted remediations, and on the confidence thresholds, guardrails, and human-in-the-loop boundaries that make those remediations safe in production.
• Lead high-severity incident response as incident commander when escalation reaches this seat, and coach the team to handle the rest.

4) Compliance, security, and regulated-environment readiness

• Ensure reliability practices comply with Lilly standards and applicable regulatory requirements, and engineer them so that audit evidence falls out of normal operation.
• Promote secure operational practices, auditability, and validated-environment-friendly engineering as part of the standards the team holds.
• Act as a trusted technical leader in regulated and validated environments.

5) Technical leadership and talent development

• Set the engineering bar through standards, expectations, and role modeling.
• Mentor senior reliability engineers in the pillar; build the bench for sustained team growth and develop the next layer of principal engineers.
• Influence engineering, product, and platform leaders through credibility and outcomes rather than authority.
• Contribute to the evolution of enterprise-wide reliability practices in partnership with the Senior Architect and peer technical leaders.

How you will succeed

At the senior-most engineering individual-contributor level for reliability, success is defined by breadth of impact and sustained outcomes:

• Be recognized as the senior reliability authority for your area.
• Demonstrate measurable, sustained improvements such as: reduced major incidents, fewer recurring failures, improved time-to-recovery, and a credible error-budget regime.
• Influence decisions across multiple teams and leaders through expertise and trust.
• Scale reliability through systems, standards, and people, not heroics.

Your Basic Qualification:

• 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
• 7+ years of progressive engineering experience, with at least 6 years as a Site Reliability Engineer, Production Engineer, or equivalent, including a tour as the senior-most reliability engineer for a multi-application production estate — not a single product.
• 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. 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 ownership experience of an SLO/SLI framework and error-budget policy across a multi-application estate, including defining SLIs, negotiating SLOs with product owners, and operationalizing burn-rate alerting and error-budget governance.
• Experience leading high-severity incident response as incident commander, running blameless postmortems, and converting findings into durable engineering work — measured by reduced recurrence rather than narrative quality.
• Demonstrated technical leadership experience at scale: mentoring senior ICs, influencing engineering and product leaders without org-chart authority, and writing the standards and engineering documents that set the bar for a discipline.

What You Should Bring:

• 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.
• Track record of saying no to a deploy because the error budget was burned, and making the call stick.
• Prior experience building a reliability practice from a small founding team.
• Experience operating in pharma, healthcare, financial services, or other regulated industries.

Leadership expectations

• Acts as the judgment layer between aspiration and engineering reality.
• Combines engineering rigor with operational pragmatism, and knows when each is the right answer.
• Leads through what they build and how they write, not through org-chart authority.
• Comfortable telling a product owner that their application does not meet the reliability bar yet, and showing them how to get there.
• Treats mentorship of senior reliability engineers as a first-class outcome of the role.

Additional information

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.