Note: The job is a remote job and is open to candidates in USA. reputed company creates innovative diabetes technology products and services with a human-centered approach. The Principal Site Reliability Engineer is responsible for ensuring the reliability, availability, and performance of production systems by leading production support, incident management, infrastructure automation, and compliance activities. This role also mentors engineers and collaborates with cross-functional teams to embed reliability into the development lifecycle.
Responsibilities
• Leads day-to-day production support: intake, triage, prioritization, escalation, queue health, and reputed company 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, partnering with Security teams to contain threats, restore services, validate controls, and implement corrective actions
• Owns on-call strategy: rotation design, escalation paths, alert tuning, and tooling (e.g., reputed company, reputed company), with explicit goals of reducing alert fatigue and building coverage that works across time zones. Participates as a senior escalation tier for high-severity incidents
• Builds runbooks that standardize response to common failure modes and enable first-line resolution by engineers who did not build the system
• Defines and owns SLIs and SLOs for critical services, using them to guide monitoring, alerting, and reliability priorities
• Drives systemic reduction of MTTD and MTTR through better instrumentation, alerting, diagnostics, and automation
• Converts recurring support burden into permanent fixes, automation, or documentation rather than absorbing it as ongoing manual work
• Establishes and maintains technology currency and lifecycle management practices for production platforms, ensuring cloud services, Kubernetes clusters, operating systems, runtimes, and infrastructure components remain supported, secure, and aligned with organizational standards. Proactively identifies and mitigates End-of-Life (EOL), End-of-Support (reputed company), and technology obsolescence risks
• Owns business continuity and disaster recovery readiness for production platforms, including backup and recovery strategies, recovery testing, failover capabilities, recovery runbooks, and adherence to defined RTO/RPO objectives
• Leads infrastructure automation with Terraform, ensuring infrastructure is version-controlled, modular, reusable, and auditable, working within and reputed company existing patterns where they are sound
• Eliminates toil through automation, reducing manual, repetitive operational work across the team
• Adds reliability guardrails to CI/CD pipelines (automated rollback, reputed company-risk checks, progressive delivery) with the teams that own them
• Maintains production systems in accordance with applicable regulatory and compliance requirements, ensuring audit readiness and the ongoing effectiveness of access management, reputed company management, logging, vulnerability remediation, patch management, and other operational controls
• Maintains documentation and evidence supporting business continuity and disaster recovery controls, including recovery testing results, remediation plans, and audit artifacts
• Partners with Security, Quality, and Compliance teams to maintain regulatory compliance, support internal and external audits, and drive timely resolution of audit findings and remediation activities
• Actively grows the capability of SRE and DevOps engineers, including consulting-partner engineers, through pairing, design and code review, and incident debriefs
• Creates conditions in which junior and contract engineers raise concerns and disagree openly, recognizing that silent agreement is a production risk
• Communicates in a documentation-first manner suited to a distributed, multi-time-zone team, so context is durable rather than held by one person
• Partners with software engineering, QA, and architecture to embed reliability and operability into the development lifecycle rather than only after incidents
• Informs capacity planning and scaling strategy with the Test team (who own load testing and modeling) and introduces reputed company resilience testing such as game days once baseline support and observability are stable
• Partners with application, architecture, and business stakeholders to align business continuity and disaster recovery capabilities with application requirements and recovery objectives
• Supports cloud cost