Staff Site Reliability Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present. We have: About IonQ (company overview) maybe "About the role"? Actually "About the role" is a generic heading for role description. We have "The Role" paragraph. Could treat that as "About the role". Then "Responsibilities". Then "Requirements". Then "Preferred Qualifications" maybe under "Qualifications". Then "Benefits". Then "Pay". Also location and travel maybe as a short p.
We must not repeat job title as heading. Not include Job ID as heading. Remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, navigation, cookie, legal. Also remove duplicated lines.
We must preserve all substantive information. So we need to include location, travel, maybe remote option. Also mention that role based at Santa Clara, CA office, option to work a few days a week remotely. Travel up to 25%.
We need to include compensation: base salary range $152,000 - $228,000 USD, note that compensation varies based on factors, total compensation includes base, bonus, equity, benefits. Also mention benefits list: comprehensive medical, dental, vision, matching 401(k), unlimited PTO and paid holidays, parental/adoption leave, legal insurance, home technology stipend.
We need to include maybe a "Benefits" section with that list.
We need to include maybe a "Pay" section with salary range and note about total compensation.
We need to include maybe a "Schedule" section? Not present; location includes remote option but not schedule specifics. So we should not create Schedule unless stated. So omit.
We need to include maybe a "Qualifications" section: combine Requirements and Preferred Qualifications? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (mandatory) and Qualifications (preferred). Or we could have Requirements and Preferred Qualifications under Qualifications. But better to follow typical: Requirements (mandatory) and Preferred Qualifications (maybe under Qualifications). We'll output:
About the role
...
(the role description paragraph)Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
- ...
Pay
...
(salary range and note) Also include location/travel maybe as a short p after About the role? Could be part of About the role paragraph. But we can include a separate short p: "Location: Santa Clara, CA office with option to work a few days a week remotely. Travel: up to 25%." Not a heading. We must not include Job ID. Also remove any mention of "Posted base salary figures are subject to change..." etc. That's part of compensation details, we can keep but maybe shorten? We must preserve ALL substantive information; we cannot invent or summarize away detail. So we need to keep the compensation details exactly as given: "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. 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 need to keep that. Also earlier: "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." Keep that. Thus Pay section paragraph includes all that. Now we need to ensure we removed boilerplate: EEO, equal opportunity, scam-warning, legal, etc. Also remove "US Technical Jobs." etc. Also remove "US Non-Technical Jobs." etc. Also remove "At IonQ, we believe in fair treatment..." etc. That's EEO boilerplate; remove. Also remove "We are proud to be an Equal Employment Opportunity employer." etc. Remove. Also remove "Please note that in the absence of confirming you are a U.S. Person..." etc. That's export control legal; remove. Also remove "If you are interested in being a part of our team and mission, we encourage you to apply!" (application instruction) remove. Also remove "Job Details About IonQ IonQ, Inc . [NYSE: IONQ] is the world's leading quantum platform..." That's about company; we can keep as part of About the role? Actually it's company overview; we can include in About the role paragraph. We need to preserve all substantive information: company description, location, travel, role description, responsibilities, requirements, preferred qualifications, compensation, benefits. Let's craft. First, About the role paragraph: combine company overview and role description? Could be two paragraphs: one about IonQ, one about the role. But we need to usefor prose. We'll have maybe two
elements under About the role heading? The instruction: use
for section headings,
for prose. So we can have multiple
under a heading. Thus:
About the role
IonQ, Inc. (NYSE: IONQ) is the world's leading quantum platform and merchant supplier, delivering integrated quantum solutions across computing, networking, sensing, and security. Its newest generation of quantum computers, the IonQ Tempo, helps 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, IonQ 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. Its quantum computing services are available through all major cloud providers, while also meeting the needs of networking and sensing customers across land, sea, air, and space.
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%.
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.
But we might split responsibilities into its own section. The above paragraph includes a lot of role description; maybe we should keep that as About the role, and then Responsibilities section list. Now Responsibilities list: we need to extract bullet points from the "Responsibilities" section in the posting. Let's list them: - 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 need to preserve all substantive information; we can keep as list items. Now Requirements list: from posting: - 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. Now Preferred Qualifications list (Qualifications): - Proven production experience with cloud security posture management, runtime vulnerability detection, and workload protection across cloud and distributed environments. - Strong experience prioritizing risk using identity, workload, and exposure-path context to focus remediation on issues that materially increase attack likelihood and operational impact. - Experience with autonomous remediation and self-healing workflows powered by AIOps, including Amazon Bedrock Agent Core or equivalent agentic automation frameworks. - Hands-on experience in capacity management, resource rightsizing, efficiency engineering, and practical cost optimization based on FinOps principles. - Experience with load-balancing design and operations, including health-based failover, global traffic management, and performance optimization for highly available services. - Experience with AI traffic management via an LLM gateway,