Principal Site Reliability Engineer

for prose. So we can embed physical requirements as a

within Requirements. Skills: maybe we can extract from qualifications: experience with software development, scripting, etc. Could be a Skills section. Benefits: The posting includes "Some of the Ways We Prioritize Your Health and Happiness" with bullet list of benefits. So we can create Benefits section with

• . Pay: The posting includes base pay scale for Phoenix and San Francisco, plus discretionary incentive plan and benefits. So we have pay info. Should create Pay section. Schedule: The posting mentions hybrid work model for positions located in Scottsdale, San Francisco, Chicago, or New York. Also maybe schedule not explicitly given. It says "Positions located in Scottsdale, San Francisco, Chicago, or New York follow a hybrid work model". That's schedule info (hybrid). So we can create Schedule section with that. We must not include sections with filler like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Must remove those paragraphs. We must preserve all substantive information: need to include details about role summary, responsibilities, minimum qualifications, preferred qualifications, physical requirements, benefits, pay, schedule, hybrid work model, eligibility to work in US, visa sponsorship ineligible, etc. We must not invent or summarize away detail. Must keep all specifics. We need to format with headings

  for each section. Inside sections, we can have

  for prose and

  • for lists. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must not include markdown fences. We must output only HTML fragment. Let's extract content. First, About the role: The "Role Summary" paragraph(s). Also "Leveling Intent" and "Level Expectations" maybe part of About the role. Let's include them as prose. Role Summary: "The Principal Site Reliability Engineer applies software engineering and systems engineering practices to improve the reliability, resilience, scalability, and operational health of production services. The role partners with Software Engineering and other technology teams to ensure reliability, observability, recoverability, performance, and operational readiness are engineered into systems throughout their lifecycle. The role operates at enterprise scope, establishing technical direction and applying evidence-driven engineering, technical rigor, sound judgment, automation, and broad systems expertise across organizational boundaries." Leveling Intent: "Principal represents enterprise domain-level technical leadership and organizational impact. Deep individual expertise is expected, but Principal-level impact comes from identifying systemic risk, establishing technical direction, influencing engineering practices and architecture, and multiplying the capability of the broader engineering organization." Level Expectations: "Acts as an enterprise force multiplier, raising the effectiveness and technical capability of engineers and teams across the organization while building sustainable organizational capability rather than individual dependency. Demonstrates software engineering, systems thinking, troubleshooting, and production reliability capabilities appropriate to the level. Applies evidence-driven reasoning and technical rigor to distinguish observed facts from assumptions and make defensible engineering recommendations. Shares knowledge and contributes to sustainable engineering capability rather than creating dependency on individual expertise. Operates with significant autonomy across the organization's most consequential reliability challenges. Establishes enterprise technical direction, develops senior technical leaders, and demonstrates impact well beyond systems personally touched." We can combine these into About the role section as multiple paragraphs. Responsibilities: The "Core Responsibilities" list. It's a long paragraph with many sentences separated by periods. We need to turn into list items. The spec says use
    • for any list of duties/requirements/benefits. So we should split each responsibility into separate
    • . The original text: "Use software engineering, automation, and DevOps principles and practices to continually improve how services are built, tested, deployed, observed, operated, and recovered. Use data, evidence, experimentation, and rigorous engineering analysis appropriate to the level to identify reliability risks, test assumptions, and guide technical decisions. Define, implement, or improve SLIs, SLOs, error budgets, and other service-health measures appropriate to the scope of responsibility. Improve observability through metrics, logging, tracing, monitoring, alerting, dashboards, and service-health instrumentation. Drive continuous improvement across CI/CD, observability, deployment practices, Infrastructure as Code, automation, testing, incident response, capacity management, resilience, and operational readiness. Identify recurring or systemic production issues and translate operational experience into improvements in code, architecture, automation, tooling, and engineering practices. Partner with Software Engineering teams to incorporate reliability, resiliency, scalability, performance, observability, recoverability, and operational readiness throughout the development lifecycle. Participate in or lead incident response, troubleshooting, service restoration, and blameless post-incident learning appropriate to the level. Provides enterprise-level technical leadership for critical production incidents and establishes or influences engineering practices that improve incident response, escalation, service restoration and sustainable on-call operations across the organization. Reduce operational toil and unnecessary manual intervention through software, automation, reusable patterns, and better engineering practices." We can split each sentence as a list item. Requirements: Minimum Qualifications. Let's extract: "Typically 15+ years of relevant professional experience in Software Engineering, Site Reliability Engineering, Systems Engineering, Cloud/Platform Engineering, DevOps, Infrastructure Engineering, Architecture where applicable, or a comparable technical discipline. Experience with software development or scripting using one or more modern programming languages. Experience with software engineering principles, distributed systems, production troubleshooting, automation, and observability appropriate to the level. Experience with public cloud technologies and architectures, preferably AWS, along with infrastructure, networking, Linux/Unix, and modern application architectures appropriate to the level. Demonstrated analytical, problem-solving, communication, and collaboration skills appropriate to the scope of the role." We can make each bullet as
    • . Also Physical Requirements: "Early Warning works together in a highly collaborative office environment. Working conditions consist of a normal office environment. Work is primarily sedentary and requires extensive use of a computer and involves sitting for periods of approximately four hours. Work may require occasional standing, walking, kneeling, and reaching. Must be able to lift 10 pounds occasionally and/or negligible amount of force frequently. Requires visual acuity and dexterity to view, prepare, and manipulate documents and office equipment including personal computers. Requires the ability to communicate with internal and/or external customers. Employee must be able to perform essential functions and physical requirements of position with or without reasonable accommodation." We could include this as part of Requirements (maybe as a separate subsection but still within Requirements). Since we only have Requirements section, we can add a

      for physical requirements after the list. Qualifications: Preferred Qualifications. Let's extract: "Hands-on experience with AWS is preferred, or comparable experience with another major cloud platform such as Microsoft Azure, Google Cloud Platform (GCP), or Oracle Cloud Infrastructure (OCI). Experience developing, deploying, operating, or improving highly available production software or distributed systems. Experience with CI/CD, Infrastructure as Code, containers or orchestration, observability, monitoring, alerting, and software-delivery automation. Experience with SLIs, SLOs, error budgets, incident management, performance analysis, capacity management, resilience testing, disaster recovery, or operational readiness appropriate to the level. Experience creating reusable automation, tooling, platforms, patterns, or practices that improve engineering effectiveness. Bachelor's degree in Computer Science, Software Engineering, Computer Engineering, Information Systems, or a related technical field, or equivalent practical experience." We can make each as

    • . Skills: Could be derived from qualifications but maybe we can create a Skills section summarizing technical skills: e.g., software development, scripting, programming languages, distributed systems, AWS, etc. However we must not invent or summarize away detail; we should preserve all substantive information. If we create a Skills section, we need to ensure we are not duplicating content that already appears elsewhere? The spec didn't forbid duplication but we should preserve all info; duplication is okay as long as we don't lose info. However we should avoid creating thin sections. Perhaps we can skip Skills section and put skill-related info under Requirements or Qualifications. But the spec includes Skills as a possible section; we can decide to include if there is specific content. The posting does not have a dedicated "Skills" heading, but we can extract skill statements from qualifications. However that would be summarizing; but we could just move the skill-related bullet points into Skills section and keep them there, not duplicating. That would be preserving detail. The spec says "Prefer a few substantive sections over many thin ones." So we might combine skill info into Requirements or Qualifications. Since we already have Requirements (minimum) and Qualifications (preferred), we could treat those as covering skills. So we might omit Skills section. Benefits: The bullet list under "Some of the Ways We Prioritize Your Health and Happiness". Let's extract each benefit: - Healthcare Coverage – Competitive medical (PPO/HDHP), dental, and vision plans as well as company contributions to your Health Savings Account (HSA) or pre-tax savings through flexible spending accounts (FSA) for commuting, health & dependent care expenses. - 401(k) Retirement Plan – Featuring a 100% Company Safe Harbor Match on your first 6% deferral immediately upon eligibility. - Paid Time Off – Flexible Time Off for Exempt (salaried) employees, as well as generous PTO for Non-Exempt (hourly) employees, plus 11 paid company holidays and a paid volunteer day. - 12 weeks of Paid Parental Leave - Maven Family Planning – provides support through your Parenting journey including egg freezing, fertility, adoption, surrogacy, pregnancy, postpartum, early pediatrics, and returning to work. - And SO much more! We continue to enhance our program, so be sure to check our Benefits page here for the latest. Our team can share more during the interview process! We should keep all substantive info; the "And SO much more!" is vague but still part of benefits description. We'll keep as a
    • . Pay: The base pay scale for Phoenix, AZ: $173,000 - $230,000. San Francisco, CA: $207,000 - $276,000. Additionally, candidates are eligible for a discretionary incentive plan and benefits. Also note that pay scale is subject to change etc. We should include all that info. Schedule: Hybrid work model for positions located in Scottsdale, San Francisco, Chicago, or New York. Also maybe mention that other locations? Not needed. We'll include that. Also need to include eligibility to work in US and visa sponsorship ineligibility. That