Site Reliability Engineer, Observability
for headings, - for lists,
for prose.
We need to parse the posting.
First part: "At Ripple, we’re building a world..." repeated. That's about the company, maybe "About the role"? Actually "About the role" is typical heading for description of role. The posting includes "THE WORK:" and then description. So we can put that under "About the role" or "Responsibilities". The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- About the role: maybe the initial description of Ripple and the role context. Could be considered "About the role". We'll include a paragraph summarizing the mission and role context.
- Responsibilities: The "WHAT YOU’LL DO:" section lists bullet-like items (Observability Engineering, Infrastructure & IaC, Incident Management, Cross-Functional Enablement). Those are responsibilities.
- Requirements: The "WHAT YOU'LL BRING:" includes Core SRE Experience, Observability & Incident Management Expertise — Required, Infrastructure & Tools — Required, Desired / Additional. Those are requirements/qualifications.
We could separate Requirements (must-have) and Qualifications (desired) or Skills. But we can combine.
We need to avoid filler like "commensurate with experience". Not present.
Pay: There's salary range for NY: $160,000 - $200,000 USD. So we can include Pay section.
Benefits: There's a "WHO WE ARE:" section with benefits: Competitive salary, bonuses, equity; Competitive benefits covering physical and mental healthcare, retirement, family forming, and family support; Employee giving match; Mobile phone stipend; R&R days; Generous wellness reimbursement and weekly onsite & virtual programming; Generous vacation policy; Industry-leading parental leave policies; Family planning benefits; Catered lunches, fully-stocked kitchens; etc. Also "Take Control of Your Finances" and "Take Care of Yourself". So we have benefits content.
Schedule: Not mentioned explicitly. There's mention of in-office collaboration: "In-office collaboration for moments that matter is important to our culture, and we give managers and teams the flexibility to decide which 10+ days a month they come in." That's about schedule/hybrid. Could be considered Schedule. But it's not explicit schedule like full-time, remote, etc. Might be considered Schedule. However we should only include Schedule if posting actually states them. It does mention flexibility to decide which 10+ days a month they come in. That's schedule info. So we can include Schedule.
We must not include boilerplate like EEO etc. Remove that.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tools, percentages, etc.
We need to format as HTML fragment.
Let's craft sections:
About the role
At Ripple, we’re building a world where value moves like information does today. Through our crypto solutions for financial institutions, businesses, governments, and developers, we are improving the global financial system and creating greater economic fairness and opportunity for more people, in more places around the world. Ripple Treasury, now a Ripple solution acquired in 2025, marks a significant expansion into the multi‑trillion‑dollar corporate finance arena. With more than 40 years of experience supporting some of the world’s largest and most sophisticated companies, Ripple Treasury integrates a treasury command center into Ripple’s technology stack—giving corporates the ability to move, manage, and optimize liquidity in real‑time, across traditional and digital assets, under one expanded umbrella. This is an engineering‑first role with a coaching dimension—not the other way around. You will spend the majority of your time doing hands‑on observability and reliability engineering work: building instrumentation, designing alert configurations, authoring Terraform, and troubleshooting production systems. Alongside that, you will coach and consult with stream‑aligned product teams, helping them build operational maturity over time. You will join Ripple’s Technical Operations team and work across Azure (80%) and AWS (20%) environments supporting infrastructure that is predominantly Windows‑based (80%), handling significant payment volume for enterprise treasury customers. The incident management program you will help build is early‑stage—you will be establishing practices, not inheriting a mature playbook.
That seems to capture the initial description and THE WORK intro.
But we also have a separate Responsibilities section with bullet points. We could keep the above as About the role (overview) and then Responsibilities as list.
Responsibilities: list items from WHAT YOU’LL DO: Observability Engineering, Infrastructure & IaC, Incident Management, Cross-Functional Enablement. Each has sub-bullets.
We need to use - for any list of duties/requirements/benefits. So we can have nested lists? Probably we can have top-level
with - each responsibility, and inside each
- we can have
for sub-items.
Let's extract:
Observability Engineering:
- Design and implement monitoring, alerting, and dashboards in New Relic (APM, Infrastructure, Logs, Synthetics) across Azure and AWS; write NRQL queries for troubleshooting, analysis, and reporting.
- Define and implement SLOs/SLIs and error budgets; coach teams on using them to balance feature velocity with reliability and communicate system health to stakeholders.
- Lead alert noise reduction and signal quality engineering—tune thresholds, eliminate false positives, and ensure every alert is actionable.
- Optimize observability costs through log ingestion management, pipeline rules, and New Relic configuration governance.
- Partner with engineering teams to improve observability maturity: structured logging, metrics instrumentation (RED/USE methods), distributed tracing, and effective dashboard patterns.
Infrastructure & IaC:
- Develop and maintain Terraform infrastructure as code for provisioning and managing monitoring resources, alert configurations, and observability infrastructure—this is a primary engineering responsibility, not an occasional task.
- Establish and enforce IaC governance standards for observability infrastructure across teams, providing a repeatable, auditable model for how monitoring resources are managed.
- Author and troubleshoot Azure DevOps pipelines; support teams with deployment visibility, change tracking, and release hygiene as it relates to production reliability.
Incident Management:
- Administer and configure Incident.IO: alert routing, notification workflows, Slack and OpsGenie integration, and runbook management—operationalizing what exists today and expanding from there.
- Build out incident management foundations that are largely yours to establish: PIR/postmortem processes, on-call rotation design, escalation policies, incident severity classification, and response playbooks.
- Track and report on MTTR, MTTD, and incident frequency; identify trends and drive continuous improvement in partnership with engineering teams.
- Respond to and debrief on production incidents—providing real-time troubleshooting support and facilitating structured post-incident reviews.
Cross-Functional Enablement:
- Enable stream-aligned engineering teams to adopt improved observability and incident management practices through workshops, consultation, and hands-on guidance.
- Collaborate with the Subsystems Platform Team to translate common needs into self-service observability and incident management capabilities.
- Build lasting team competency through documentation, training materials, and knowledge-sharing sessions that outlast any individual engagement.
Now Requirements/Qualifications/Skills.
We have "WHAT YOU'LL BRING:" with sections:
Core SRE Experience:
- 7+ years in Site Reliability Engineering, DevOps, or Platform Engineering with a strong focus on observability and production operations.
- Proven ability to deliver hands-on engineering work while coaching and mentoring teams—comfortable switching between builder and consultant modes.
- Experience working in Agile/Scrum environments and collaborating effectively with cross-functional teams.
Observability & Incident Management Expertise — Required:
- Expert-level hands-on experience with New Relic (APM, Infrastructure, Logs, Synthetics, Alerts) and strong NRQL proficiency for troubleshooting and analysis.
- Deep understanding of structured logging, metrics collection (RED/USE methods), distributed tracing, and designing effective dashboards and alerts.
- Expertise defining and implementing SLOs/SLIs and error budgets for reliability management.
- Hands-on experience with incident management platforms (Incident.IO, PagerDuty, OpsGenie, or similar).
- Experience designing incident response workflows, on-call rotations, escalation policies, and facilitating post-incident reviews that drive actionable improvements.
- Demonstrated ability to troubleshoot complex production issues using observability data across distributed systems.
Infrastructure & Tools — Required:
- Strong Terraform experience: developing and maintaining IaC for cloud infrastructure and monitoring resources; familiarity with IaC governance patterns.
- Proficiency with PowerShell scripting (required given the 80% Windows environment).
- Strong experience with Azure cloud (App Services, Virtual Machines, Azure SQL, networking, monitoring) and working knowledge of AWS.
- Experience with Azure DevOps for CI/CD pipeline authoring and troubleshooting.
- Experience with Octopus Deploy for deployment management and release orchestration.
- Comfort working across both Windows and Linux server environments.
- Familiarity with Slack for operational workflows, alert routing, and incident communication.
Desired / Additional:
- Experience with alert noise reduction strategies and observability cost optimization (log ingestion, pipeline rules, cardinality management).
- Background facilitating chaos engineering, game day exercises, or failure injection to build team resilience.
- Knowledge of VM-hosted SQL Server monitoring and performance optimization.
- Familiarity with FinTech compliance requirements (SOC 2, ISO 27001) and audit evidence collection.
- Experience measuring and improving key reliability metrics (MTTR, MTTD, availability, error budgets) at an organizational level.
- Python or Bash scripting experience in addition to PowerShell.
- Familiarity with Jira for incident tracking and workflow automation.
Other common names for this role: Senior Site Reliability Engineer, Observability Engineer, Incident Management Engineer
We could treat "Other common names" as not needed.
We need to decide sections: Requirements (must-have) and Qualifications (desired) or Skills. The instruction says we can use sections like Requirements, Qualifications, Skills. We could combine Requirements and Qualifications into one section, but better to separate: Requirements (mandatory) and Qualifications (desired) or Skills (maybe both). However we must not create thin sections with filler. We have plenty of content for both.
Thus:
Requirements
Core SRE Experience:
- 7+ years in Site Reliability Engineering, DevOps, or Platform Engineering with a strong focus on observability and production operations.
- Proven ability to deliver hands-on engineering work while coaching and mentoring teams—comfortable switching between builder and consultant modes.
- Experience working in Agile/Scrum environments and collaborating effectively with cross-functional teams.
Observability & Incident Management Expertise — Required:
- Expert-level hands-on experience with New Relic (APM, Infrastructure, Logs, Synthetics, Alerts) and strong NRQL proficiency for troubleshooting and analysis.
- Deep understanding of structured logging, metrics collection (RED/USE methods), distributed tracing, and designing effective dashboards and alerts.
- Expertise defining and implementing SLOs/SLIs and error budgets for reliability management.
- Hands-on experience with incident management platforms (Incident.IO, PagerDuty, OpsGenie, or similar).
- Experience designing incident response workflows, on-call rotations, escalation policies, and facilitating post-incident reviews that drive actionable improvements.
- Demonstrated ability to troubleshoot
for prose. We need to parse the posting. First part: "At Ripple, we’re building a world..." repeated. That's about the company, maybe "About the role"? Actually "About the role" is typical heading for description of role. The posting includes "THE WORK:" and then description. So we can put that under "About the role" or "Responsibilities". The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have: - About the role: maybe the initial description of Ripple and the role context. Could be considered "About the role". We'll include a paragraph summarizing the mission and role context. - Responsibilities: The "WHAT YOU’LL DO:" section lists bullet-like items (Observability Engineering, Infrastructure & IaC, Incident Management, Cross-Functional Enablement). Those are responsibilities. - Requirements: The "WHAT YOU'LL BRING:" includes Core SRE Experience, Observability & Incident Management Expertise — Required, Infrastructure & Tools — Required, Desired / Additional. Those are requirements/qualifications. We could separate Requirements (must-have) and Qualifications (desired) or Skills. But we can combine. We need to avoid filler like "commensurate with experience". Not present. Pay: There's salary range for NY: $160,000 - $200,000 USD. So we can include Pay section. Benefits: There's a "WHO WE ARE:" section with benefits: Competitive salary, bonuses, equity; Competitive benefits covering physical and mental healthcare, retirement, family forming, and family support; Employee giving match; Mobile phone stipend; R&R days; Generous wellness reimbursement and weekly onsite & virtual programming; Generous vacation policy; Industry-leading parental leave policies; Family planning benefits; Catered lunches, fully-stocked kitchens; etc. Also "Take Control of Your Finances" and "Take Care of Yourself". So we have benefits content. Schedule: Not mentioned explicitly. There's mention of in-office collaboration: "In-office collaboration for moments that matter is important to our culture, and we give managers and teams the flexibility to decide which 10+ days a month they come in." That's about schedule/hybrid. Could be considered Schedule. But it's not explicit schedule like full-time, remote, etc. Might be considered Schedule. However we should only include Schedule if posting actually states them. It does mention flexibility to decide which 10+ days a month they come in. That's schedule info. So we can include Schedule. We must not include boilerplate like EEO etc. Remove that. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tools, percentages, etc. We need to format as HTML fragment. Let's craft sections:
About the role
At Ripple, we’re building a world where value moves like information does today. Through our crypto solutions for financial institutions, businesses, governments, and developers, we are improving the global financial system and creating greater economic fairness and opportunity for more people, in more places around the world. Ripple Treasury, now a Ripple solution acquired in 2025, marks a significant expansion into the multi‑trillion‑dollar corporate finance arena. With more than 40 years of experience supporting some of the world’s largest and most sophisticated companies, Ripple Treasury integrates a treasury command center into Ripple’s technology stack—giving corporates the ability to move, manage, and optimize liquidity in real‑time, across traditional and digital assets, under one expanded umbrella. This is an engineering‑first role with a coaching dimension—not the other way around. You will spend the majority of your time doing hands‑on observability and reliability engineering work: building instrumentation, designing alert configurations, authoring Terraform, and troubleshooting production systems. Alongside that, you will coach and consult with stream‑aligned product teams, helping them build operational maturity over time. You will join Ripple’s Technical Operations team and work across Azure (80%) and AWS (20%) environments supporting infrastructure that is predominantly Windows‑based (80%), handling significant payment volume for enterprise treasury customers. The incident management program you will help build is early‑stage—you will be establishing practices, not inheriting a mature playbook.
That seems to capture the initial description and THE WORK intro. But we also have a separate Responsibilities section with bullet points. We could keep the above as About the role (overview) and then Responsibilities as list. Responsibilities: list items from WHAT YOU’LL DO: Observability Engineering, Infrastructure & IaC, Incident Management, Cross-Functional Enablement. Each has sub-bullets. We need to use- for any list of duties/requirements/benefits. So we can have nested lists? Probably we can have top-level
- with
- each responsibility, and inside each
- we can have
- for sub-items.
Let's extract:
Observability Engineering:
- Design and implement monitoring, alerting, and dashboards in New Relic (APM, Infrastructure, Logs, Synthetics) across Azure and AWS; write NRQL queries for troubleshooting, analysis, and reporting.
- Define and implement SLOs/SLIs and error budgets; coach teams on using them to balance feature velocity with reliability and communicate system health to stakeholders.
- Lead alert noise reduction and signal quality engineering—tune thresholds, eliminate false positives, and ensure every alert is actionable.
- Optimize observability costs through log ingestion management, pipeline rules, and New Relic configuration governance.
- Partner with engineering teams to improve observability maturity: structured logging, metrics instrumentation (RED/USE methods), distributed tracing, and effective dashboard patterns.
Infrastructure & IaC:
- Develop and maintain Terraform infrastructure as code for provisioning and managing monitoring resources, alert configurations, and observability infrastructure—this is a primary engineering responsibility, not an occasional task.
- Establish and enforce IaC governance standards for observability infrastructure across teams, providing a repeatable, auditable model for how monitoring resources are managed.
- Author and troubleshoot Azure DevOps pipelines; support teams with deployment visibility, change tracking, and release hygiene as it relates to production reliability.
Incident Management:
- Administer and configure Incident.IO: alert routing, notification workflows, Slack and OpsGenie integration, and runbook management—operationalizing what exists today and expanding from there.
- Build out incident management foundations that are largely yours to establish: PIR/postmortem processes, on-call rotation design, escalation policies, incident severity classification, and response playbooks.
- Track and report on MTTR, MTTD, and incident frequency; identify trends and drive continuous improvement in partnership with engineering teams.
- Respond to and debrief on production incidents—providing real-time troubleshooting support and facilitating structured post-incident reviews.
Cross-Functional Enablement:
- Enable stream-aligned engineering teams to adopt improved observability and incident management practices through workshops, consultation, and hands-on guidance.
- Collaborate with the Subsystems Platform Team to translate common needs into self-service observability and incident management capabilities.
- Build lasting team competency through documentation, training materials, and knowledge-sharing sessions that outlast any individual engagement.
Now Requirements/Qualifications/Skills.
We have "WHAT YOU'LL BRING:" with sections:
Core SRE Experience:
- 7+ years in Site Reliability Engineering, DevOps, or Platform Engineering with a strong focus on observability and production operations.
- Proven ability to deliver hands-on engineering work while coaching and mentoring teams—comfortable switching between builder and consultant modes.
- Experience working in Agile/Scrum environments and collaborating effectively with cross-functional teams.
Observability & Incident Management Expertise — Required:
- Expert-level hands-on experience with New Relic (APM, Infrastructure, Logs, Synthetics, Alerts) and strong NRQL proficiency for troubleshooting and analysis.
- Deep understanding of structured logging, metrics collection (RED/USE methods), distributed tracing, and designing effective dashboards and alerts.
- Expertise defining and implementing SLOs/SLIs and error budgets for reliability management.
- Hands-on experience with incident management platforms (Incident.IO, PagerDuty, OpsGenie, or similar).
- Experience designing incident response workflows, on-call rotations, escalation policies, and facilitating post-incident reviews that drive actionable improvements.
- Demonstrated ability to troubleshoot complex production issues using observability data across distributed systems.
Infrastructure & Tools — Required:
- Strong Terraform experience: developing and maintaining IaC for cloud infrastructure and monitoring resources; familiarity with IaC governance patterns.
- Proficiency with PowerShell scripting (required given the 80% Windows environment).
- Strong experience with Azure cloud (App Services, Virtual Machines, Azure SQL, networking, monitoring) and working knowledge of AWS.
- Experience with Azure DevOps for CI/CD pipeline authoring and troubleshooting.
- Experience with Octopus Deploy for deployment management and release orchestration.
- Comfort working across both Windows and Linux server environments.
- Familiarity with Slack for operational workflows, alert routing, and incident communication.
Desired / Additional:
- Experience with alert noise reduction strategies and observability cost optimization (log ingestion, pipeline rules, cardinality management).
- Background facilitating chaos engineering, game day exercises, or failure injection to build team resilience.
- Knowledge of VM-hosted SQL Server monitoring and performance optimization.
- Familiarity with FinTech compliance requirements (SOC 2, ISO 27001) and audit evidence collection.
- Experience measuring and improving key reliability metrics (MTTR, MTTD, availability, error budgets) at an organizational level.
- Python or Bash scripting experience in addition to PowerShell.
- Familiarity with Jira for incident tracking and workflow automation.
Other common names for this role: Senior Site Reliability Engineer, Observability Engineer, Incident Management Engineer
We could treat "Other common names" as not needed.
We need to decide sections: Requirements (must-have) and Qualifications (desired) or Skills. The instruction says we can use sections like Requirements, Qualifications, Skills. We could combine Requirements and Qualifications into one section, but better to separate: Requirements (mandatory) and Qualifications (desired) or Skills (maybe both). However we must not create thin sections with filler. We have plenty of content for both.
Thus:
- 7+ years in Site Reliability Engineering, DevOps, or Platform Engineering with a strong focus on observability and production operations.
- Proven ability to deliver hands-on engineering work while coaching and mentoring teams—comfortable switching between builder and consultant modes.
- Experience working in Agile/Scrum environments and collaborating effectively with cross-functional teams.
- Expert-level hands-on experience with New Relic (APM, Infrastructure, Logs, Synthetics, Alerts) and strong NRQL proficiency for troubleshooting and analysis.
- Deep understanding of structured logging, metrics collection (RED/USE methods), distributed tracing, and designing effective dashboards and alerts.
- Expertise defining and implementing SLOs/SLIs and error budgets for reliability management.
- Hands-on experience with incident management platforms (Incident.IO, PagerDuty, OpsGenie, or similar).
- Experience designing incident response workflows, on-call rotations, escalation policies, and facilitating post-incident reviews that drive actionable improvements.
- Demonstrated ability to troubleshoot
Requirements
Core SRE Experience:
Observability & Incident Management Expertise — Required: