Staff Site Reliability Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About IonQ:" then location, travel, job id, then "The Role:" description, then "Responsibilities:", "Requirements:", "Preferred Qualifications:", compensation, benefits, EEO etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Job ID" etc. Keep substantive info: IonQ description maybe considered "About the company"? Not required heading but we could include as a paragraph under maybe "About IonQ"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says we can use those headings if content exists. We should not repeat job title as heading. We need to include sections only when posting has real specific content. So we need sections: About the role? There's a description under "The Role:" which is a paragraph describing role. Could be "About the role". We'll put that as

About the role

then

... content. Responsibilities: list items. Requirements: list items. Preferred Qualifications: could be under "Qualifications" heading? The instruction list includes Qualifications as possible heading. We'll use

Qualifications

for Preferred Qualifications. Benefits: there is benefits description. Pay: there is wage transparency range $152,000—$228,000 USD. Also mention total compensation includes base, bonus, equity, etc. So we can include Pay section. Schedule: location mentions remote option few days a week, travel up to 25%. Could be under Schedule? Not exactly schedule but we could include location and travel maybe under "Schedule"? The instruction says Schedule heading for schedule info. We have location and remote option, travel. Could treat as Schedule? Might be better to include a short paragraph under maybe not a heading? But we need to include only when posting has real specific content. We have location and travel info. Could create a

Schedule

with paragraph about location and remote option and travel. Or we could incorporate location into About the role paragraph. But better to follow instruction: Use heading Schedule if we have schedule info. We have location and remote option, travel up to 25%. That's schedule-ish. We'll do Schedule. We must not include headings with filler like "commensurate with experience". We have actual numbers. We must not repeat job title as heading. Not include Job ID. We must remove EEO boilerplate etc. So we will strip all that. We need to preserve all substantive information: IonQ description, location, travel, role description, responsibilities list, requirements list, preferred qualifications list, compensation, benefits. Let's extract content. About IonQ paragraph: "IonQ, Inc. [NYSE: IONQ] is the world's leading quantum platform and merchant supplier - delivering integrated quantum solutions across computing, networking, sensing, and security. IonQ's newest generation of quantum computers, the IonQ Tempo, is the latest in a line of cutting-edge systems that have been helping customers and partners including Amazon Web Services, and AstraZeneca achieve 20x performance results and accelerate innovation in drug discovery, materials science, financial modeling, logistics, cybersecurity, and defense. In 2025, the company achieved 99.99% two-qubit gate fidelity, setting a world record in quantum computing performance. Headquartered in College Park, Maryland, IonQ has operations in California, Colorado, Massachusetts, Tennessee, Washington, Italy, South Korea, Sweden, Switzerland, Canada, and the United Kingdom. Our quantum computing services are available through all major cloud providers, while we also meet the needs of networking and sensing customers across land, sea, air, and space. IonQ is making quantum platforms more accessible and impactful than ever before." Location: "Location: This role is based at our Santa Clara, CA office, with the option to work a few days a week remotely. Travel: Up to 25%" We could combine location and travel into Schedule section. The Role description paragraph after "The Role:" includes multiple sentences. Let's capture that: "The Platform Engineering team builds, secures, and operates scalable infrastructure for cloud-managed SaaS products with on-premises components deployed at customer sites. The Site Reliability Engineering discipline keeps the platform stable and reliable, with a strong focus on service continuity and customer experience. It owns production reliability, service-level objectives, observability architecture, backup and disaster recovery, incident response, and resilience, and co-owns cloud security posture and runtime vulnerability management with DevSecOps. As Staff Site Reliability Engineer, you set the technical direction for reliability across regions and services. You own the reliability strategy, define the standards and mechanisms that guide production operations, and raise the bar through design leadership, operational discipline, and mentorship. You remain deeply hands-on by designing and operating observability platforms, defining and governing SLO programs, leading high-severity incident response, building resilience and disaster-recovery automation, improving reliability of stateful and streaming platforms, and creating AI Ops workflows for triage, remediation, and self-healing. The work is driven by observability and automation, with a focus on detecting and fixing issues before customers are affected and using every incident to improve the system." Then after that there is a list of areas: "Production reliability, SLOs, and error budgets — the reliability of production services end to end, including standards, governance, and escalation for Tier-1 and Tier-2 services.Observability architecture and standards — metrics, logs, distributed tracing, and profiles instrumented across production systems, with consistent platform-wide standards.Chaos engineering and resilience — failure-injection experiments and validation of recovery mechanisms in pre-production and production environments.Backup and disaster recovery — backup validation, disaster-recovery architecture, failover testing, and recovery verification against defined RTO and RPO objectives.Cloud security posture — cloud security posture management, runtime vulnerability detection, and configuration-compliance monitoring, co-owned with DevSecOps.Data and streaming platform reliability — reliability engineering for Postgres, Redis/Valkey, Kafka, OpenSearch, and other critical stateful services.Capacity, efficiency, and AI Ops — resource rightsizing, predictive alerting, autonomous triage, remediation automation, and self-healing workflows.Incident response and command — severity classification, incident command, executive communication, and blameless post-incident review for the highest-severity events.On-call and escalation — rotation design, operational readiness, escalation policy, and clean follow-the-sun handoffs across regions." These could be considered part of responsibilities but they are also listed under Responsibilities later. We'll keep them as part of responsibilities list. Responsibilities list after "Responsibilities:" includes bullet points each starting with a bold? Actually they are sentences: "Production reliability — own service-level objectives, error budgets, and production reliability outcomes end to end, and represent reliability in architecture and scaling decisions.Engineer observability — design and operate the observability stack so production services are fully instrumented and define the standards platform and application teams follow.Govern SLOs and error budgets — define and manage service-level objectives, run regular reviews with service owners, and drive corrective action when services consume error budgets unsafely.Drive resilience — design and execute chaos experiments and validate that failure modes are covered by tested safeguards.Lead incident response — define the incident process and serve as incident commander for the highest-severity incidents, including security incidents within the coverage window.Run on-call and escalation — establish and manage rotations and escalation paths that provide continuous coverage with clean follow-the-sun handoffs.Disaster recovery — own disaster-recovery testing and failover validation against defined recovery objectives and turn exercise findings into architectural and operational improvements.Cloud security posture — co-own cloud security posture management, runtime vulnerability detection, and configuration-compliance monitoring with DevSecOps.Data, streaming, and AI Ops — own reliability of stateful and streaming services, capacity planning and rightsizing, and autonomous agents for triage, predictive alerting, remediation, and self-healing.Scale the team and broaden impact— mentor engineers at different seniority levels, set standards adopted across teams, and align Architecture, DevSecOps, Cloud Operations, and Product Development behind a shared reliability roadmap." We'll turn each into

