Software Development · San Francisco, CA

Hybrid Full-time

Senior Software Engineer, Issue Detection

Sentry · San Francisco, CA · Posted Sep 14, 2026

This posting comes from Sentry. Confirm the details on their site before applying.

Overview

Issue Detection decides when something is wrong in a developer's application. Today that mostly means individual errors, and teams still set up alerts by hand to find out when something bigger breaks. That's changing. Sentry already sees enough of an application to recognize an outage, an error spike, a regression or a failing dependency on its own, for every project, without anyone configuring a monitor.

Responsibilities

  • Detect incidents by default. Build detection that recognizes outages, error spikes and regressions on every project with no setup, and that people and agents can adjust when they need to.
  • Decide what's real before anyone is paged. Check each signal against what Sentry knows about the application, its traffic, releases and history, so detection can fire early without false alarms.
  • Detect more than errors. Find slow queries, failing dependencies and other problems in performance data on our shared detector platform. Detection runs on Kafka-fed pipelines processing billions of events a day, so it has to be fast and cheap enough to run for every customer.
  • Own projects end to end. Scope work with product and design, make the technical calls, ship it, measure whether it worked, and keep improving it. Help the engineers around you do the same.
  • Are comfortable when the ground keeps moving. How teams find out about and respond to production problems is changing every few months. You'd rather design for where that's going than keep tuning hand-configured alerts.
  • Like problems you can measure. You can see which incidents were real, how quickly the right person heard about them and how long they stayed open. You'll make precision, recall and latency tradeoffs with real data.
  • Want to design from the outcome. Start from what the best incident experience looks like for a developer, from first signal to fix, and work back to the systems you own, even when that means replacing something we already have.
  • Want to use what you build. We debug Sentry with Sentry, including our own incidents. You'll be responsible for what you ship, and you'll use that experience to decide what we detect next.

Requirements

  • 4+ years of software engineering, much of it on backend systems in Python
  • You've owned a high-volume data pipeline or stream processor in production
  • You've built alerting, anomaly detection or monitoring that people relied on, and tuned its precision and recall with real data
  • You've responded to production incidents and know what slows a response down
  • You're comfortable moving quickly and iterating toward an ideal solution
  • You're product-minded and care about what the person getting paged actually sees
  • You communicate clearly in writing and in person

Great fits start here.

Whether you're looking for your next role or your next team member, give people and possibilities a place to meet.