Site Reliability Engineering M6

Microsoft Substrate is the foundational cloud platform that powers many of Microsoft’s most critical services including Exchange Online and M365 Copilot, providing shared infrastructure, identity, messaging, storage, and service-to-service capabilities used across Microsoft 365 and related cloud offerings. Substrate services operate at global scale and are designed to deliver high availability, reliability, and security for some of the world’s most demanding workloads. 

We are seeking a Principal Site Reliability Engineering Manager to lead a team responsible for building and operating Substrate services in highly regulated environments. In these environments, success depends not only on operational excellence, but also on strong software engineering fundamentals—clean, maintainable code; sound design decisions; robust telemetry; and disciplined engineering lifecycle practices that make systems reliable by design. 

This role requires deep appreciation for software engineering as a reliability lever. You will lead teams that write and maintain production code, build automation and self-healing systems, and partner closely with feature engineering teams to ensure reliability, diagnosability, security, and compliance are embedded early in design and sustained throughout the service lifecycle. As a Principal-level manager, you will scale impact through others—developing senior and principal engineers, shaping reliability and engineering strategy, and influencing how Substrate services are designed, implemented, and operated across organizational boundaries. 

Microsoft’s mission is to empower every person and every organization on the planet to achieve more. As employees we come together with a growth mindset, innovate to empower others, and collaborate to realize our shared goals. Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond. 

• Lead and develop a team of Site Reliability Engineer ICs, providing clear expectations, regular coaching, and career guidance across senior and principal levels. Foster a culture of accountability, learning, and inclusion.  

• Own the operational health and reliability posture of Substrate services running in regulated environments, ensuring strong availability, incident readiness, and recovery practices. 

• Drive change and influence across the org as you establish and drive SLOs, SLIs, and operational metrics, using data and learning loops to continuously improve reliability, diagnosability, and customer experience. 

• Lead effective incident management and post-incident reviews, emphasizing systemic fixes, automation, and long-term resilience rather than short-term remediation. 

• Serve as an actively engaged on-call engineer (OCE) and participate in an on-call rotation, leading incident response for Substrate services in regulated environments, providing hands-on leadership during incidents, and driving high-quality post-incident reviews that result in durable engineering improvements. 

• Own reliability, resilience, and disaster recovery, including driving and coordinating DR and game day exercises, validating recovery objectives, and ensuring operational playbooks and restore procedures remain current, effective, and auditable. 

• Drive engineering led operational excellence at scale, leveraging strong software engineering practices, automation, and AI assisted techniques to reduce operational toil, improve diagnosability, and raise overall service and OCE health in partnership with infrastructure and service teams. 

• Partner with engineering and product teams to embed reliability, security, and compliance considerations early in service design, architecture, and deployment decisions. 

• Influence technical and operational strategy beyond your immediate team, particularly for cross‑cutting reliability and compliance challenges that span multiple services or organizations. 

• Represent your team’s work clearly to leadership and partners, articulating risks, trade‑offs, and progress in regulated environments with precision and credibility. 

• Build strong cross-functional relationships with security, compliance, infrastructure, and operations teams to deliver durable, compliant, and auditable reliability outcomes. ‑functional relationships with security, compliance, infrastructure, and operations teams to deliver. 

• Doctorate Degree in Computer Science, Information Technology, or related field AND 5+ years technical experience in software engineering, network engineering, or systems administration
  • OR Master's Degree in Computer Science, Information Technology, or related field AND 6+ years technical experience in software engineering, network engineering, or systems administration
  • OR Bachelor's Degree in Computer Science, Information Technology, or related field AND 8+ years technical experience in software engineering, network engineering, or systems administration
  • OR equivalent experience.

Ability to meet Microsoft, customer and/or government security screening requirements are required for this role. These requirements include but are not limited to the following specialized security screenings:

• Microsoft Cloud Background Check: This position will be required to pass the Microsoft Cloud background check upon hire/transfer and every two years thereafter.
• Citizenship & Citizenship Verification: This position requires verification of U.S. citizenship due to citizenship-based legal restrictions. Specifically, this position supports United States federal, state, and/or local United States government agency customer and is subject to certain citizenship-based restrictions where required or permitted by applicable law. To meet this legal requirement, citizenship will be verified via a valid passport, or other approved documents, or verified US government clearance. 
• This role needs to be able to access Substrate’s GCCM, GCCH, and DoD environments.  This requires at least a favorably adjudicated T3 background check (for GCCH/DoD) as well as CJIS (for GCCM).  For manager roles, T5 is preferred as we will need some people on the team with this for approvals. This section needs to be updated with the appropriate language for this.  (I am open to hiring people without these background checks who we believe can get them, as they could be trained while working on the background checks.  But, continuation in this role would be contingent on completing these requirements.)