. Requirements list after "Requirements:" includes: "7+ years of production engineering experience with recent hands-on reliability work.Hands-on, recent experience operating large-scale, fault-tolerant production systems on AWS or GCP.Observability ownership — has instrumented production systems and governed service-level objectives and error budgets, not only installed dashboards.Resilience practice — has designed and executed failure experiments or disaster-recovery exercises with real failover validation.Incident command — has personally commanded serious SEV1/SEV2 incidents and driven root cause through to a systemic fix.Demonstrated ownership of reliability outcomes with measurable results, such as availability, mean time to recovery, and error-budget adherence.Evidence of multi-team technical leadership through standards, review, coaching, and mechanisms adopted beyond one service or team." We'll list each. Preferred Qualifications list after "Preferred Qualifications:" includes many items. We'll list each. Compensation: "The total compensation package includes base, bonus, equity, and a range of benefit options found on our career site. If this role has a commission structure, the compensation range below just reflects the base compensation range. Wage Transparency: $152,000—$228,000 USD Compensation will vary based on individual factors such as education, qualifications, and experience of the final candidate(s), specific office location, and calibration against relevant market data and internal team equity. Posted base salary figures are subject to change as new market data becomes available." We'll put in Pay section. Benefits: "Our benefits include comprehensive medical, dental, and vision plans, matching 401(k), unlimited PTO and paid holidays, parental/adoption leave, legal insurance, and a home technology stipend. Details of participation in these benefit plans will be provided when a candidate receives an offer of employment." We'll put in Benefits section. Schedule: location and travel. We'll also maybe include a short paragraph about location under Schedule. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

...

Responsibilities

• ...
...

Requirements

...

Qualifications

...

Benefits

...

Pay

...

Schedule

...

We need to ensure we don't duplicate content. The role description includes some paragraphs that could be considered part of About the role. We'll include the initial paragraph after "The Role:" as About the role. Then responsibilities list as separate. We must not include the repeated lists of areas that appear before Responsibilities (the long sentence list). Those are essentially same as responsibilities but we can ignore to avoid duplication. However we need to preserve ALL substantive information; we cannot omit details. But if we include them in responsibilities list we cover them. The earlier list is basically same items but phrased differently. To preserve all, we could incorporate them into responsibilities as well, but we risk duplication. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not summarizing away detail; it's repeating detail. It might be okay to repeat but better to avoid duplication? The instruction didn't forbid duplication, but said remove duplicated lines. It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. The earlier list appears to be duplicated content that is also in Responsibilities. So we should remove that