> Markdown version of [/jobs/ext/3322016-senior-software-engineer-sre](https://www.wearedevelopers.com/jobs/ext/3322016-senior-software-engineer-sre). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Software Engineer - SRE

- **Company:** Mercury Systems, Inc.
- **Location:** New York, NY, United States
- **Experience:** Expert
- **Salary:** $189,700.0 - $250,900.0
- **Contract:** Permanent contract
- **Skills:** Code Review, Software Debugging, Software Design Documents, DevOps, PostgreSQL, Reliability Engineering, TypeScript, Data Logging, Grafana, Glasgow Haskell Compiler
- **Published:** September 7, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=6bc4573bdbc6135e

## About the Role

* Has past Site Reliability Engineering or DevOps experience
 * Has measurable examples of influencing an organization towards greater reliability
 * Has significant experience with PostgreSQL
 * Has authored and operated Temporal workflows
 * Has experience with observability platforms like Grafana or Honeycomb
 * Has familiarity with OpenTelemetry, If this role interests you, we invite you to explore our public demo at personal-demo.mercury.com.

## Description

* Embed with product teams, helping them improve their operational maturity by setting up and refining practices around on-call, monitoring, alerting, and run books
 * Run regular game day exercises with product teams, helping them feel more prepared to investigate and quickly remediate incidents
 * Jump into application code written in Haskell & TypeScript and implement reliability techniques such as retries, better error handling, better logging, circuit breaking, etc
 * Steer SLOs towards meaningful customer outcomes that product teams are accountable for. Those SLOs become a strong signal for whether the product is working as intended
 * Champion reliability practices through design document and code reviews
 * Identify observability gaps that hinder debugging, incident response, and business intelligence and help close those
 * Advocate for longer-term improvements that non-product engineering teams can drive
 * Participate in the product team's on-call rotation while embedding or as part of a more general engineering rotation, helping us improve processes and how we learn from incidents